One of the most common mistakes in leadership, agile and productivity is treating complex work as if it were merely complicated.
The difference matters.
Complicated work can be analysed.
Complex work has to be explored.
If you confuse the two, you often make things worse.
What complicated work looks like
Complicated work may be difficult, but it is still knowable.
There may be many moving parts. You may need experts. It may take time to work through.
But with enough analysis, you can usually find a good answer.
Examples include:
- diagnosing a technical fault
- designing a bridge
- planning a database migration
In Cynefin terms, this is the domain where experts analyse, assess and advise.
What complex work looks like
Complex work is different.
In a complex situation, the answer is not waiting to be discovered through analysis alone. Cause and effect are only clear in retrospect. Human behaviour, changing conditions and emergence all play a part.
Examples include:
- introducing a new way of working in a team
- improving collaboration
- leading organisational change
- helping a team to rebuild trust after conflict
- responding to customer behaviour in a changing market
Here, the right approach is not “analyse and implement”, it is “probe, sense, respond”.
The hidden mistake
The mistake is easy to make.
When work feels messy, leaders often try to create certainty by adding:
- more planning
- more reporting
- more approval steps
- more control
That can help in the complicated domain.
In the complex domain, it often creates drag instead of clarity.
You do not get better outcomes by forcing certainty onto work that is inherently uncertain.
What to do instead
When the work is complex:
- run small experiments
- shorten feedback loops
- watch for patterns
- learn as you go
- adapt based on what emerges
This does not mean chaos.
It means using enough structure to support learning without pretending you can predict everything in advance.
Why this matters
Many teams are not failing because they lack effort.
They are struggling because they are using the wrong approach for the nature of the work.
Treating complex work as complicated leads to frustration, delay and false confidence.
A better question is not “How do we control this?” It is “What kind of work are we dealing with, and what approach does it need?”
That is where Cynefin becomes practical.
