Here’s another management term, but this one bears examination.

Organisational engineering.

It’s not a phrase you hear very often. When you do, it’s usually describing the design of organisational structures or operating models. But I think there’s another interpretation that’s worth exploring. To me, organisational engineering isn’t about designing organisations from scratch. It’s about understanding the one that already exists. Not the version described in a policy document or process map, but the one that has evolved over years through people, habits, spreadsheets, workarounds and decisions. Before you can improve an organisation, you first have to understand it.

I’ve become increasingly convinced that this understanding comes from observation rather than intervention. Throughout my career, whether as a director in the private sector or leading transformation work in the public sector, the greatest improvements I’ve seen haven’t come from introducing a new methodology or buying a new system. They’ve come from taking the time to patiently observe how work really flows through an organisation, setting aside assumptions and allowing the evidence to tell its own story. That approach helped us improve profit margins, increase the accuracy of our quotations and exceed our post-pandemic turnover targets. None of those outcomes were achieved by chasing the numbers directly. They came from understanding the organisation well enough to improve the system that produced them.

That patience is harder than it sounds. We are conditioned to solve problems quickly. We hear about an issue in a meeting and immediately begin forming opinions about the cause and the solution. Organisational engineering asks us to do almost the opposite. Suspend judgement. Accept that the organisation is behaving exactly as it has been designed to behave, whether intentionally or otherwise, and become curious enough to understand why.

When I start working with an organisation, I rarely begin with workshops or process maps. I begin by following the work. I follow an invoice from beginning to end. I trace how a customer request becomes an operational task. I look at how decisions are made, where information changes hands, which spreadsheets people quietly rely upon and where knowledge exists only in someone’s experience rather than within the organisation itself. Every one of those observations is a clue, and over time those clues begin to reveal patterns that nobody can see when they are standing inside the system every day.

Those patterns are rarely dramatic. More often they are small inconsistencies that repeat themselves. A process that depends on one individual remembering to do something. Two teams who both believe they own the same activity. A report that exists because nobody trusts the system. A manual adjustment that has become so routine it is no longer questioned. Individually they seem insignificant. Collectively they explain why the organisation behaves the way it does.

Eventually something changes. The organisation becomes understandable. Once that happens, improvements stop being based on opinion and start being based on evidence. Governance becomes easier because ownership is clearer. Decisions become more consistent because knowledge has moved from individuals into the system. Risks become visible because they no longer hide within assumptions. And occasionally, something emerges that nobody expected to find at all.

That, for me, is the essence of organisational engineering. It isn’t about fixing organisations. It is about understanding them so well that the right improvements become difficult to ignore.

Perhaps the most valuable management skill we can develop isn’t the ability to solve problems quickly. Perhaps it’s the discipline to observe patiently enough that we solve the right ones.