Most leaders who inherit an underperforming technical organisation reach for the same instrument: the wrecking ball. Reorganise the teams. Rip out the stack. Replace the people. Start again. It feels decisive, and it is almost always the most expensive mistake available to you.
The world-class organisation you want is not somewhere else, waiting to be hired in. It is already latent in the one you have. Michelangelo said the sculpture was complete inside the block of marble before he ever picked up a chisel. "I just have to chisel away the superfluous material." That is the right way to think about a technical organisation. Your job is not to import a great team. It is to uncover the one hidden in the people, the systems and the potential you already own.
The wrecking ball is the expensive option
Demolition feels like leadership. It rarely is. When you tear an organisation down to its foundations you throw away the one thing that is genuinely hard to buy: the accumulated knowledge of how your systems actually behave, why past decisions were made, and where the real risks are hiding. You also tell every talented person who stays that nothing they built mattered.
And here is the part that catches people out. I have been brought in after exactly this. New names on the org chart, a fashionable new stack, and the same three problems six months later, with nobody left who could explain why the old system was built the way it was. The shiny new team quietly reproduces the old dysfunction, because the conditions that created it were never addressed. You pay an enormous price to relearn your own lessons. Reshape before you replace.
Start with why, not with the org chart
Most reorganisations begin in exactly the wrong place: with boxes and reporting lines. Structure is the last thing you should touch, not the first.
Begin instead by establishing a shared destination with the people who matter, and do it in a way that is subtle and politically sensitive, because you are asking people to change. Begin with the why before the what: the right thing to build, in the right way, for the right reasons. Clarity is the first gift a leader gives, and it does more work than any reorg.
Intelligent people are remarkably good at organising themselves once they understand the objective and agree on how to reach it. Give them that clarity and their effort all points the same way instead of scattering. Withhold it and you get silos, politics and motion without progress. Making the hard calls that set direction under real uncertainty is the actual work of leading.
Then look honestly at what you've got
Only now do you audit, and the audit has to be unflinching. The status quo of the technology, yes: the architecture, the tech debt, the tooling, the methodologies, the way you measure and report. But that is the easy half, and it is the half most leaders stop at.
The harder, more revealing half is the foundations. Your teams, your people and your culture. Your recruitment and your progression paths. How decisions actually get made when things are uncertain. The technology is where the symptoms show. The foundations are where the performance actually comes from. If you only audit the stack, you will fix symptoms and wonder why the deeper problems keep growing back.
The five things that actually decide it
When people ask what separates a world-class technical organisation from a mediocre one, they expect the answer to be about process: the right SDLC, the right methodology, the right delivery framework. All useful. None of them foundational.
The factors that actually decide it sit a couple of levels above all that. People, Leadership, Culture, Problem-solving and Creativity. Not five boxes to tick. They are interconnected, and they compound: improve one and the rest gain, weaken one and they all weaken. That is the destination, the shape you are chiselling towards.
Two of them do most of the work. Culture, because the best people only perform when they feel safe enough to. And leadership, because it is usually the binding constraint, the factor that decides whether all the others get to count. After twenty years I am convinced the engineering is rarely the hard part.
Change without stopping the bus
Here is the constraint nobody escapes. You do not get a clean slate, a bigger budget, or permission to halt delivery while you rebuild. The business keeps running, the roadmap keeps moving, and your people are watching to see whether the change is done to them or with them.
So transformation has to be incremental and non-disruptive. You protect continued delivery and staff wellbeing at the same time as you reshape. You make one improvement, review the result, make the next: kaizen, never finished, always moving. You do as much as you can with what you have, and you aim for world-class anyway. Done this way, the change earns trust rather than provoking fear, because people can feel the thing getting better while they are still carrying the load.
Give your curious people a remit
One part of the destination is not optional any more, and it is usually already in the building, waiting to be uncovered. You almost certainly have people who are quietly curious about what is coming next, reading about it on their own time. Give them a remit. A small, explicit function whose job is the future: experimenting with emerging technology and watching where it is heading.
Without it you spend your life receiving requirements and reacting to change after it has already hit you. With it you co-shape your own direction and you are in position when the opportunity arrives. AI is the obvious case. Every organisation has to be ready for its impact, and the ones that made deliberate experimentation a habit will harness it while the rest are blindsided.
The work is never quite done
There is a reason this is continuous rather than a project with an end date. Left alone, every organisation drifts back towards disorder. Silos reform, clarity fades, the energy you aligned starts to scatter again. Keeping an organisation in a coherent, high-performing shape takes constant, deliberate effort, the way a sculptor keeps refining rather than declaring the work done.
That is the job. Not one dramatic act of demolition and rebuild, but the patient, ongoing work of chiselling away what does not serve the vision and protecting what does. The best technical organisation you will ever lead is almost certainly hidden inside the one you have right now. You just have to uncover it.
If you are staring at a technical organisation that is underperforming and wondering whether you need to tear it down and start over, you almost certainly do not. I am always happy to compare notes on how to reshape the one you have. Let's talk.
Related: The best technology rarely wins. The best-led team does · After 20 years as a CTO, the engineering was the easy part · NHS Wales: transformation at national scale
