This is the first post in a short series exploring the Scrum Master role through the four main Cynefin domains:
- clear
- complicated
- complex
- chaotic
Cynefin is useful because it reminds us that not all work is the same.
Some work is uncertain and needs experimentation.
Some work needs expert analysis.
Some work is urgent and unstable.
But some work really is straightforward.
In the clear domain, the relationship between cause and effect is obvious. The work is familiar, repeatable and well understood.
For Scrum teams, this matters.
Not every issue needs a workshop.
Not every decision needs deep discussion.
Not every task needs to be treated as complex.
Sometimes, simple rules help.
What clear work looks like
Clear work is work where the team already knows what good looks like.
It may include:
- routine support work
- release checklists
- agreed definitions
- simple workflow rules
- recurring admin tasks
- maintenance activities
- repeatable technical checks
This kind of work benefits from standardisation.
The aim is not to remove thought from the process. The aim is to avoid wasting energy on things the team has already understood.
Why this matters in Scrum
Scrum is often used for complex product work.
That does not mean every part of the team’s work is complex.
A Sprint may include discovery, uncertainty and difficult trade-offs. It may also include repeatable tasks that simply need to be done well.
For example:
- updating documentation
- preparing a release
- checking acceptance criteria
- reviewing accessibility basics
- applying a Definition of Done
- triaging known support requests
- following an agreed deployment process
Treating all of this as complex can slow the team down.
It can lead to unnecessary debate, repeated decisions and meetings that add little value.
The Scrum Master’s role
In the clear domain, the Scrum Master helps the team notice what can be simplified.
This may mean helping the team:
- identify repeatable work
- agree simple working rules
- create lightweight checklists
- clarify definitions
- reduce unnecessary discussion
- make routine work visible
- improve consistency without adding bureaucracy
The Scrum Master is not there to impose rigid process.
They are there to help the team decide where a simple process would make life easier.
Checklists are not the enemy
In some agile environments, checklists can be treated with suspicion.
They can sound controlling, bureaucratic or old-fashioned.
But a good checklist is not a command-and-control tool. It is a memory aid.
It helps the team avoid missing obvious steps, especially when people are busy, tired or distracted.
Useful checklists are:
- short
- visible
- easy to update
- owned by the team
- used only where they genuinely help
A release checklist, for example, can reduce stress. It can help the team move through a familiar process without relying on one person’s memory.
Avoid over-discussing obvious work
One useful Scrum Master skill is knowing when not to facilitate.
Not every topic needs a collaborative workshop.
Not every minor decision needs the whole team.
Not every recurring issue needs to be reopened from first principles.
Sometimes the helpful intervention is to ask:
“Have we solved this before?”
Or:
“Do we already have an agreed way of handling this?”
If the answer is yes, the team may simply need to follow, improve or refresh the existing approach.
The risk of over-standardisation
The clear domain is useful, but it has limits.
Standardisation becomes harmful when it is applied to work that is not actually clear.
A checklist cannot solve an unclear product direction.
A workflow rule cannot remove genuine uncertainty.
A definition cannot replace conversation where judgement is needed.
The danger is assuming that because some work can be standardised, all work should be standardised.
That is where teams become rigid.
The Scrum Master needs to help the team distinguish between:
- work that is repeatable
- work that needs expert judgement
- work that needs experimentation
- work that needs urgent action
Clear work deserves simple rules.
Complex work does not.
A practical question for Scrum Masters
A useful question for the Scrum Master is “What are we repeatedly discussing that could safely become a simple agreement?”
The answer might become:
- a checklist
- a working agreement
- a Definition of Ready
- a Definition of Done
- a support triage rule
- a release preparation step
- a recurring admin habit
The goal is not to create more process.
The goal is to free the team’s attention for the work that genuinely needs thought.
Simple rules can create space
In the clear domain, good Scrum Masters help teams reduce friction.
They help the team avoid unnecessary complexity. They make routine work easier to complete, easier to explain and easier to improve.
Simple rules are not a retreat from agility. Used well, simple rules create space for agility. They protect the team’s attention for the work that really is uncertain, creative and complex.
Photo by Kelly Sikkema on Unsplash
