5 Reasons CMS Projects Will Typically Fail
01/22/2007 4:32:57 PM
I've been in this business a long time and have seen a lot of companies implement and use their CMS successfully, but unfortunately this is not always the case:
5. You'll pull a Frankenstein: You'll attempt the unholy
mix of document management, business process management, e-commerce, and web publishing. Each solution is for different projects and teams with different requirements.
4. You'll make a token gesture at training:
You won't train the end-users well. You won't create a custom how-to
manual for your project to use for new users over time. You won't have
somebody to answer user questions and help them when they paste something
nutty into a form and break a page. And - your people will hate the
CMS.
3. Your UI will be poor. And nobody will use it. Open
source systems are notorious for poor/inflexible interfaces.
2. You
will launch a system based on requirements and not change it based on user
feedback after launch.
1. You won't have a service to make system
modifications after launch. Every time you need a new type of page, a new
layout, a change to workflow, a simple integration, somebody needs to modify
the system. Have a service or have a CMS that stinks to high heaven within
12 months.
I challenge you to not make these mistakes, but beyond that let me know what you think or if you've experienced other challenges in your CMS implementations.
Jim Howard
CEO
trackback:
