Guide
Design sprint roles: the facilitator and the Decider
A design sprint has two key roles. The facilitator runs the process: the agenda, the timer, the discussion and the energy of the group. The Decider owns the outcome: they make the final call after each team vote, and the result of the sprint is theirs to act on. The book Sprint advises giving the two roles to different people. AppSprint calls them host and decision-maker, and the host can also name co-hosts.
Where the two roles come from
Both roles are defined in the book Sprint by Jake Knapp, John Zeratsky and Braden Kowitz. The Decider exists because sprints move too fast for consensus: someone with real authority, often a founder, a product lead or a client sponsor, has to be able to say "this one" so the team can move on. The facilitator exists because a group working to a timer needs someone watching the process, not the content.
The book advises against combining them. A facilitator should be neutral about which idea wins, and a Decider cannot be.
Who does what
| Facilitator | Decider | |
|---|---|---|
| Owns | The process and the clock | The outcome and what happens after |
| During votes | Runs the vote and the reveal, takes no side | Votes with the team, then makes the final call |
| Good fit | Organised, neutral, comfortable interrupting | Has the authority to act on the result |
Set up the roles step by step
Choose the Decider first
Ask who could overrule the result afterwards. That person is the Decider. If they cannot attend all of the sprint, they name a delegate whose decisions they will respect.
Choose a facilitator with no stake in the answer
Pick someone happy to keep time and cut discussions short, ideally from outside the team whose idea is on the table.
Agree how decisions will be made (10 minutes)
Tell the team beforehand: everyone works alone, votes are private, the vote is advice, and the Decider chooses.
Brief both people (15 minutes each)
Walk the facilitator through the agenda and timings. Ask the Decider to hold their opinions until others have voted and to explain their choices in a sentence or two.
Close the loop
At the end, the Decider states the decision, the owner and the next step, and the facilitator sends the record to everyone.
Common mistakes
- A Decider in name only. If someone more senior can reverse the decision later, the team stops investing.
- A Decider who speaks first. Their view becomes the anchor for everyone else's.
- A facilitator who argues for an idea. The group stops trusting the process.
What changes when the team is remote
The facilitator's job grows: on a call they also manage links, the timer and who is lost, so a co-facilitator is worth having. The Decider's influence is easier to contain online, provided ideas are anonymous and votes are private until the reveal. See anonymous dot voting.
Doing this in AppSprint
AppSprint shows three roles: host, co-host and decision-maker. The host is the facilitator. Hosts and co-hosts control the timer and move the room from step to step; everyone else sees a read-only countdown. The host assigns co-hosts and the decision-maker. See guest access and roles.
The decision-maker is the Decider. Team votes are private and advisory, and the decision-maker then confirms each choice. In the Gallery step they keep one to three prototypes, and in Refine Together only the decision-maker prompts the AI while teammates send anonymous suggestions.
One difference from the book: the decision-maker defaults to the host, and the role falls back to the host if the decision-maker disconnects. To follow the book's advice, assign the role to someone else at the start. The agenda is fixed by the template, so a custom agenda needs a different tool. The Sprint Coach is pre-recorded voice guidance; it supports the host and does not replace one.