The full title is What kind of problem is this? A Scrum Master’s field guide to using Cynefin in real team situations.
It is a practical book for Scrum Masters, Agile Coaches, Product Owners, delivery leaders and anyone who works with Scrum but has sometimes wondered why the same practices work beautifully in one situation and fall flat in another.
Most productivity advice assumes your work is simply a matter of getting organised.
Sometimes it is.
But sometimes the real problem is that you are using the wrong approach for the kind of work in front of you.
That is where Getting Things Done (GTD) and Cynefin work surprisingly well together.
Two useful lenses
GTD helps you decide what to do next.
Cynefin helps you understand what kind of situation you are in.
Put them together, and you get something more practical than either on its own.
GTD brings:
capture
clarify
organise
review
engage
A line drawing of the four regions of the Cynefin framework: Clear, Complicated, Complex, and Chaotic, plus the central unknown area Confusion. (Source: Wikipedia)
Cynefin brings:
clear (simple)
complicated
complex
chaotic
One helps with action. The other helps with sense-making.
When productivity is clear
Some tasks are straightforward.
You know what needs done. The steps are familiar. The next action is obvious.
Examples:
paying a bill
replying to a routine email
booking an appointment
Here, GTD works exactly as expected. Capture it, decide the next action and do it.
When productivity is complicated
Some work needs more thinking. You may need expertise, planning or research before you can move.
Examples:
choosing new software
preparing a budget
troubleshooting a technical issue
Here, GTD still helps, but the next action may not be ‘do the task’. It may be:
research options
ask an expert
compare approaches
draft a plan
Cynefin reminds you not to force immediate clarity where some analysis is still needed.
When productivity is complex
This is where many personal systems start to struggle.
Some parts of life cannot be reduced to a simple next action at the start.
Examples:
rebuilding your energy after burnout
deciding whether to change career
improving a difficult relationship at work
finding a sustainable way of working
These are not just tasks.
They are situations that unfold.
In the complex domain, progress often comes through:
small experiments
reflection
noticing patterns
adjusting as you go
That means the right next action may be something like:
have one honest conversation
try one small change this week
keep notes on what affects energy
test a new routine for five days
The goal is not to force certainty too early.
It is to create movement and learn from what happens.
When things become chaotic
Sometimes life stops feeling manageable.
Something breaks. A crisis hits. You are overwhelmed.
In that moment, you do not need a perfect system.
You need stabilisation.
Examples:
cancel non-essential commitments
ask for help
deal with the urgent problem
reduce incoming demands
Cynefin is helpful here because it reminds you that chaos is not the time for over-analysis.
First act to create enough stability. Then make sense of what comes next.
Why this matters
A lot of self-criticism comes from misreading the situation.
You think you are being lazy, disorganised or undisciplined.
But sometimes you are trying to use a clear-domain productivity method on complex or chaotic circumstances.
That will always feel frustrating.
GTD is still valuable. But Cynefin adds an important question: “What kind of situation am I actually dealing with here?”
That question can bring more realism, more compassion and often better decisions.
A more humane productivity practice
GTD helps you choose the next action. Cynefin helps you choose the right kind of response.
Used together, they can make personal productivity less mechanical and more humane.
When work feels messy, priorities shift, and people are pulled in different directions, Scrum’s regular events can look like admin overhead. But at their best, they do something more important than enforce process. They create coherence.
Scrum events are a shared rhythm
A good Scrum team does not rely on constant supervision. It relies on shared understanding.
But sometimes Agile itself becomes a way of avoiding reality.
When that happens, practices become rigid, language becomes moralistic, and teams are judged not by whether they are learning, but by whether they are following the ‘right’ process.
This is where Cynefin helps.
Cynefin reminds us that context matters. Not every problem is the same. Not every team needs the same response. And not every Agile practice fits every kind of work.
When Agile becomes dogma
Dogmatic Agile usually sounds certain.
It says:
every team must work this way
every backlog must look like this
every Sprint must follow the same pattern
every problem can be solved with better Scrum discipline
That kind of thinking can make people feel safe, because it offers clarity and control.
But it can also become blind.
When Agile turns into a rigid formula, it stops being adaptive.
What Cynefin brings back
A line drawing of the four regions of the Cynefin framework: Clear, Complicated, Complex, and Chaotic, plus the central unknown area Confusion. (Source: Wikipedia)
Cynefin asks a more useful question: what kind of situation are we in?
That question changes everything.
In the clear domain, standard practices and repeatable steps may work well.
In the complicated domain, expert analysis and judgement matter.
In the complex domain, you cannot rely on fixed answers. You have to probe, learn and adapt.
In the chaotic domain, you act first to create enough stability to make sense of what is happening.
Cynefin does not reject method.
It rejects the idea that one method fits every situation.
Why this matters in Agile teams
Many teams struggle not because they lack frameworks, but because they are applying the wrong kind of thinking to the work in front of them.
For example:
treating culture change as a process compliance issue
treating uncertainty as poor planning
treating experimentation as failure to decide
treating every deviation from Scrum as a sign of immaturity
These are not just mistakes in practice.
They are mistakes in sense-making.
Agile needs humility
Cynefin introduces humility into Agile.
It reminds us that:
some things can be standardised
some things need expertise
some things have to be explored
some things need immediate stabilisation before anything else
That makes Agile less ideological and more useful.
Instead of asking, “Are we doing Agile properly?”, a better question is “Given the nature of this situation, what approach makes sense here?”
A better kind of Agile
Cynefin does not weaken Agile. It strengthens it by returning it to its purpose.
Agile was never meant to be a belief system. It was meant to help people respond well to change, uncertainty and learning.
Used together, Agile and Cynefin can help teams become less dogmatic, more thoughtful and more responsive to reality.
