Prioritisation & Trade-offs
Prioritisation is the skill of deciding what not to build and defending it. It is assessed on the quality of the reasoning and the explicitness of what was cut — not on which framework someone names.
Also called: roadmapping, product prioritization, scope management
What is prioritisation & trade-offs?
Prioritisation covers sequencing work under real constraints, making trade-offs between competing stakeholders, stating the cost of each decision, and communicating a cut so the people affected accept it.
Every roadmap looks reasonable until constraints bite. The people who can hold a line under pressure and explain why are rare, and the ability is invisible on a CV — it looks identical to the person who shipped the same features by saying yes to everything.
What do the levels of prioritisation & trade-offs mean?
Four levels, each defined by observable behaviour rather than by years. This is the definition employers set their bar against, and the one every proof is scored to.
- L1Aware
Can order a backlog by stated importance.
Evidence: A prioritised backlog with reasons.
- L2Working
Weighs effort against impact and can justify a sequence when asked.
Evidence: A sequenced plan with effort/impact reasoning.
- L3Independent
Makes and defends cuts under conflicting pressure, names the cost of each decision, and communicates it to the person who loses.
Evidence: A decision record naming what was cut, why, and how it was communicated.
- L4Leading
Sets the prioritisation model an organisation uses and holds the line on it across teams and quarters.
Evidence: An adopted prioritisation framework with decisions traced to it.
| Level | Label | People proven here |
|---|---|---|
| L1 | Aware | 0 |
| L2 | Working | 0 |
| L3 | Independent | 1 |
| L4 | Leading | 0 |
How is prioritisation & trade-offs assessed?
Candidates receive a roadmap, a fixed capacity, and three stakeholders who each want something different. Scoring rewards explicit statements of what is being sacrificed and why, and a communication plan for the loser of the trade-off.
Which roles require prioritisation & trade-offs?
| Role | Level required | Status |
|---|---|---|
| AI Product Manager | L3 Independent | Required |
| Product Manager | L3 Independent | Required |
| Growth Analyst | L2 Working | Nice to have |
How do you prove prioritisation & trade-offs?
Prioritisation & Trade-offs: questions people ask
- Do I need to know RICE or MoSCoW?
- No. Naming a framework scores nothing on its own. What scores is whether your reasoning holds up and whether you were explicit about the cost of what you cut.
- How is this different from project management?
- Project management sequences agreed work. Prioritisation decides which work does not happen at all — and defends that to people who wanted it. The challenge specifically tests the second.
- What level do most product roles need?
- Level 3 for any role owning a roadmap. Level 2 is usually enough for roles executing within a set direction.