Scrum Masters and Cynefin – when the team needs expertise

This is the second post in a short series exploring the Scrum Master role through the four main Cynefin domains:

  • clear
  • complicated
  • complex
  • chaotic.

The first post looked at the clear domain, where simple rules, checklists and repeatable practice can help.

This post looks at the complicated domain.

What is the complicated domain?

Hand-drawn Cynefin framework diagram showing four domains around a central area of confusion: complex, complicated, chaotic and clear, with each domain labelled with its constraint type, response pattern and practice type.
A line drawing of the four regions of the Cynefin framework: Clear, Complicated, Complex, and Chaotic, plus the central unknown area Confusion. (Source: Wikipedia)

In the complicated domain, the work is not obvious, but it is still knowable.

There may be more than one right answer. The team may need analysis, diagnosis or specialist input before deciding what to do.

This is the world of expertise.

Continue reading Scrum Masters and Cynefin – when the team needs expertise

A moment of deliberate non-intervention

Sometimes the most important thing a Scrum Master does is not visible.

They do not interrupt.
They do not rescue.
They do not explain.
They do not tidy up the conversation too quickly.

They wait.

Not because they are passive.
Not because they are unsure.
But because the team may need the space to work something out for themselves.

Continue reading A moment of deliberate non-intervention

Scrum Masters and Cynefin – when simple rules help

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.

Continue reading Scrum Masters and Cynefin – when simple rules help

The Scrum Master’s hardest skill is knowing when not to act

Scrum Masters are often expected to help.

They notice tension.
They see confusion.
They spot inefficient conversations.
They recognise patterns before the team does.

So the temptation is obvious: step in, explain, fix, smooth, coach or redirect.

Sometimes that is exactly what is needed.

But sometimes the most helpful thing a Scrum Master can do is pause.

Continue reading The Scrum Master’s hardest skill is knowing when not to act

When rhythm matters more than velocity

Previously, I argued that Scrum events create coherence, not control.

This is where that idea becomes practical.

Because there are moments in team life when speed is not the real problem. The real problem is loss of rhythm.

The team is busy. Work is moving. People are under pressure. But the usual patterns that help everyone stay aligned have started to break down.

Conversations become reactive.
Priorities shift too often.
Decisions happen too late or in the wrong place.

In those moments, trying to speed up usually makes things worse.

What helps is restoring rhythm.

Continue reading When rhythm matters more than velocity