Good prioritization doesn’t have to be complex. Sometimes it just requires balancing quick fixes vs. product (r)evolutions.
This one doesn’t require much explanation.
Draw a matrix like the one above 👆
With your team, evaluate the potential impact and effort for each feature and map them accordingly on the chart
Start working on the low-hanging fruits — quick wins — and work yourself forward to the top right part — these are product (r)evolutions some of which might have disrupting potential. Ignore everything in the lower half.
don’t forget to account for uncertainty. When evaluating effort (but also impact), make sure to ask yourself: Do we have data to back up this estimation? Otherwise you are just relying on a gut feeling.
if you do this, consider using the RICE method, which is not a far stretch from this method.
use an online tool (such as Miro or Mural) to help you with this.
Got questions, ideas or remarks on this method? Join the conversation on