Today, we publish the Forrester Wave™: Web Content Management Systems, Q1 2017 after three months of research and another month of writing and editing. Today, we can step back and begin to help our clients leverage this research to shape their digital experience strategy. But first, a special thank you to my colleagues Danielle Geoffroy, Allison Cazalet, Stephen Powers, and Ted Schadler for their invaluable contributions. Also, thank you to the 15 vendors -- Acquia, Adobe, Crownpeak, Episerver, e-Spirit, Hippo (BloomReach), IBM, Jahia, Magnolia, OpenText (TeamSite), OpenText (WEM), Oracle, Progress Software, SDL, and Sitecore -- and their client references who made this research possible.
So where to start? At the highest level, we’re witnessing a step-function along our evolutionary journey thanks to digital. Digital disrupts communication, community, privacy, convenience, products, and services because always-on connections change our demand cycles. Those enterprise organizations who don’t evolve are being disrupted. My colleagues on customer experience research team have shown this correlation of revenue being tied to customer experience, across industries and geographies (link). Additionally, we’re starting to understand how digital maturity stages correlate to technology priorites such as Web CMS with Forrester's Digital Maturity Model (link):
I’m sitting on my sofa at home (Yes! Home!) on Sunday morning just before Christmas. I’m “shut down” for the holidays now, but of course, I’m watching Twitter and now listening to my brilliant friends Chris Dancy and Troy DuMoulin discussing CMDB (configuration management database) on the Practitioner Radio podcast. It’s a marvelous episode, covering the topic of CMDB in with impressive clarity! I highly recommend you listen to their conversation. It’s full of beautiful gems of wisdom from two people who have a lot of experience here – and it's pretty entertaining too!
I agree with everything these guys discussed. In particular, I love the part where they cover systems thinking and context as the key to linking everything conceptually. I only have one nit about this podcast, and the greater community discussion about CMDB, though. Let’s stop calling this “thing” a CMDB!
I coauthored a book with the great Carlos Casanova (his real name!) called The CMDB Imperative, but we both hate this CMDB term. This isn’t hypocritical. In fact, we make this point clear in the book. Like the vendors, we used CMDB to hit a nerve. We actually struggled with this decision, but we realized we needed to hit those exposed nerves if we were going to sell any books. Our goal is not to fund a new Aston Martin with book proceeds. If so, we failed miserably! We just wanted to get the word out to as many as possible. I hope we've been able to make even a small difference!