“Does everyone agree?” is the weakest question a facilitator can ask. Silence follows, a couple of people nod, and the team moves on with a plan that one or two people quietly expect to fail. Fist of five replaces that question with a vote that takes ten seconds and makes doubt visible: everyone shows, at the same moment, how strongly they back the proposal, from a closed fist to five fingers.

This guide covers what fist of five is, what each number means, how to run it step by step, and what to do with the low votes, which is where all its value sits. It also covers its two close relatives: the Roman vote, for deciding whether to keep talking, and dot voting, for choosing between many options. Pick the right one for the question in front of you and each takes under five minutes.

What is fist of five?

Fist of five (also called fist to five, fist to 5 or five-finger voting) is a quick decision-making technique that shows how much support a proposal has before a group commits to it. Someone states the proposal in one sentence, the facilitator counts down, and everyone holds up zero to five fingers at once. Zero, a closed fist, means “I can’t support this.” Five means “I’m all in.”

It works because it changes the question. A yes/no vote tells you whether people will go along with something. A 0 to 5 scale tells you how firmly they hold that view, and it gives a quiet person a way to say “I have doubts” without having to interrupt a confident room. Agile teams use it in sprint planning, when agreeing working agreements and before design or architecture decisions. Project teams use it at kickoffs and go/no-go calls, and teachers use the same gesture to check whether a class has understood a lesson.

What the fingers mean

Agree the scale before the first vote, ideally written somewhere everyone can see. The most common meanings in team decisions are:

  • Fist (0): “I block this. I can’t support it as it stands.”
  • One finger: “I have serious concerns. It needs changes before I can support it.”
  • Two fingers: “I have some concerns I’d like to talk through.”
  • Three fingers: “I can live with it. Not my first choice, but I won’t stand in the way.”
  • Four fingers: “I support it.”
  • Five fingers: “I strongly support it and I’d champion it.”
0 1 2 3 4 5 Block Serious concerns Some concerns Can live with it Support Champion Stop and talk Go ahead FINGERS SHOWN
The scale splits in two. Three or more means a person will back the decision; a fist, one or two means there is a concern the group needs to hear before it commits.

Before you start, also agree what result lets the team proceed. Our default: the proposal goes ahead when everyone shows three or more. Any two or lower gets heard first, and a fist means the team does not proceed until the concern is resolved or the proposal changes. Some teams treat a fist as a hard veto and others as a very strong objection; either works, as long as everyone knows which rule applies before they vote.

Three more ways to use the scale

The hand signal is the same in every case. What changes is the question you ask, so say the question out loud and agree what the numbers mean for it before anyone votes.

Confidence votes

A confidence vote asks “how confident are you that we can deliver this?” instead of “do you support it?” Teams run one at the end of sprint planning against the sprint goal, and SAFe’s PI planning closes with a confidence vote across the whole group, usually taken with fist of five. Read it the same way: a fist, one or two means someone sees a risk in the plan, and the time to hear it is before the work starts. Ask what would raise their confidence, adjust scope or dependencies if needed, and vote again.

ROTI: was this meeting worth it?

Return on time invested (ROTI) uses the scale at the end of a meeting. Everyone shows how much value they got for the time they spent. A simple ROTI template:

  • One finger: “Not worth my time.”
  • Two fingers: “Some value, but not worth the time it took.”
  • Three fingers: “Worth the time I spent, no more.”
  • Four fingers: “More value than the time I spent.”
  • Five fingers: “A lot of value. Definitely worth it.”

Some teams add a fist for “I shouldn’t have been here at all”, which is useful feedback on the invite list. Before people leave, ask the ones and twos what would have made it worth their time; the answers improve the next meeting more than any average score. Our post on return on time invested covers ROTI in more depth.

Fist to five as a check for understanding

In classrooms and training sessions the same gesture measures understanding instead of agreement. A fist means “I’m lost”, three means “I mostly get it but need more practice”, and five means “I could explain this to someone else.” The mechanics are identical: everyone shows at once, and the low numbers tell you where to spend the next five minutes. It works just as well at the end of a team onboarding session or a walkthrough of a new process.

How to run fist of five

The whole vote takes a minute or two. The discipline is in steps four and five.

  1. State the proposal in one sentence. “We move the release to Thursday so QA gets a full day.” If you can’t say it in a sentence, the team isn’t ready to vote on it; clarify the proposal first.
  2. Ask everyone to decide privately. Give people a few seconds to settle on a number before anyone shows a hand.
  3. Vote at the same moment. Count down, “three, two, one, show”, and every hand goes up together. If people vote one after another, the first hand sets the room, and if that hand belongs to the most senior person, everyone else tends to match it. As facilitator, show your own number last.
  4. Look at the low end first. Ignore the average. Ask anyone showing a fist, a one or a two: “What would it take to move you to a three?” Listen without defending the proposal. That question invites a fix; “why are you against this?” invites silence.
  5. Adjust and vote again. If the concern is real, change the proposal and re-vote. If the group hears it and still wants to go ahead, say so plainly and vote again so everyone commits to the same version. Skipping the second vote is the most common way fist of five turns into a survey nobody acts on.
  6. Record the decision. Once the team is at three or above, write the decision down where the team will see it again. Team agreements in particular are worth revisiting at the next retrospective.

