Content management no image

Published on December 3rd, 2005 | by Rahel Bailie


How can content management projects go wrong: let me count the ways

How many ways can a content management project go wrong? At the CM Professionals Canada West chapter meeting, panelists discussed thirteen ways a project can get derailed, including purchasing the software before determining the requirements, foregoing a project plan, underestimating the project scope (easy to do when there are no requirements), and ignoring the people who will be using the system after its integration.

Identifying what not to do is obviously a popular learning tool for what to do. There was enough interest in the topic that I think we should make this an annual event.

Share this post:
These icons link to social bookmarking sites where readers can share and discover new web pages.

  • StumbleUpon
  • email
  • Facebook
  • LinkedIn
  • TwitThis

About the Author

Rahel Anne Bailie is a synthesizer of content strategy, requirements analysis, information architecture, and content management to increase the ROI of content. She has consulted for clients in a range of industries, and on several continents, whose aim is to better leverage their content as business assets. Founder of Intentional Design, she is now the Chief Knowledge Officer of London-based Scroll. She is a Fellow of the Society for Technical Communication, she has worked in the content business for over two decades. She is co-author of Content Strategy: Connecting the dots between business, brand, and benefits, and co-editor of The Language of Content Strategy, and is working on her third content strategy book,

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Back to Top ↑