The CMS Demo Myth
Selecting a new web content management system can be a long process full of internal politics, vendor negotiations and pushy sales types.
The coveted CMS demo is one of the lone bright spots in the journey. It can hold all the anticipation of Christmas morning for web teams anxious to get beyond piles of RFP documentation to finally see some enterprise software in the wild.
The CMS vendor will typically have a sales representative and a sales engineer presenting a walk-through of the software to the end client. More formal selection engagements may have an agreed-upon script with specific scenarios and a room full of end users, executives and technical stakeholders.
This is a very important event for vendors who don’t get many shots to present in front of the extended team. It’s well known in the CMS world how much weight the demo carries and how important first impressions of a user interface can be.
I met with a prospective client a few weeks ago who had discounted a perfectly well suited CMS platform because he didn’t like the initial high-level demonstration.
While it’s a necessary step in the process, the myth lies in the overinflated value placed on the demo in the decision making process.
Platforms can be voted on or off the island for subjective reasons, and the vendors often come unprepared to address core requirements. The larger the group the more the demonstrations get blown off course with questions that matter very little in the overall evaluation process.
Independent CMS consultants often boast about getting vendors off their script, but demos on autopilot are only a small part of the problem. Companies simply put too much stock in the demo itself as part of the decision making process and in turn underinvest in researching the areas that really matter.
I’ve watched selection processes unfold where the team gets a matrix to fill out after each demo and the tabulated scores from the team carry the most weight in the final decision. It’s a dangerous way to pick a platform where success comes down to factors that can’t be uncovered in a 90-minute point and click demonstration.
Platforms are evaluated on ease of use, but usability can be in the eye of the beholder and the slickest interfaces aren’t always best equipped to handle unique requirements. The stakeholders responsible for the final judgment are also often disconnected from the requirements and overall strategy.
All of this contributes to what we call the CMS Selection Myth where organizations rush into technology selection and forgo the strategic planning actually necessary for success.
Once an organization is well prepared for a technology selection process, getting a first-hand look at a new CMS in a demo is vital. But it shouldn’t replace or outweigh even more important steps in the process. These include:
- Talking with end users who recently went through an implementation with the platform
- Meeting with integration partners who work with the solution frequently
- Finding organizations that have switched off the platform and understanding the reasons why
- Sending developers to vendor training to get hands on with the platform
- Developing an implementation plan and high-level system architecture based on your actual needs
- Conducting a proof of concept with the chosen CMS (or a few finalists)
Kicking the tires on new platforms can be fun, but getting a ‘CMS lemon’ has little to do with how much the team likes or dislikes the WYSIWYG editor.