One of the hardest questions you face daily is: “What should we do next?”
Stakeholders want their feature delivered now. Developers want clarity and focus. Users want problems solved. And you? You’re stuck balancing it all.
That’s where prioritisation techniques come in. They’re not magic formulas, but they help bring structure to the chaos. Instead of arguing over who shouts loudest, you can use a framework everyone understands.
In this series, I’ll cover the most common ones:
- Effort vs Value Matrix → the simplest visual way to compare options.
- MoSCoW Method → “must, should, could, won’t” prioritisation.
- RICE Scoring → reach, impact, confidence, effort.
- Kano Model → understanding what customers value.
- Cost of Delay (WSJF) → deciding what really can’t wait.
- Story Mapping → seeing priorities through the user journey.
- ICE Scoring → a lightweight cousin of RICE.
Each post will explain:
- What the technique is.
- When to use it.
- How to apply it step by step.
- A quick example.
- Pros and cons.
By the end, you’ll have a toolkit of methods to draw from, depending on your team and context.
