When I first started leading engineers, I thought my job was making decisions.
I don't believe that anymore.
I think leadership is mostly diagnosis.
Over the last decade I've worked in organisations that couldn't have been more different.
Large enterprises where every decision was cautious and deliberate. Startups where priorities changed every week. Businesses modernising legacy platforms. Businesses trying to rebuild confidence in struggling ones.
On the surface they had different architectures, products and technical challenges.
Underneath, they all shared the same problem.
Leaders would arrive with solutions before they'd properly understood the system they were walking into.
"We need OKRs."
"We need Agile."
"We need a platform team."
"We need to rewrite everything."
Sometimes those things helped. Often they didn't. Not because the ideas were bad. Because they solved the wrong problem.
Every organisation has a tide.
Some are coming in — building momentum, accumulating confidence, ready to move faster if someone gives them permission.
Some are going out — exhausted, overstretched, in need of someone who'll slow things down before they break.
The mistake is assuming the same leadership works in both.
Leadership isn't applying best practice. It's reading the tide well enough to know whether to swim with it, redirect it, or float until the conditions change.
I've watched leaders fight tides their whole tenure and never understand why they were tired.
That's why, whenever I join a new organisation, I spend the first few weeks asking questions instead of proposing solutions.
Not because I have a framework.
Because until I understand where the organisation's energy is, I don't know what problem I'm trying to solve.
Where do engineers and stakeholders see the same picture? Where do their views quietly diverge?
That gap is almost always where the real work starts.
Technology leadership has taught me that architecture is rarely what determines whether a transformation succeeds.
People are. Communication is. Trust is. Shared understanding is.
Technology is simply one of the tools we use to improve those things.
Platforms matter. Architecture matters. Technology matters.
But they're usually consequences, not causes.
The real work is helping an organisation understand itself well enough to move with confidence.
Everything else follows.
That's why I think leadership is mostly diagnosis.