Facilitator placing sticky notes on a flip chart while teammates review options in a loft workspace

Workshop Guide

Dot Voting Workshop

Turn a long list of ideas into a visible, shared set of priorities in minutes, so every voice counts and the group knows exactly where to focus next.

Steps
Frame→
Vote Silently→
Tally→
Decide

01 / Summary

What Is Dot Voting?

Dot voting is a fast, visual prioritization technique. Each participant receives a fixed number of votes, traditionally small dot stickers, and places them on the options they believe matter most. Participants can spread their dots across several options or stack more than one on a single option they feel strongly about. When everyone has voted, the dots form a heat map that shows where the group’s energy and agreement already sit.

Agile teams use dot voting to narrow retrospective topics, choose which improvement actions to take on, shortlist features or ideas, and break a stalemate when discussion stops moving. It works because it gives every person an equal, simultaneous say, takes minutes rather than hours, and converts a sprawling list into a short, ranked set the group can act on. Dot voting is a tool for focusing a conversation, not for replacing one: the tally tells the group where to spend its discussion time.

1
Every Voice Counts Equally
Each participant gets the same number of dots, so the quietest person in the room has the same influence on the outcome as the loudest.
2
Turns a Long List Into a Short One
A wall of thirty ideas becomes a clear top three to five in a few minutes, freeing the group to spend its time on the items that matter.
3
Makes Agreement Visible
The finished board shows at a glance where the group converges and where opinions split, so the next conversation starts from evidence rather than assumption.

02 / Application

When to Use Dot Voting.

Use this workshop any time a group has generated more options than it can act on and needs to agree, quickly and fairly, on which few to pursue first.

Retrospective Topic Selection

The team has surfaced a dozen or more observations in a retrospective and needs to choose the two or three that are worth a deep discussion in the time remaining.

Improvement Backlog Shortlisting

An Agile Release Train or team has a long list of possible improvement items, and needs to agree on which ones to commit to in the next iteration or Program Increment.

Idea and Feature Narrowing

A brainstorming session has produced many feature, solution, or design ideas, and the group needs a shortlist to carry into deeper analysis such as WSJF or MoSCoW.

Breaking a Discussion Stalemate

A conversation has stalled with several options on the table and no clear way forward; a quick round of dots shows where the group already leans and restarts the conversation.

Prerequisites

A Visible, Clearly Worded Option List

Every option is written down, posted where everyone can see it, and phrased clearly enough that participants understand what they are voting for; duplicates are merged before voting starts.

A Clear Voting Question

The group agrees on the single question the dots answer, such as “Which of these will make the biggest difference next iteration?” Votes cast against different questions produce a meaningless tally.

Roles and Responsibilities

Facilitator
Frames the voting question, sets the number of dots and the voting rules, keeps the voting round silent, tallies the results, and leads the discussion of what the tally means.
Participants
Vote independently based on the agreed question, resist lobbying during the voting round, and take part in the discussion that follows the tally.
Decision Owner
The Product Owner, Release Train Engineer, or team lead who confirms how the result will be used and carries final authority if the group must break a tie or override the vote.
Scribe
Records the final tally, the ranked shortlist, and any owners or next steps agreed in the room, and captures a photo or export of the board before it is cleared.

Agree before voting whether the result is binding or advisory. A group that believes its vote decides the outcome, only to see it overridden, will stop trusting the technique.

Scheduling and Timing

  • Plan for 30 to 60 minutes when dot voting runs as a standalone session; as part of a retrospective or larger workshop, 10 to 20 minutes for voting and tallying is usually enough.
  • Run it right after a divergent activity such as brainstorming or a retrospective, while the options are fresh and the group still has the context behind each one.
  • Limit the list to roughly 30 options or fewer; longer lists benefit from a quick affinity grouping first so votes are not split across near-duplicates.
  • Send the option list ahead of time when it already exists, so participants can think about each item before the session rather than voting on first impressions.

03 / Preparation

Preparing for the Workshop

Dot voting is quick to run, which makes it easy to under-prepare. The quality of the result depends almost entirely on the setup: a clear question, a clean option list, and voting rules everyone understands before the first dot goes up.

  • Write the single voting question the group will answer, and confirm with the decision owner whether the result will be binding or advisory.
  • Prepare the option list: merge duplicates, give each option a short, clear label, and assign each a letter or number so votes can be recorded and tallied accurately.
  • Decide the number of dots per person; a common rule of thumb is roughly one dot for every four options, and always more than one but fewer than the total number of options.
  • Set up the voting space: dot stickers or markers and a wall or board for in-person sessions, or a virtual whiteboard with voting enabled and anonymity settings checked for remote sessions.
  • Download and prepare the Facilitator Presentation and the Dot Voting Excel Template.
  • Track every workshop activity, from preparation through follow-up, using the Dot Voting Workshop Checklist. Teams using Jira can import the Dot Voting Jira Accelerator.
  • Send scheduling communication with agenda and pre-read materials

    Email Template

    Subject: [Team/Program Name] Dot Voting Session – Agenda and Option List

    Hi team,

    We’re holding a short Dot Voting session on [date] to agree on which [improvement items / ideas / features] we focus on first for the upcoming [iteration / increment / release].

    The question we’ll be voting on is: “[voting question].” Please review the attached option list before the session and come with an initial view of which items you’d prioritize. Each person will receive [number] votes to place.

    Location/Link: [link]
    Duration: [30 to 60 minutes]

    Calendar Invite Copy

    Subject: Dot Voting Session

    Agenda: Frame the question, review the options, silent voting round, tally and discuss, confirm the shortlist and owners.

    Room/Virtual: [link]

    Please review the option list beforehand so your votes reflect real consideration, not first impressions.

