Home › Blog › IT Leadership

IT Leadership

When the Org Chart You Defended Turns Out to Be Wrong

We had to fold three separate reporting lines (infrastructure, InfoSec and support) into one unified function, and just eighteen months earlier I'd been the loudest internal voice arguing to keep them separate.

The business had changed underneath the old structure. Three separate leaders meant three separate priorities during every incident, and the customer never once cared which team owned the root cause. I had to walk into a room and reverse a position I'd defended publicly, in front of people who remembered exactly what I'd said the first time.

Ray Dalio's Principles has an idea I've quoted back to myself more than once: believing you're right is not the same as being right, and the data eventually gets a vote regardless of how confident you were. The reorg was the data casting its vote.

We made the change over real resistance, including some of my own residual pride. Eighteen months later, mean time to resolution on shared incidents had improved enough that nobody was arguing to go back.

Restructuring IT, InfoSec and support into one function at Verse Innovation taught me that the hardest leadership moves are the ones where you have to admit the org chart you built was wrong.

Signals your structure has outlived the business

  • Incidents stall on "whose problem is this?" before anyone works on the fix.
  • Teams optimise their own metrics while the customer-facing one gets worse.
  • The same escalation crosses three managers before anyone can decide.

Have you ever had to publicly reverse a call you'd defended just as publicly?

First shared on LinkedIn in November 2026. Join the conversation there.

organizational designIT org structurechange managementleadershipdecision making