Content Governance Proposal

Web Content Governance Proposal Reducing effort and error through standardization and policy Proposed by: Paul Mitchell

Situation
An unfortunate fact is that most companies have no enterprise-wide content standards. This leads to teams implementing content projects attempting to reinvent the wheel, spending unnecessary time and resources defining and modeling content on an ad hoc basis, resulting in content that is not easily reusable by the enterprise in other channels.
Also, no mechanism exists to settle differences about content structure and management such as metadata, workflow standards, naming standards. W3C web standards are implemented inconsistently across teams and projects. All of this results in piecemeal, ad hoc solutions that do not scale or enable content reuse.

Goal
Reduce the amount of learning, negotiation and redesign in new projects while improving content integrity and promoting content reuse with enterprise-wide content standards and policies
Organizational groups following the standards and accountable for compliance
Content Standards Visual Guide intranet site, a central source for content standards, adopted as the single-point-of-truth

Proposal
Establish a Web Content Governance Council as an authoritative administrative structure that establishes policies, sets standards and sees to their enforcement.
The council would consist of representatives from each of the content stakeholder groups.
The activities of the council would be policy setting, standards codification and dissemination, standards implementation and enforcement, and evaluation, review and revision.
The council’s remit would span customer-facing content including website, microsite, and sitelet content, social content, partner, and dynamic email.

Impact Analysis
Impacted parties: content owners and managers, project and program owners, IA/UX, site developers, CMS support team.
Impact: Parties will need to participate in the policy-setting process and comply with the standards published.
Standards for: 1. Graphical/User Interface (UI), 2. Editorial, 3. HTML (and other markup), 4. Syndication 5. Taxonomy, 6. Content Review, 7. Archival and Disposition.

Benefits
Reduces the amount of learning, negotiation and redesign in new projects
Improves content integrity
Promotes content reuse and mulitchannel
Helps maintain a consistent brand
Gives business users a better grasp of technical capabilities and constraints
Makes new projects easier to implement and streamlines changes to existing content

Implementation Effort
New group to be assembled
Establish policies and standards
Build intranet Content Standards Visual Guide
Organizational units to learn, follow standards
Program to operate indefinitely

Content Governance Proposal

by Paul Mitchell on Nov 19, 2009

Accessibility

Categories

Upload Details

Usage Rights

Embed Views

Statistics

Content Governance Proposal — Presentation Transcript