Dot Voting Template
Better prioritize items and make decisions as a group. The Dot Voting Template helps you bring teams to an agreement effortlessly.
About the Dot Voting Template
Dot voting (also known as “sticker voting,” “dotmocracy,” or “voting with dots”) helps teams improve decision-making, making sure every voice is heard and taken into account. A dot voting method is also an excellent tool when teams need to prioritize what action to take first when presented with many different options.
Keep reading to learn more about the Dot Voting Template.
What is dot voting
Dot voting is different from the default “one-share” or “one-vote” rule. Instead, each person in the group is given as many votes (or “points”) as can be filled. Those votes can either be cast for one idea or distributed among many ideas. Consider all votes equally since the aim is to reach an agreement quickly.
Think of dot voting as a survey or polling method to understand what ideas or tasks a team considers the highest priority. Cast votes by posting a dot next to the preferred option.
Everyone on your team must dot vote simultaneously rather than in turns. This helps reveal group priorities rather than the opinion of the most influential team member.
The dot voting facilitator or team manager counts the final votes at the end of the timed voting session. They can point to preferred ideas, ranking them in priority by going in the highest number of dot votes.
When to use a Dot Voting Template
Many product and UX design teams use the Dot Voting Template to prioritize tasks or agree on a direction to take for a high-stakes project. Other teams can also benefit from the dot voting method, especially when there is a need for consensus in a project.
To facilitate a dot voting session, you can copy this Dot Voting Template and use it on a new board or add it to any other existing Miro board.
First, select all elements on the board using Ctrl+A/Cmd+A shortcut. Then you can copy and paste onto your preferred Miro Board (or any Miro Board element) using Ctrl+C (copy) and Ctrl+V (paste).
How to apply the dot voting method
Product and UX teams use Dot voting during sprint retrospectives. This method can often lead to false or confusing results, so it’s best to keep a few tips in mind to make this method fair and valuable for everyone.
Avoid “group think” No dot voter should feel pressured to add dots to the most popular item – instead, they should vouch for what they think is worth prioritizing.
Look for the “lowest resistance” – not just the greatest approval The options with the highest acceptance level in the group are those with the highest acceptance dot votes and the lowest number of resistance dot votes (you can allocate a color, such as red, to represent negative votes).
Avoid similar-sounding options Try to spot these options earlier – ideally, combine specific and similar-sounding ideas to a single option. For example, instead of choosing between a fruit basket and six different cookies, turn the options into either a fruit basket or cookies.
Keep the number of options as low as possible Do an options audit before voting to avoid team or voter overwhelm.
Clarify expectations beforehand What are your goals and criteria for voting? Make sure everyone knows before dot voting.
Create your own Dot Voting exercise
Making your own dot voting exercise is easy. Miro’s whiteboard tool is the perfect canvas to create and share them. Get started by selecting the Dot Voting Template, then take the following steps to make one of your own.
1. Be clear about your voting goals
Remind your team about why you’re voting and what you'll use the results for. Remind your team how many equal votes everyone has – remember, everyone always has more than one in a typical dot voting session.
2. Let your team know about voting criteria and constraints
Will the vote be going towards deciding potential product features? In that case, your developers may lean toward feasibility as criteria, whereas designers would vote based on user impact. Revisit the best practices listed in the “how to apply” section to ensure your ideas suit the criteria you’ll be voting for.
3. Vote as a team
Use it to give everyone a chance to vote in silence. The conversation should only restart after everyone has finished voting. No one should be influencing each other to vote a particular way during the quiet voting time, either.
4. Calculate the results
The manager or group facilitator can now count the votes after the team has voted. As a team, you can discuss why the most highly ranked ideas or solutions were picked and map out the next steps.
5. Narrow down your options and revote if needed
Noticed you have a tie between two ideas? Still, think you have too many options to choose from? To reestablish a clear winner, you can revote by distributing the same number of votes to narrow down your top options again.
How does dot voting work?
After you have all the options that need to be chosen or prioritized on the board, calculate how many votes each team member will have. A good practice is that the dots for each person equal 25% of the total options on the board. Then, set the rules for the voting. Afterward, set the timer and ask people to cast their votes. Finalize the session, counting the votes and discussing with your team the results of the voting session, e.g. what to prioritize based on the majority of the votes.
Which teams should use dot voting?
Dot voting is popular amongst UX designers and product teams, but any other team can benefit from it. This methodology is a great tool for making decision-making more equal, and it brings effectiveness to sprint planning and prioritization of tasks.
Get started with this template right now.
Kanban Framework Template
Works best for:
Kanban Boards, Agile Methodology, Agile Workflows
Optimized processes, improved flow, and increased value for your customers — that’s what the Kanban method can help you achieve. Based on a set of lean principles and practices (and created in the 1950s by a Toyota Automotive employee), Kanban helps your team reduce waste, address numerous other issues, and collaborate on fixing them together. You can use our simple Kanban template to both closely monitor the progress of all work and to display work to yourself and cross-functional partners, so that the behind-the-scenes nature of software is revealed.
Meeting Reflection Template
Works best for:
Meetings, Brainstorming, Team Meetings
When schedules get hectic, “learning by doing” becomes the default way to learn. So make time for your team to learn in other valuable ways — by reflecting and listening. Led by “learners,” (team members who share with the rest of the team), a meeting reflection lets teammates share new information about a client’s business or an internal business initiative, offer problem-solving techniques, or even recommend books or podcasts worth checking out. Meeting reflections also encourage colleagues at all levels to engage in each other’s professional development of their teammates.
Event Planning Template
Works best for:
Whether you’re planning a product launch, fully remote conference, or milestone event, the Event Planning Template will act as a visual checklist and map for all the details you need to consider before the big day. The Event Planning Template is an adaptable way to make sure the creative and strategic vision of your event doesn’t get lost in the details. By mapping out different sections - from the marketing plan, to the agenda, to snacks and swag for guests — you and your team can focus on the details most important to your functions, and collaborate as needed when overlaps occur.
Team Meeting Agenda Template
Works best for:
Documentation, Team Meetings, Workshops
Making the time for your team is important to help you to make decisions, align on priorities, and move in the same direction together. Team meeting agendas help add a schedule and structure to your allocated time slot when you need to share information and collaborate with your team. They also allow your team to agree on goals, talking points, action items, and who will lead the next steps. Uninterrupted team meeting time with an agenda can help your team review progress against OKRs, share updates, discuss roadblocks, and brainstorm ideas.
Quick Retrospective Template
Works best for:
Education, Retrospectives, Meetings
A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. The term “retrospective” has gained popularity over the more common “debriefing” and “post-mortem,” since it’s more value-neutral than the other terms. Some teams refer to these meetings as “sprint retrospectives” or “iteration retrospectives,” “agile retrospectives” or “iteration retrospectives.” Whether you are a scrum team, using the agile methodology, or doing a specific type of retrospective (e.g. a mad, sad, glad retrospective), the goals are generally the same: discovering what went well, identifying the root cause of problems you had, and finding ways to do better in the next iteration.
Daily Stand-up Meeting Template
Works best for:
Agile Methodology, Meetings, Software Development
The entire team meets to review the day before and discuss the day ahead. These daily meetings, also known as “scrums,” are brief but powerful — they identify roadblocks, give each team member a voice, foster collaboration, keep progress on track, and ultimately keep teams working together effectively. This template makes it so easy for you to plan daily standups for your sprint team. It all starts with picking a date and time, creating an agenda, and sticking with the same format throughout the sprint.