WCXM Pitfall 3: Thinking a web content management package will provide a full CMS solution

  • 3-Apr-2014

Twelve Common Pitfalls to Avoid (and Best Practices to Follow) When Embarking on a Web Content and Experience Management Project

Pitfall 3: Thinking a web content and experience management package will provide a full CMS solution

Best Practice:

Model your existing and prospective CMS using building blocks of people, content, practices, and infrastructure.

Software is just one part of the infrastructure building block in your WCXM strategy. If your Content Management System is like most others, it will consist of 20 percent technology and 80 percent process.

This is actually good news. You can control and modify a system. You can't always control and modify packaged software as much as you would wish.

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.

Pitfalls 4-12: Coming soon...

Our customers say...

"As high-end web consultants, we use a variety of research tools to keep on top of the evolving technology platforms. Among these, Real Story Group is by far the best--a sort of bible for our CMS consulting practice. We've used The Web CMS Research both to get a jump on understanding products in advance of a formal CMS selection, as well as to start the conversation about potential partnerships. It's also great when a client asks you about an obscure product -- and you can get back to them within an hour with a grounded, thoughtful appraisal of the product, knowing that the information is accurate and written by analysts with real perspective."

John Berndt, President and CEO, The Berndt Group, Ltd.

Other Web Content & Experience Management posts