Learn how to use dot voting, impact/effort matrices, MoSCoW, and other prioritization techniques to converge on the best ideas after brainstorming.
Divergence is exhilarating. After a good brainstorming session, you might have 50 or 100 ideas on the wall. The energy in the room is high. Everyone contributed. But then comes the hard part: choosing which ideas to pursue. Without a structured convergence process, teams either default to the highest-paid person's opinion (the HiPPO effect), argue until energy runs out, or try to do everything at once and do nothing well.
Prioritization is a design skill, not just a management function. The techniques in this guide give teams a fair, transparent way to move from a broad field of possibilities to a focused set of concepts worth prototyping and testing.
Design thinking is deliberately structured as alternating phases of divergence (generating options) and convergence (selecting from options). Most teams are reasonably good at divergence, especially with the right techniques. Convergence is where things break down, because narrowing options requires making trade-offs, and trade-offs create disagreements.
The goal of structured prioritization is not to eliminate disagreement. It is to make the decision-making process transparent and democratic so that even people whose preferred ideas are not selected feel that the process was fair. This is critical for maintaining team buy-in through the prototype and test stages.
Dot voting (sometimes called "dotmocracy") is the simplest and most widely used convergence technique. Each participant gets a fixed number of dot stickers (typically 3 to 5) and places them on the ideas they find most promising. Ideas with the most dots move forward; ideas with few or no dots are set aside.
First, display all ideas on a wall or whiteboard where everyone can see them simultaneously. Give each participant their dots (physical stickers or marker dots). Allow 5 to 10 minutes for everyone to read through the ideas and place their dots. Participants can distribute dots however they want: one dot per idea, multiple dots on a single idea, or any combination.
After voting, count the dots and rank the ideas. Typically you will see a natural clustering: a few ideas with many dots, a large middle group with one or two dots, and several ideas with none. Take the top-voted ideas (usually the top 3 to 5) forward for further discussion and development.
Silent voting is essential. If people discuss while voting, social pressure distorts the results. Everyone should vote simultaneously and independently. Some facilitators ask participants to turn away from the board while others vote, though this is usually unnecessary if you simply enforce a "no talking during voting" rule.
Category-specific dots add nuance. Give participants dots in two colors: one for "most desirable" and one for "most feasible." Ideas that score high on both dimensions are clear winners. Ideas that are highly desirable but seem infeasible may need creative problem-solving to make them workable.
The impact/effort matrix (also called the 2x2 prioritization matrix) plots ideas on two axes: estimated impact (how much value the idea would create for users) and estimated effort (how much time, money, and complexity would be required to implement it). This creates four quadrants.
Quick wins (high impact, low effort) are the obvious first choices. Big bets (high impact, high effort) are worth pursuing but need careful planning and resource allocation. Fill-ins (low impact, low effort) can be done when capacity allows but should never take priority over quick wins. Money pits (low impact, high effort) should be deprioritized or abandoned.
Draw a large 2x2 grid on a whiteboard. Write "Low Effort" and "High Effort" on the horizontal axis, and "Low Impact" and "High Impact" on the vertical axis. Write each idea on a sticky note. As a group, discuss and place each idea on the grid. The discussion itself is often more valuable than the final placement, because it forces the team to articulate their assumptions about value and cost.
Be honest about effort estimates. Teams consistently underestimate implementation complexity, especially for ideas that sound simple but have hidden dependencies. If anyone on the team raises concerns about hidden effort, take them seriously. It is better to overestimate effort than to commit to an idea that stalls in development.
MoSCoW categorizes ideas or features into four buckets: Must have, Should have, Could have, and Won't have (this time). The strength of MoSCoW is that it explicitly includes a "Won't have" category, which forces the team to make clear decisions about what is out of scope rather than leaving everything vaguely "nice to have."
Must-haves are the features without which the product or prototype fails to address the core user need. These are non-negotiable. Should-haves are important and add significant value, but the product could launch without them. Could-haves are desirable but have minimal impact if excluded. Won't-haves are explicitly deferred to a future iteration.
MoSCoW is most useful when moving from the Ideate stage to the Prototype stage, where you need to decide exactly what to include in your first testable prototype. It forces the discipline of building the minimum viable concept rather than trying to prototype everything at once.
The How/Now/Wow matrix evaluates ideas along two dimensions: originality (how novel is the idea?) and feasibility (how easy is it to implement?). This produces three categories.
Now ideas are easy to implement but not particularly original. They represent incremental improvements and low-hanging fruit. How ideas are original but difficult to implement; they may become feasible in the future with more resources or technology. Wow ideas are the sweet spot: original enough to be exciting and feasible enough to actually build. These are your priority.
The matrix is particularly useful in design thinking because it prevents teams from settling for safe, incremental solutions (all "Now") or getting distracted by visionary ideas that cannot be prototyped and tested within the project timeline (all "How"). The goal is to find the Wow zone where innovation meets practicality.
For more rigorous prioritization, especially when presenting to stakeholders who want quantitative justification, use a weighted scoring model. Define 3 to 5 criteria (for example: user value, technical feasibility, business alignment, speed to implement, differentiation from competitors). Assign a weight to each criterion based on its importance. Score each idea on each criterion from 1 to 5. Multiply scores by weights and sum for a total priority score.
The advantage of feasibility scoring is objectivity and traceability. When someone asks "Why did you choose Idea A over Idea B?", you can point to specific criteria and scores. The disadvantage is that it can create a false sense of precision; the scores are still subjective estimates, just structured ones. Use scoring as a conversation tool, not as a definitive ranking.
The Highest Paid Person's Opinion carries disproportionate weight in most organizations. When a senior leader expresses a preference, team members often adjust their votes or evaluations to align. Counter this by using anonymous voting (dot voting with simultaneous placement), or by having the most senior person vote last or abstain from the initial round.
The first idea discussed in detail tends to become the anchor against which all other ideas are compared. Counter this by randomizing the order in which ideas are presented, or by evaluating all ideas against fixed criteria (like MoSCoW or feasibility scoring) rather than comparing them to each other.
People naturally favor ideas they personally contributed. This is human but counterproductive. The best practice is to anonymize ideas before prioritization so that nobody knows whose idea is whose. In brainwriting sessions, ideas are already somewhat anonymized, which is one reason brainwriting pairs well with dot voting.
In practice, the most effective workshops use a progression of techniques. Start with dot voting to quickly surface the group's collective instinct about which ideas have the most energy. Then take the top-voted ideas and evaluate them more rigorously using an impact/effort matrix or MoSCoW to ensure the group's instinct aligns with practical reality. Finally, use feasibility scoring for the final 3 to 5 candidates if you need a defensible recommendation for stakeholders.
This layered approach respects both intuition and analysis. Dot voting captures gut-level enthusiasm that analytical frameworks sometimes miss. Impact/effort matrices and MoSCoW provide the structural rigor that pure enthusiasm sometimes lacks. Together, they produce decisions that the whole team can support.
Prioritization is not the end of the design thinking process; it is the bridge to prototyping. The ideas that survive prioritization should be turned into testable prototypes as quickly as possible. See our guide on rapid prototyping for techniques to build rough versions fast, and our user testing methods guide for how to evaluate those prototypes with real users.
Remember: the ideas you deprioritized are not dead. They are parked. After testing your first prototype, you may discover that one of the "won't have this time" ideas addresses a need you did not anticipate. Keeping a visible record of all ideas and their prioritization rationale makes it easy to revisit them in future iterations.
Related guides: problem statement examples · design thinking templates · design thinking tools and software
Design Thinker Labs Home · All Guides · How It Works · Pricing