Defining roles and responsibilities


The scope and complexity of the project will determine how many people are involved. At a minimum, you need to make sure that the following roles are covered:

  • Education
  • Development
  • Review
  • Approval

The education role is responsible for getting buy-in from all affected parties—especially managers who approve the effort and staff who will use the new system. Depending on the audience, you may use different approaches, such as presentations, informal discussions, and training.

If consultants are involved, they will most likely do the development work and then present it for your review and approval. There may also be an internal review on the consultant’s side before you see any deliverables.

For larger projects, there is often a development team. For example, one person might be responsible for establishing taxonomy (element and metadata definitions), another for choosing and installing a content management system, and a third for creating output transformation stylesheets.

Our consulting practice uses a collaborative approach. We strive to identify or develop technical expertise on the client side as early as possible so that our clients can provide meaningful reviews and feedback as we build their systems. By combining our clients’ business requirements and expertise in their own subject matter with our consultants’ understanding of content strategy and publishing technologies, we can deliver a final product that improves on what either of us could do on our own.

Working on implementation and review teams will require significant time commitments from the participants. Any realistic resource plan must take into account other commitments, deadlines, and deliverables that could conflict with project requirements.



Add comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.