Most software organisations are full of talented, hard-working people doing exactly what's expected of them. The developers care about the code. The product managers care about the roadmap. Leadership cares about delivery.
And something still isn't right.
Products ship late, miss the mark, or quietly accumulate technical debt that makes every future feature slower and more expensive. You've probably tried to fix it. Hired people. Possibly run a transformation. The ceremonies ran. The status reports looked fine. The underlying problems stayed — and then surfaced somewhere else.
Here's why: good people, doing their best, inside a system they didn't design. What each person sees, reports, and acts on is shaped by where they sit and what they're measured by. By the time the picture reaches the top, it's passed through every lens in the organisation — each one honest, each one partial.
You can feel the gap. You can't see the source from where you stand.
The real issues live in the friction between business goals, organisational structure, and technical reality. They cause each other. And they're hardest to see from inside the system generating them.
I've spent 35 years at every level of that chain — developer, architect, team lead, CTO. I still write production code. That means I can sit with your developers and hear what they're not saying in the status meeting. I can read what your codebase says about the decisions that have been made. And I can have an honest conversation with the people who have the authority to act on what I find.
Then I stay — not to create dependency, but to remove it. Working with the people inside who will carry this without me. No master plan. Small, incremental experiments — safe enough to try, visible enough to learn from, honest enough to stop when they're not working. No long-term contract. No minimum commitment.
The goal is to make myself unnecessary. The diagnosis comes first. Always.