Fist of five examples

Three votes on the same kind of proposal, and what each result tells you:

  • “We adopt feature flags by the end of next sprint.” Votes: 5, 5, 4, 4, 4, 2. The two is the important vote. The person explains that a database migration is landing in the same sprint. The team moves the target out by a sprint, re-votes, and everyone is at four or five.
  • “We stop estimating bugs.” Votes: 4, 4, 4, 4, 4, 4. Nobody objects, nobody is keen. Asked what would make it a five, someone says “a cap on how many unestimated bugs we pull into a sprint.” The team adds the cap and the second vote comes back mostly fives.
  • “Hotfixes skip code review.” Votes: 5, 4, 4, 0. The fist is doing its job. The person who raised it runs on-call and has seen an unreviewed hotfix take production down. The team drops the proposal and agrees a faster review path for hotfixes instead.

Where fist of five fits, and where it doesn’t

Fist of five earns its place in the gap between “we’ve discussed it” and “we’re committed to it”. It suits any single decision the whole team has to live with:

It is the wrong tool in three situations. For a plain yes/no question, a Roman vote is faster. For choosing between several options, dot voting gives you a ranking where fist of five can only score one proposal at a time. And on a team that won’t act on a low vote, skip it altogether: asking for doubts and then ignoring them teaches people to stop raising them.

The Roman vote: keep going or move on

A Roman vote is the fastest decision a group can make. Someone asks a yes/no question and everyone answers at once with a thumb: up for yes, down for no, sideways for “I’m fine either way.”

Its natural home is Lean Coffee. The group votes on topics, discusses the top one against a short timer, and when the timer ends the facilitator asks: “Keep going, or move on?” Thumbs up gives the topic another few minutes; thumbs down moves to the next one. It works just as well inside any timeboxed discussion that keeps running past its slot.

Two habits make it reliable:

  • Read the sideways thumbs. Sideways looks neutral, but in a “keep going?” vote it usually means “I have nothing left to add.” If four people want to continue and three are sideways, the four are talking and the three have tuned out. Most of the time the right call is to move on.
  • Everyone votes at once, senior people included. A Roman vote is meant to stop the loudest voice from extending a topic on its own. That only works if nobody can wait to see which way the manager’s thumb goes.

A Roman vote has three states, so it cannot tell you how strongly someone objects. When the answer matters enough that you need to hear the doubts, switch to fist of five.

Dot voting: choose from many options

Dot voting is the convergence step of most retrospectives and brainstorms. The team has surfaced more ideas than it can act on, so each person gets a small number of votes, the dots, and spends them on the items they think matter most. The items with the most dots get discussed first.

It is quick and almost everyone knows it already. Whether it produces a useful result depends on a few rules you set before anyone votes:

  1. Give each person three dots by default. Three forces a real choice. Use up to five for a long list you want to rank. Past that, votes spread thin and everything ties.
  2. Decide on stacking. Allowing several dots on one item lets people show a strong preference and usually produces a clear winner. One dot per item produces a flatter ranking. Announce the rule up front and don’t change it halfway through.
  3. Vote privately and reveal together. If people can see where the dots are landing, they pile onto the early leader, especially when it’s the most senior person’s pick.
  4. Take the top one or two. The point is to converge. If two items tie, re-vote on just those two.

Group related ideas before you vote so similar suggestions don’t split each other’s dots. And read the shape of the result as well as the winner: dots scattered evenly across every item mean the team has no strong preference yet, while one item with most of the dots is often the whole conversation for the session.

Choose the vote by the question you’re asking

All three techniques are quick. They answer different questions, and using one for another’s job is the usual reason a vote gives a misleading result.

THE QUESTION REACH FOR Keep talking about this? Do we all back this plan? Which of these matters most? Roman vote Fist of five Dot voting 3 states 0 to 5 3 dots each
Ask yourself what the group needs to decide. Whether to keep going is a Roman vote, whether everyone backs one plan is fist of five, and which of many items comes first is dot voting.

They also chain together well. In a typical retrospective, dot voting picks which themes to discuss, a Roman vote decides when a discussion has run its course, and a fist of five confirms the team stands behind the action it agreed. Whichever you use, the same three rules apply: agree the rules before voting, everyone votes at the same moment, and the most senior person shows their vote last or not at all.

