Framework · Facilitation techniques · 2 min read
Fist to Five
A quick consensus check: everyone shows 0–5 fingers for their level of support at the same time, and you discuss anything at 2 or below before you close the decision.
- 0 Fist
- Means
- I block this. We must not go ahead.
- Then
- Stop and hear the objection in full
- 1 finger
- Means
- Serious concerns. I need changes first.
- Then
- Ask what would make it a 3
- 2 fingers
- Means
- Some concerns I want to discuss.
- Then
- Ask what would make it a 3
- 3 fingers
- Means
- I can live with it and support it.
- Then
- Enough to go ahead
- 4 fingers
- Means
- I support it. It is a good idea.
- Then
- Enough to go ahead
- 5 fingers
- Means
- Full support. I will help lead it.
- Then
- Ask them to help with next steps
Discuss every 0, 1 or 2 before you close the decision.
Use it when
- A discussion seems finished, but you are not sure whether silence means agreement.
- You want to close a design-system or process decision in a mixed group of designers, developers and product managers.
- A senior stakeholder is in the room and you want quieter people to show their real support level.
How to use it
- State the proposal in one sentence. Write it where everyone can see it, so people vote on the same thing. Output: one visible proposal.
- Explain the scale. 0 (a fist) means "I block this", 2 means "I have concerns I want to discuss", 3 means "I can live with it and support it", 5 means "full support, I will help lead it". Output: a shared meaning for each number.
- Count down and show at the same time. Say "3, 2, 1, show". Everyone shows their hand at once, so nobody copies the most senior person. On a call, people type the number in the chat and send on your signal. Output: a visible spread of support. Under 1 minute.
- Ask every low score what would make it a 3. Go to each 0, 1 or 2. Listen, don't defend the proposal. Output: the concrete concerns behind the low scores.
- Adjust and check again, or close. If the concerns lead to a change, update the proposal and run a second round. If everyone is at 3 or above, record the decision. Output: a decision with visible support, or a named open concern. About 5 minutes in total.
Worked example
A UX lead runs a design-system workshop with 6 designers and 2 frontend developers on an internal operations platform. After 40 minutes the group proposes: "All data tables use the shared filter panel from next quarter." The lead runs Fist to Five.
| Round | Result | What the lead does |
|---|---|---|
| First show | Five people show 4 or 5, two show 3, one developer shows 2 | Asks the developer: "What would make it a 3 for you?" |
| Concern | "Two old tables can't use the panel without a rebuild." | The group adds: "Existing tables move when they are next rebuilt." |
| Second show | Everyone shows 3 or above | The lead records the decision and the exception in the workshop summary. |
Watch out for
- Votes that are not shown at the same time. If people raise hands one by one, they follow the first or most senior person. Always count down.
- Treating it as a majority vote. Six fives do not cancel one fist. A 0 means there is a real objection you need to hear.
- Rushing past the 2s. Saying "noted" and moving on teaches people that their concern does not matter. Ask the question and wait.
- Using it too early. Fist to Five closes a decision. It does not replace the discussion, so run it after options are clear.
Template
Put this on the board or slide before you run the check.
FIST TO FIVE
Proposal: _________________________________________________
0 Fist I block this. We must not go ahead.
1 Serious concerns. I need changes first.
2 Some concerns I want to discuss.
3 I can live with it and support it.
4 I support it. It is a good idea.
5 Full support. I will help lead it.
"3, 2, 1, show."
Everyone at 0-2: "What would make it a 3 for you?"
Result: ______ Changes made: ______ Decision recorded: yes / no
Saved only on this device.