You keep circling the same conversation
There is plenty of analysis, but decisions are repeatedly deferred, reopened or handed elsewhere.
Facilitation sprints · 4–6 weeks
Facilitation sprints: ready to actually get stuff done?
A sprint gives a cross-functional team the structure, pace and protected space to untangle a complex problem, test practical solutions and make the decisions that keep getting deferred.
4–6weeks
One focused, cross-functional rhythm from problem to tested change.
What is a facilitation sprint?
More than a series of workshops. Less than a drawn-out transformation programme.
A sprint is a focused, time-bound way of creating movement around an adaptive challenge.
It is not a single methodology or simply a faster project plan. It creates a temporary structure in which a team can step outside its normal rhythm, examine the whole system and test decisions while the work is still live.
I join the team for a concentrated period, hold the overall process and help people move repeatedly between understanding, making, testing and deciding.
The pace matters, but speed is not the point. The aim is to shorten the distance between a useful insight and doing something with it, without flattening complexity or leaving quieter perspectives behind.
Good enough to test
beats perfect on paper.
When a sprint helps
For challenges that will not be solved in one good workshop.
A sprint is useful when the issue crosses teams, the current process has become slow or nobody has enough space to look at the whole system.
The process has too many hand-offs
Different functions own small parts, while nobody can see or improve the whole.
You need to test before committing
The answer cannot be designed perfectly on paper. It has to meet real work, real partners or real users.
The big questions keep swallowing the practical ones
The existential issues matter, but the team also needs enough containment to make progress now.
Sprint or workshop?
Choose based on the job, not the diary.
A workshop can create alignment or make a defined decision in a day. A sprint is for work that needs iteration between conversations.
| Workshop | Sprint | |
|---|---|---|
| Best for | One defined outcome | A connected system or process |
| Rhythm | One or several sessions | Weekly cycles over four to six weeks |
| Between sessions | Limited follow-up | Focused work, testing and learning |
| Typical output | Agreement and next actions | A tested new way of working |
The sprint process
A clear backbone. A responsive route.
Each sprint follows a deliberate progression, while the work inside it adapts as the team learns.
Week 0–1
Set the scene
Clarify the challenge, the decision space, who needs to be involved and what useful progress would look like.
You leave withA shared sprint brief, clear boundaries and agreed measures of progress.
Week 1–2
Explore and sensemake
Map the real system, hear different perspectives and identify where friction, assumptions or missing information sit.
You leave withA visible picture of the current system and the leverage points within it.
Week 2–4
Prototype in real time
Create tangible alternatives, workflows, tools, criteria or ways of working, and test them with the people who will use them.
You leave withWorking prototypes and evidence about what needs to change.
Week 4–5
Make the decisions
Use what the team has learnt to resolve trade-offs, make clear choices and agree the new approach.
You leave withRecorded decisions, clear ownership and a practical route to implementation.
Week 5–6
Embed and hand over
Put the new approach into practice, capture the learning and make ownership explicit before the sprint closes.
You leave withUsable tools, a learning record and a team able to continue without me.
What the weeks feel like
A working rhythm, not a weekly performance.
I become part of the team’s rhythm: facilitating the important conversations, supporting workstreams and keeping the whole challenge visible while people test pieces of it.
Structure holds the pace.
The team does the thinking.
- 01
Come together
Share evidence, make sense of what has changed and decide the next focus.
- 02
Work and test
Small groups build, try and gather feedback in the real context.
- 03
Learn and adapt
Bring the evidence back, refine the approach and make the next decision.
Working together
I hold the process. Your team holds the knowledge and the decisions.
What I bring
- The sprint architecture and weekly pace
- Neutral facilitation across functions and hierarchies
- Methods for seeing systems, generating options and making decisions
- Containment for the bigger questions without allowing them to derail the practical work
- Documentation of the learning, choices and tangible outputs
What your organisation brings
- A senior sponsor who can unblock the work and enable decisions
- A small cross-functional core team with the relevant knowledge
- Honest access to the people who use, deliver or experience the process
- Time for focused work and testing between sessions
- Permission to learn, change course and make something good enough to test
What comes out of it
Not a deck of observations. A usable change.
The exact outputs depend on the challenge. Every sprint is designed to leave the organisation with practical evidence, decisions and tools, not reliance on an external facilitator.
A clear picture of the current system
The process, relationships, hand-offs and hidden blockers made visible in one place.
A tested alternative
Not a theoretical recommendation: a workflow, tool, decision framework or approach that has met real work.
Decisions people can trace
What was agreed, why it was agreed and where genuine uncertainty or disagreement remains.
Practical tools your team owns
Templates, criteria, maps, prompts or working agreements designed for continued use.
A record of the learning
What worked, what did not, what changed during testing and what the organisation should watch next.
A route beyond week six
Clear ownership, immediate next actions and a sensible rhythm for review and iteration.
What makes it different
I work inside the process, not at arm’s length.
I become part of the team’s weekly rhythm: facilitating sessions, supporting workstreams, helping people test prototypes and making the learning visible as it happens.
- Cross-functional team, not a facilitation audience
- Short cycles of thinking, making and testing
- Decisions made using real evidence
- Practical tools and workflows left behind
- Learning captured alongside delivery
Sprint in actionSprint in action
Three sprints. £3.75m distributed.
An independent grantmaker redesigned its funding process while live rounds continued to move through it. Programmes, learning, legal, finance and operations worked together to test a faster and more useful approach.
£3.75mdistributed across three sprints
2 weeksfrom first contact to payment
≈60%less internal administration
Practical questions
What people usually want to know.
Does every sprint take six weeks?
No. Four to six weeks is the usual shape, but the right length depends on the decision, the people involved and how quickly the team can test work in the real context.
How much time will the team need?
There is normally one facilitated working session each week, plus focused work between sessions. I agree the rhythm and expectations before the sprint begins so people can protect the right amount of time.
Can a sprint be online or hybrid?
Yes. The format follows the team and the work. Some sprints combine shorter online working sessions with focused in-person days; others can run fully online.
Who needs to be involved?
A small cross-functional core team works best, with access to a decision sponsor and the people who use, deliver or experience the process. Not everyone needs to attend everything.
What if we have not framed the problem properly?
That is common. The opening stage creates a shared sprint brief and tests the assumptions behind the challenge before the team starts designing answers.
What happens after the sprint?
The final phase makes ownership, review points and next actions explicit. The aim is for your team to continue using and improving the new approach without needing me in the middle of it.
Let's work together
Could a sprint unlock your challenge?
You do not need to know the solution, or even have the problem perfectly framed. Start by telling me where the work is getting stuck.
Talk through your challenge