Running these votes online

Hands and thumbs are hard to read in small video tiles; half the room will misread a four as a three. For remote and hybrid teams, move the vote into a tool where everyone answers at once and the results stay hidden until the reveal.

In TeamRetro you can run all three without leaving the meeting:

  • Fist of five: add a poll to an idea, a comment or the meeting chat and pick the 0 / 1 / 2 / 3 / 4 / 5 template. Hide the results while people answer, then reveal them together and ask the low votes what would change their mind. For confidence votes and ROTI, the built-in Delivery Confidence and Return on Time Invested check-out questions ask the same thing at the close of a retrospective, health check or estimation meeting, and your team’s insights show how the answers trend from meeting to meeting.
  • Roman vote: in presentation mode, the agree/disagree poll gives you a thumbs up or down from everyone in seconds, and the go slower/faster signal tells you when a discussion is dragging.
  • Dot voting: the Vote step lets you set the number of votes per person, cap how many one person can put on a single idea, vote on ideas or on whole groups, and keep every vote hidden until the next step. People who shouldn’t vote, such as observers, can abstain.

Once a decision passes, capture it as an action or a team agreement so it’s still visible at the next retrospective. The retrospective features page shows how polls, voting and agreements fit into one meeting, and our guide to retrospective games has formats that end in exactly these decisions.

Frequently asked questions

What is fist of five?

Fist of five is a quick consensus check. Someone states a proposal, and everyone shows their level of support at the same moment by holding up zero to five fingers: a fist means “I block this”, five means “I’ll champion it”. It takes under a minute, and its real value is the low votes. A one or a two tells you someone has a concern the group hasn’t heard yet, so you stop, listen, adjust and vote again.

Is it fist of five or fist to five?

Both names describe the same technique. “Fist to five” describes the range of the scale, from a closed fist up to five fingers; “fist of five” is the more common name in agile teams. Some groups also call it five-finger voting. The steps and the meaning of each number are the same whichever name you use.

What do the fingers mean in fist of five?

A fist (0) means “I can’t support this and will block it”. One finger means serious concerns that need changes first. Two means some concerns the person wants discussed. Three means “I can live with it”. Four means clear support, and five means strong support: the person would champion it. Agree the meanings before the first vote so everyone reads the numbers the same way.

What is a fist of five confidence vote?

A confidence vote uses the fist of five scale to ask how confident each person is that the team can deliver a plan, such as a sprint goal or a PI plan. Everyone shows zero to five fingers at once. Low votes point to risks the plan hasn’t accounted for, so you hear them, adjust scope or dependencies, and vote again before the team commits.

How do you use fist of five for ROTI?

At the end of a meeting, ask “was this worth your time?” and have everyone show one to five fingers: one means not worth it, three means worth the time and no more, five means a lot of value. Ask the low scores what would have made the meeting worth their time, and use the answers to change the next one.

What do you do when someone shows a fist, a one or a two?

Stop and ask them what would change their vote. Listen without defending the proposal, decide as a group whether the concern changes the plan, adjust it if it does, then vote again. The low vote is the reason the technique exists: it surfaces a risk or a doubt before the team commits, which is far cheaper than discovering it halfway through the work.

When should I use fist of five, a Roman vote or dot voting?

Match the technique to the question. A Roman vote answers “do we keep talking about this?” with thumbs up, sideways or down. Fist of five answers “do we all back this one plan?” on a 0 to 5 scale. Dot voting answers “which of these many items matters most?” by giving everyone a few votes to spend. Using one for another’s question is the most common reason a quick vote produces a misleading result.

How do you run fist of five remotely?

Fingers held up to a webcam are hard to read in small video tiles, so use a poll or reactions instead. Post a 0 to 5 poll, keep the results hidden until everyone has answered, then reveal them together. In TeamRetro you can add a poll with a 0 / 1 / 2 / 3 / 4 / 5 template to an idea, a comment or the meeting chat, and choose when to reveal the results.

What is a Roman vote?

A Roman vote is a three-way thumbs vote: thumbs up means yes or keep going, thumbs down means no or move on, and sideways means “I’m fine either way”. Teams use it most often in Lean Coffee, where a topic’s timer runs out and the group decides in seconds whether to give it more time. Watch the sideways votes: a room full of them usually means the topic has run its course.

How many votes should each person get in dot voting?

Three votes each is a sensible default: few enough to force a real choice, enough to show a pattern. Use up to five for a long list you want to rank, and avoid more than that, because extra votes spread out until everything ties. Decide before voting starts whether people may put several votes on one item, and keep the votes hidden until everyone has finished.