04 / Facilitation

Facilitation Agenda

Facilitation protects the independence of each vote. The most common failure mode is a round where people watch where others put their dots, or where one person campaigns out loud, so the tally reflects influence rather than individual judgment. The facilitator’s job is to keep voting quiet and independent, then make sure the discussion that follows explains the result rather than relitigates it.

Presenting the Dot Voting Process

This agenda guides facilitators through a structured dot voting session. Time estimates reflect a 45-minute standalone format; shorten each step when dot voting runs inside a retrospective or a larger workshop. Keep the session focused on producing a ranked shortlist with clear owners, not on debating every option.

  1. Frame the Question and the Rules
    • State the voting question, the number of dots per person, whether stacking dots on one option is allowed, and whether the result is binding or advisory.
  2. Review and Clarify the Options
    • Read each option aloud, answer clarifying questions only, and merge any duplicates; no advocacy or debate at this stage.
  3. Run a Silent Voting Round
    • Give participants a few minutes to decide privately, then place their dots; ask people to note their picks on paper first, or use hidden voting in a virtual tool, to reduce follow-the-crowd voting.
  4. Tally and Reveal the Results
    • Count the dots on each option, record totals in the Excel Template, and present the ranked list so everyone sees the same result.
  5. Discuss the Pattern
    • Ask what surprised people, why the top options drew votes, and whether any low-vote option carries a risk the group should not ignore.
  6. Break Ties and Confirm the Shortlist
    • Run a quick second round on tied or near-tied options if needed, then confirm the final shortlist, an owner for each item, and the next step.

Common Anti-Patterns to Avoid

  • Voting happens in full view and in sequence, so later voters follow the early dots instead of their own judgment; use a silent, private decision step before anyone places a dot.
  • One participant lobbies for a favorite option during the voting round; the facilitator pauses voting and reminds the group that discussion comes after the tally.
  • The most senior person votes first and everyone else follows; have leaders vote last, or use anonymous digital voting.
  • The tally is treated as the final answer with no discussion, so a low-vote option with a critical risk or dependency gets quietly dropped.
  • Options are vague or overlapping, so votes split across near-duplicates and no clear winner emerges.

05 / Follow-Up

After the Workshop

A dot voting result is only valuable if the top items actually get worked. Within a day of the session, the group should see the final tally, know who owns each shortlisted item, and know when progress will be checked, otherwise the next session starts by re-voting on the same list.

Expected Outputs

Final Vote Tally
Ranked Shortlist
Owners and Next Steps
Parked Options Log
Board Photo or Export

Distribute the completed Dot Voting Excel Template within 24 hours to all attendees and to any stakeholders who were not in the room. Post it where the team actively works, a pinned Confluence page, a shared drive folder, or the relevant Jira epic, so the ranked shortlist is easy to find at the next planning Event or retrospective.

Follow-Up Communication Template

Subject: [Team/Program Name] Dot Voting – Results and Agreed Shortlist

Hi team,

Thank you for taking part in our Dot Voting session on [date]. Attached is the final tally. Based on the vote and our discussion, we agreed to focus on these items first:

1. [Item] – Owner: [name]
2. [Item] – Owner: [name]
3. [Item] – Owner: [name]

The remaining options are captured in the parked options log and will be revisited at [next retrospective / planning Event / date]. If you see something that needs another look, let [name] know before [date].

Ongoing Next Steps

  1. Scribe or facilitator posts the completed Dot Voting Excel Template and board photo to [Confluence / Jira / shared drive] within 24 hours.
  2. Each owner turns their shortlisted item into a backlog item or improvement story with a clear next action.
  3. Decision owner confirms the shortlist fits the team’s available capacity for the [iteration / increment] and raises any conflicts.
  4. Owners report progress on the shortlisted items at the next team sync or retrospective.
  5. Facilitator reviews the parked options log at the next retrospective or planning Event and removes items that are no longer relevant.
  6. Run a fresh round of dot voting when the option list changes significantly, rather than carrying an old tally forward.

06 / References and Resources

References and Resources

Complimentary Workshops

MoSCoW Prioritization Workshop

Agree on what is a Must, Should, Could, and Won’t before work begins.

Read More

Lean Coffee Workshop

Let the group build the agenda and time-box the topics that matter most.

Read More

WSJF Workshop

Sequence work to deliver maximum economic value first.

Read More

Pain Point Identification Workshop

Surface what slows teams down and fix the root causes.

Read More

Ready to facilitate?

Download templates and tools to run your own Dot Voting session.