Insight:

4 Lessons for CMS selection, governance and implementation

Author
Gijs Edelbroek
Date updated
October 6, 2025
Reading time
7
mins read
Over the last few weeks, I’ve shared a series of 4 out of 8 stories from my 20+ yrs career in digital. Each with a lesson you can use when you are planning to replace your ‘legacy’ CMS.

Lesson #1 - Not every shiny new feature delivers value.

In 2001, I joined Tridion - the “cool new product” in content management. We quickly signed most large Dutch enterprises and government organisations.Over time, the company added products (Email marketing, webforms, …) to become a DXP. And the truth? None of those add-ons delivered real value to clients.

Lessons I’ve learned:

  • Focus on the core capabilities of a software vendor.
  • No platform is the best at everything.
  • Promised integrations rarely live up to the hype.
  • When focus drifts, innovation on the core slows down.

Lesson #2 - Don't underestimate content management

In 2006, I moved to Dubai to work for Emirates Airline - launching new country websites every month. We handed content management to local marketing teams. It seemed empowering… until it wasn’t. Inconsistency, broken workflows, and brand drift followed. Not because the teams weren’t capable, but because they weren’t trained, frequent CMS users. 

Lessons I’ve learned:

A CMS is never simple if you’re not a digital native. For global brands, centralising operations with a trained, multilingual team keeps quality, tone, and brand intact, while still working closely with local markets.

Lesson #3 - The best software can still deliver the worst results.

After Emirates, I co-founded a digital agency Indivirtual Dubai, designing and building websites. Many prospects had platform implementations (CMS, Commerce, ….) that were almost unmaintainable. The reason? They’d been built by partners without the right skills or experience.

Lessons I’ve learned:

  • All software is only as good as the people who implement and maintain it.
  • Choose implementation partners who have done it before.
  • Demand experience and certification with your chosen vendor.
  • Have a plan to upskill your own team and onboard them to the codebase

Lesson #4 - The three most expensive words in platform projects? “Can we just…”

At first, it seems harmless. But tweak by tweak, a clean, standard setup turns into a tangled custom build (broken upgrades, development slows down, higher costs, ...). And suddenly, the platform that was meant to accelerate you becomes unmaintainable.

Lessons I’ve learned:

  • Keep your platform close to standard.
  • Use out-of-the-box for the 80%.
  • Only customise when it creates real business value.
  • Always weigh the cost of tomorrow’s maintenance against today’s preference.

Get started

Unsure whether headless, composable or a DXP is right for you?

Book a sparring session. In just 60 minutes we’ll uncover whether your challenge lies in the software, or in implementation, governance or adoption and what you can change tomorrow.

Reach out to us
Reach out to us
Arrow icon