Organisational Complexity Diagnostic...Understand the problem before investing in the solution.
When something isn't working, the natural response is to fix it, but what if the problem you're trying to solve isn't actually the problem?
Diagnose the Root Cause
Organisations are complex systems. Technology, processes, structures, incentives, behaviours, data and decision-making are interconnected — and problems that appear in one place can easily originate somewhere else.
A technology problem may actually be a process problem; a performance problem may be caused by unclear accountability.
A transformation problem may have less to do with delivery and more to do with competing priorities, governance or decision-making.
Before investing in another solution, sometimes the most valuable thing an organisation can do is understand what is actually happening.
The visible problem isn't always the real problem
Organisations naturally respond to the symptoms they can see:
- A process takes too long, so it gets automated.
- Reporting isn't trusted, so a new analytics platform is introduced.
- Teams aren't collaborating effectively, so the organisation restructures.
- A transformation programme is struggling, so additional governance is introduced.
- A technology platform isn't delivering the expected value, so attention turns towards replacing it.
Each response may be perfectly reasonable but if the underlying cause hasn't been understood, solving the visible problem can simply move the complexity somewhere else. Sometimes it creates even more…
The objective of a complexity diagnostic is therefore not to begin with a solution - it is to understand the system around the problem first.
Looking at the organisation as a system
Organisational problems rarely respect departmental boundaries and understanding what is happening may require looking across:
People · Process · Technology · Data · Structure · Governance · Decision-making · Incentives · Culture
Not every problem involves all of these.
The point is not to assess everything for the sake of it, it is to follow the evidence far enough to understand what is creating the outcome you're seeing.
That might mean talking to people across different levels of the organisation, examining processes and workflows, understanding technology and data flows, looking at how decisions are made or identifying where ownership and accountability become unclear.
The question throughout is simple:
Why is this happening?
Start with the problem, not the framework
Consulting engagements can sometimes begin with a predefined answer... a technology consultancy may naturally look for a technology solution... a software vendor may identify a platform requirement... a transformation methodology may frame the problem around the methodology itself.
I take a different approach.
The starting point is the problem as the organisation experiences it and that means:
- Listening to the people involved
- Understanding the environment around them
- Challenging assumptions — including the assumption that the organisation has correctly identified the problem in the first place...
There may be technology involved, there may be process change. There may be organisational or leadership questions, there may be several interconnected causes...
Or the solution may be considerably simpler than expected.
The diagnostic exists to find out.
Where I Can Help
Problem discovery
Understand the problem from multiple perspectives, including how leadership, teams and the people closest to the work experience it differently.
Organisational complexity mapping
Identify the processes, systems, structures, dependencies and behaviours surrounding the problem and how they influence one another.
Process & workflow analysis
Understand how work actually happens — including hand-offs, duplication, manual workarounds and processes that exist because "that's how we've always done it."
Technology & data
Examine where technology and information support the organisation effectively, where they create friction and where fragmented systems or data may be contributing to the problem.
Decision-making & accountability
Understand where decisions are made, who owns outcomes and where unclear responsibility, competing priorities or unnecessary governance slow the organisation down.
Root cause analysis
Separate visible symptoms from underlying causes and identify which issues actually need intervention.
Priorities & recommendations
Turn the findings into a clear set of priorities: what needs attention, what doesn't, what should happen first and where further investment may — or may not — be justified.
Not every problem needs a transformation programme
Complexity has a tendency to create more complexity:
A problem becomes a project, which creates governance, a governance that creates reporting, new technology is introduced and new processes are created around the technology.
Eventually… the organisation can spend more time managing the solution than solving the original problem.
That's why the objective isn't to produce the biggest possible transformation roadmap - it's to understand what needs to change and, just as importantly, what doesn't.
Sometimes the answer will involve significant change, sometimes it will require technology and occasionally it will mean simplifying a process, clarifying ownership, removing duplication or stopping something that no longer serves a useful purpose.
The right solution depends on understanding the problem first.
Start with what isn't working
You don't need to know the root cause before starting - that's what the diagnostic is designed to uncover.
Whether you're dealing with a transformation that isn't delivering, processes that have become unnecessarily difficult, technology that isn't creating the expected value, or simply an organisation that's become harder to operate than it should be, we can start with the problem as you experience it.
Understand what's happening, understand why and then decide what needs to change.
Start a conversation