Is your CMS really to blame?
Oct 14, 2013
How do you know if you really need a new CMS or if you just need to optimize the platform you have? Oshyn’s VP of Services, Christian Burne, explains how companies can end up in a cycle of replacing their content management systems more often than they should because they think the platform is “bad” instead of the usual problem, the users.
Video Transcript:
Christian Burne, Oshyn: “If customers already have a content management platform, typically the problem is that they have too much content and are disorganized, people don’t know how to use the tools correctly, there’s not enough governance over the platform. When the initial implementation happens of the content management system, most of the focus is on probably the primary goal is the redesign of some external-facing website or mobile platform and they are trying to gain the efficiency by putting the tools in place. But buying the tool, purchasing it, getting server set-up, getting all the technology put in place are all sort of the prerequisites and that ends up taking precedence over the higher value things of creating governance, creating the organization, making sure that people are trained correctly. When those things get left behind, you have a situation where the customers have these things in place but it’s not well used they are actually not gaining those efficiencies that they wanted to get out of. And I’ve seen a lot of times where customers come to us and say, ‘oh our content management system isn’t working for us. We need to get rid of it and get a new one’ but really the problem isn’t that the tool is bad, the problem is that no one is trained on it, they don’t have the proper full-time employees in place to manage it in order to actually take advantage of the software they purchased. And I’ve actually seen them go and purchase another one too and then do another re-implementation which is half a million dollars or something like that and the same problem happens again.”
Related Insights
-
Oshyn
-
Esteban Bustamante
Transition Sites to AEM Using Bulk Importer
Migrate Assets into AEMaaCS
-
Prasanth Nittala
Netlify and Vercel Alternatives
Using Native AWS Services For Headless Website Hosting in XM Cloud
-
Leonardo Bravo
The State of CI/CD Report 2024
DevOps Expertise Blossoms with Experience
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.