No user involvement = disaster

Recipe for a CMS disaster.

InfoWorld has published a case study of a CMS disaster, caused by a lack of author involvement in the project. To quote:

The new system I was developing would be an improvement, but I knew it would take time for our users to become productive in the new environment — and they were not known for their patience. I was particularly worried because our project plan didn’t include any opportunity for interaction with the users.

Some of these problems could’ve been resolved through the use of requirements captured in a narrative format, along with supporting scenarios. But as indicated in the article, user involvement throughout the project is critical.

[Thanks to CMS Watch.] [Column Two]