Back to homepage

Our favourite eggs to break · 01

ITSM & CMDB transformation.

Most organisations don't set out to have four service desks and a CMDB nobody believes. It happens one sensible decision at a time, until the estate costs a fortune, the data is quietly ignored, and every change to it feels too risky to attempt.

Sound familiar?

  • Several ITSM tools doing broadly the same job, each with its own loyal following and its own licence renewal.
  • Years of customisation that nobody fully understands, which makes every upgrade a project in its own right.
  • A CMDB that's expensive to run but out of date, so when something breaks, people ask the person who “just knows” instead.
  • Discovery tools that find thousands of things, but nobody can say which business services they support.
  • Reporting that takes days of spreadsheet work because the data lives in five places and agrees in none of them.
  • A replacement programme that has been “next year’s priority” for three years running.

Why it happens

Tool sprawl rarely comes from bad decisions. It comes from mergers, from teams solving their own problem fast, and from vendors who were very good at selling into one department at a time. Each tool made sense when it arrived.

The CMDB problem is usually the same story. It gets populated in a burst of enthusiasm, nobody owns keeping it right, and trust erodes faster than data can be fixed. Once people stop believing it, they stop using it, and once they stop using it nobody notices it decaying. Questioning it feels like reopening an old argument, so the egg stays unbroken.

What it's really costing you

  • Licence, support and hosting spend on overlapping platforms.
  • Slower incident resolution, because impact and ownership have to be worked out by hand every time.
  • Risky changes, made without a reliable view of what depends on what.
  • Audit and regulatory findings that trace back to configuration data you can't evidence.

How we break this egg

  1. Map what's really there

    Every tool, integration, customisation and owner, and what each one is actually used for day to day, not what the original business case said.

  2. Decide what the CMDB is for

    Start from the decisions it needs to support (incident impact, change risk, cost, compliance), then scope the data to match. Less, but trusted, beats everything, but ignored.

  3. Build the consolidation case

    A clear, costed recommendation on which platforms to keep, retire or merge, with the trade-offs made explicit so leadership can actually decide.

  4. Plan the move and stay for it

    A phased migration and data-ownership model your teams can run, with hands-on support through vendor selection and delivery if you want it.

Tell us about your egg.

What's stuck, and what's been “done that way” for too long? We'll come back to you within one working day.