Workshop · Prioritisation
Ideas come in from phones, the room places each on impact and effort, disputed ones go to a vote, and the top bet gets a MoSCoW call.
Free to use and to run live. No card needed.
A priority matrix sorts ideas by impact and effort into quick wins, big bets, fill-ins and money pits. This template collects ideas from everyone's phone, lets the room place each on a live impact and effort grid, settles disputes with a vote, adds a MoSCoW call on the top big bet and ends with owners in 45 minutes.
01Inside
Impact and effort with 4 areas, and a 45-minute agenda that runs it.
“Add one idea we could act on. One idea per note.”
Axes: Effort → across, Impact → up.
By the end of this meeting, every idea is placed on impact and effort, quick wins have owners and we've committed to one big bet.
02In the room
The shared screen, every phone and the summary afterwards, drawn from this template.
On the shared screen
Ideas land on the board from every phone, with no names on the notes. Then everyone dot-votes what matters most.
On every phone
People scan the code or tap their invite and answer in the phone's browser. No app to install, no account to make.
Afterwards
Decisions and actions are captured as they're said. When the meeting ends, everyone gets the summary, and one link shares it.
03How to run it
Restate the goal so 'impact' means the same thing to everyone.
Collect ideas from phones; they land below the grid, one per card.
Place each idea together: you drag, the room calls high or low. Use the vote for any card people can't agree on.
Commit to the quick wins with owners, pick one big bet with a MoSCoW call, and say out loud which money pits you're dropping.
04Questions
Still deciding?
Run your next meeting on it. Every new account gets Pro free for 14 days, no card.
A 2x2 grid with impact on one axis and effort on the other. High impact, low effort ideas are quick wins; high impact, high effort are big bets; low impact, low effort are fill-ins; low impact, high effort are money pits.
A method that sorts requirements into Must have, Should have, Could have and Won't have (this time). It's common in agile and product work to agree scope for a release.
They're usually the same idea: a grid that ranks options by two factors, such as impact and effort or urgency and importance.
The structure, wording and safety points in this template follow these published sources.
Keep going
Change anything in the editor. When you're ready, press Run live: everyone joins with a scan and answers on their phone.
Free forever · Pro free for 14 days · No card needed · Guests never sign up
Priority matrixFree template