The impact effort matrix is a prioritisation technique that places each item on two axes: how much it moves the product goal and how much work it costs. Crossing them gives four quadrants: quick wins (high impact, low effort), big bets (high impact, high effort), fill-ins (low impact, low effort) and avoid (low impact, high effort). It is fast, visual and good for aligning the team before a more detailed method.
How to use
- Write one item per row (up to 30) or import the items from the RICE calculator.
- Score impact and effort from 1 to 5 for each item; 3 or more counts as high.
- See the matrix and the list by quadrant, ordered by impact relative to effort.
- Read the warnings: items scored 3 sit on the middle line and deserve discussion.
- Rename the quadrants in the result if you like, then export as PNG, PDF, CSV or Markdown.
What each field asks for
| Field | What to enter |
|---|---|
| Item | E.g. one-tap payment |
| Impact (1 to 5) | 5 = moves the goal a lot. |
| Effort (1 to 5) | 5 = a lot of team work. |
Example
A grocery app team reviews eight items. One-tap payment (impact 5, effort 2) and search with category filters (4 and 2) are the quick wins. The loyalty points programme (4 and 5), choosing a delivery time slot (4 and 3) and customer product reviews (3 and 3) are big bets; the last two sit on the middle line, so the tool asks for discussion. The shared shopping list and the new icon are fill-ins, and chat with the courier (2 and 4) lands in avoid.
When to use
- In a planning session, to reach a first order with the team in minutes.
- When the backlog has grown and you need to separate what is worth doing now from what to drop.
- To show stakeholders, in a single picture, why some requests are not coming in now.
- As a first pass before scoring the remaining items with RICE or WSJF.
Frequently asked questions
What does each quadrant mean?
Quick wins are worth doing first. Big bets need planning and, ideally, a test first. Fill-ins come in when there is spare capacity. Avoid holds items that cost a lot for the little they deliver.
How should I estimate effort?
Ask the people who will build it for a relative comparison, not an estimate in hours: the simplest item gets 1 and the hardest gets 5. Include design, testing and launch, not just code.
What if everything is high impact?
That is a sign impact is being scored against nothing in particular. Tie the score to a concrete goal and compare the items with each other: only the few that move that goal most get a 4 or 5. The tool warns you when almost everything is high.
How is the matrix different from RICE?
The matrix is quicker and more visual, with two scores per item. RICE separates reach from impact and adds confidence, which helps when items affect audiences of very different sizes. Many teams use the matrix as a first pass and RICE to break ties.
Who should do the scoring?
Impact with the people who know the customer and the goal (product, data, support); effort with the people who build. Scoring together, out loud, surfaces different assumptions, which are worth more than the score itself.
How often should I redo the matrix?
Every planning cycle or whenever something relevant changes: an experiment result, a competitor move, a change of goal. An item that looked like a big bet can become a quick win after a technical discovery.
How does the import from the RICE calculator work?
RICE impact 3, 2, 1, 0.5 and 0.25 becomes 5, 4, 3, 2 and 1. Effort in person-months becomes a band: up to 0.5 is 1; up to 1 is 2; up to 2 is 3; up to 4 is 4; above that, 5. Review the scores after importing.