Gilbane Boston & planning for a CMS
Another Gilbane conference has come and gone and the Mythbusters were once again in the middle of the action to get firsthand insight.
In fact, we’re just now gathering our thoughts from a whirlwind three days of keynotes, panels, hallway conversations and the trade show floor.
I have to admit, it feels a little bit like the movie Groundhog Day going to this show every year. Similar vendor set, familiar formats and the same core challenges around CMS. Perhaps in 10-15 more years I’ll have this CMS bit figured out just as Bill Murray’s character became a master pianist in Punxatawney.
A highlight of the show for me was being on the “Planning for a CMS” panel with Gilbane’s Tony White and Nathan Williams, the Interactive Director for the City of New Orleans. This was extra special because New Orleans was a project we all worked on together from CMS evaluation to strategic planning to implementation (launching soon!). It’s a remarkable story that I hope to be sharing about in more detail after the launch.
For now, I’ll share some highlights from the panel. Without giving a blow by blow of the presentations, I’ll recap a few of the audience questions.
What exactly does ‘out of the box’ mean with CMS features?
Great question and a slippery slope indeed. Tony cautioned that some vendors will blur the lines in demos between core functionality and add ons that have been developed as ‘demoware’ (or by third parties). It’s essential for folks evaluating vendors to know what’s core to the product and what’s not. It will affect your implementation and your upgrade path.
Is a long RFP format even useful for picking the right CMS?
There is nothing like curling up with a good 100-page RFP response on a Friday night, right? Ok maybe we need to get out more. Tony shared with the panel that if done right, an RFP can be a useful part of the process. However, he also advised to provide vendors with specific scenarios to focus the demos on, and challenge them to provide real explanations of how their product meets your needs – not simply yes/no checkboxes. He’s seen RFP responses ranging from 12 to 100+ pages and faults the vendors for not having better internal processes to deliver meaningful responses.
Are all of the user experience deliverables done before development starts?
My presentation walked through our process for user experience planning with CMS including the information architecture, template library, content requirements and more. While there are many different approaches, we almost always advise that the core UX deliverables are done up front and used to help gain alignment between the technical and business teams. With that said, some rapid prototyping early in the process can help for certain types of projects.
How do you justify the value of user experience inside an organization?
This is an entire post (or book!) in itself. In general, I usually advocate that what’s good for your users is good for business. Meaning if you can increase the effectiveness of finding information and completing transactions, there are real bottom line impacts. Beyond that, smart CMS user experience planning can reduce maintenance costs and create a site structure that can scale with your business. If you flip the question around, it’s scary to think of what it will cost the organization to not focus on creating great experiences.
Those are a few of the highlights from the panel discussion. It was a great crowd and one of the better panels I’ve been a part of. Stay tuned for more thoughts from Gilbane.