Twelve Common Pitfalls to Avoid (and Best Practices to Follow) When Embarking on a Web Content and Experience Management Project
Pitfall 6: Spending insufficient effort describing and organizing content, and underestimating migration times
Invest in mapping the structure of your content, "chunking" it, building workable taxonomies, and creating user-centric information architectures. Then clean your data.
Inadequate work up front in information design and mapping inevitably means leaving key architectural decisions to engineers or graphic designers. How will your news articles be linked to your product line? Technicians and designers have important things to say on that subject, but ultimately, it is a business-information decision.
Also, don't overlook migration. If you already have a website, you already have web content, and migration of some kind will be in order before re-launching with a new CMS. Most engineers quite properly view migrations of this sort like an extended trip to the dentist. Some CMS packages have migration wizards to import your existing HTML. Others employ scripts to do the same thing. Other, more complex migrations will require third-party tools.
Pitfall 1: Selecting a Web CMS package before developing solid requirements and a business case. Read the details of Pitfall 1 here.
Pitfall 2: Not getting a clear mandate from the top. Read the details of Pitfall 2 here.
Pitfall 3: Thinking a web content management package will provide a full CMS solution. Read the details of Pitfall 3 here.
Pitfall 4: Not involving internal Web CXM stakeholders from the very beginning. Read the details of Pitfall 4 here.
Pitfall 5: Involving only internal stakeholders. Read the details of Pitfall 5 here.
Pitfalls 7-12: Coming soon...