Robertson identifies these mistakes to avoid:
1. Not understanding the problem to be solved
2. Not understanding content management issues
3. Assuming there are only a dozen possible products
4. Bigger is better
5. Not distinguishing between requirements and selection criteria
6. Writing too many requirements
7. ‘Complies’ / ‘does not comply’
8. Focusing on the ‘what’ not the ‘how’
9. Confusing the CMS project and the broader website project
10. Running the selection as a technology project
From my point of view, no. 10 is often the biggest mistake we see institutions making. Getting broader input from those who are expected to use the CMS is critical and, in general, speeds uptake on the part of users.
Michael Stoner Co-Founder and Co-Owner Was I born a skeptic or did I become one as I watched the hypestorm gather during the dotcom years, recede, and congeal once more as we come to terms with our online, social, mobile world? Whatever. I'm not much interested in cutting edge but what actually works for real people in the real world. Does that make me a bad person?