Fist of Five

When to use

Before the team commits to a plan everyone has to live with — sprint goal, design choice, hiring decision, deployment plan. The format earns its place in the gap between agreement and commitment. Skip it for binary decisions (do we ship or not — use thumbs up/down). Skip it for multi-option decisions (which design do we pick — use Dot Voting). Skip it on a team that won't actually act on a 1 or 2; without the action loop it's a survey.

How it runs

1. State the proposal in one sentence

   'I'm proposing we adopt feature flags by end of next sprint.' One sentence, declarative. If you can't compress the proposal into a sentence, the team isn't ready to vote on it yet.

2. Vote simultaneously

   All hands at once, on a count. 5 = enthusiastic, 4 = yes, 3 = can live with it, 1-2 = real concerns, 0 = hard veto. Sequential voting hands the decision to whoever votes first — the senior person's hand sets the room.

3. Surface the lows, not the highs

   A single 1 or 2 is the entire reason the format exists. Stop the meeting. Ask the voter directly what would change their vote. The concern is the artefact you came for — not the average score, not the headcount of 4s.

4. Re-vote after addressing the concern

   Discuss; adjust the proposal if the concern is real; re-vote. Without the second vote, you've held a survey and called it consensus. The action loop — surface, address, re-vote — is the format's distinguishing feature.

5. Probe the 4s if the room is uniformly four

   All hands at four sounds like consensus and isn't. Ask one or two voters: 'what's stopping you from a five?' The answer is usually a small fix that turns the 4s into 5s — and locks in real commitment.

Why it works

Five points is the sweet spot. Three points (yes/maybe/no) loses the difference between 'enthusiastic' and 'reluctant'; ten points adds noise without signal. The 0-veto state is the format's distinguishing feature against simple thumbs voting — it gives any single person the power to stop the train, which is the point of a confidence check before commitment. The action loop on lows is what separates the format from a survey; stop running it if you won't run the loop.

Variations

• Anonymous variant: hidden poll, sticky-note ballot, or chat-DM to facilitator. Better for teams with strong seniority dynamics — the senior person's four anchors juniors to four.
• Three-finger version (1-3) for very fast decisions where the five-point distinction is overkill. Loses the veto state.
• Reaction-emoji on video: 1-5 emoji on a poll. Cleaner remote than tiny fingers on thumbnails.
• Written variant: each person writes their number on a card, reveal at once. Slower, more deliberate, fewer anchoring effects.

Facilitator notes

Vote yourself, last. If a 1 or 2 appears, your job is to make it safe to elaborate — not to defend the proposal. 'What would change your vote?' is the question, not 'why are you against this?' The first invites a conversation; the second invites silence. If the room is uniformly four, you're not done — probe one or two until you understand what's stopping the fives.

Pitfalls

• Treating it as a vote count and moving on. The 4 average hides the 1, and the 1 was the meeting.
• Skipping the re-vote after addressing a concern. Without it, the format is a survey.
• Sequential voting. The first hand sets the room; you measured the first voter, not the team.
• Using it on a binary decision. Five-point scale on a yes/no question is overkill — use thumbs up/down.
• Letting the senior person vote first. Juniors mirror the senior hand inside two seconds.

Remote tips

Physical fingers on a video call read poorly at small thumbnail size — half the team will misread a 4 as a 3. Use a 1-5 reaction emoji or a quick poll bot; the vote needs to be visible and simultaneous, and the tooling matters more than the gesture. Hidden polls are stronger when seniority dynamics are real.

Example outputs

• Proposal: 'Adopt feature flags by end of next sprint.' Vote: 5, 5, 4, 4, 4, 2. The 2 is the meeting. Stop, hear the concern (the auth migration is on the same sprint), adjust the timeline, re-vote.
• Proposal: 'Adopt feature flags by end of next sprint.' Vote: 4, 4, 4, 4, 4, 4. Uniform four sounds like consensus. Probe: 'what would make this a five?' — 'a stronger story about flag cleanup.' Add the cleanup plan; re-vote.
• Proposal: 'Skip code review for hotfixes.' Vote: 5, 5, 4, 0. The 0 is a veto and the format is doing its job. Stop and have the conversation.

FAQ

Fist of Five or Dot Voting?

Fist of Five for confidence on a single decision: do we commit to this plan? Dot Voting for prioritisation across multiple options: which of these do we work on? Different shapes of question. If you're asking 'are we sure?' use Fist of Five. If you're asking 'which one?' use Dot Voting.

Is Fist of Five a standalone meeting?

No. It's a technique that runs in two minutes inside another meeting — sprint planning, design review, kickoff. Like Roman Vote and Five Whys, it earns a page because facilitators search for it; the meeting itself is whichever planning session you're already running.

What do I do with a 1 or 2?

Stop the meeting. Ask the voter what would change their vote. Address the concern. Re-vote. The 1 or 2 is the entire point — it's the team telling you they spotted something the rest missed. Treat it as the discovery, not the obstacle.

Related activities

Recommended use cases