• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Practice : Prioritisation by Value and Risk

Purpose and Strategic Importance

Prioritisation by Value and Risk helps teams and stakeholders make better decisions about what to do next by assessing the potential value of a piece of work alongside the uncertainty, complexity, or risk it carries.

This practice ensures effort is focused where it matters most—either to unlock the highest value or reduce the most significant unknowns. It drives better economic outcomes, aligns delivery to strategy, and fosters a more transparent and defensible prioritisation process.


Description of the Practice

  • Backlog items are prioritised not only by business value, but also by delivery risk, complexity, urgency, or learning potential.
  • Teams use frameworks such as:
    • WSJF (Weighted Shortest Job First)
    • Impact vs. Effort
    • Value vs. Risk Matrices
  • Value and risk are assessed collaboratively using real data where possible.
  • High-risk, high-value items may be prioritised for early experimentation, not immediate delivery.
  • Prioritisation is revisited frequently to reflect feedback, dependencies, and strategy shifts.

How to Practise It (Playbook)

1. Getting Started

  • Define what “value” and “risk” mean in your context (e.g. revenue, learning, user impact, delivery uncertainty).
  • Pick a simple framework (e.g. Impact vs. Effort quadrant) to sort backlog items.
  • Score or assess items collaboratively during refinement or planning.
  • Use the outputs to guide sequencing discussions—not dictate them.

2. Scaling and Maturing

  • Introduce WSJF or more advanced value modelling to reflect cost of delay, opportunity size, or strategic alignment.
  • Combine quantitative metrics (e.g. adoption data, support volume) with qualitative signals (e.g. customer feedback).
  • Link prioritisation outcomes to OKRs or roadmap themes.
  • Track whether top-priority items actually deliver the expected outcomes.

3. Team Behaviours to Encourage

  • Ask “What value will this deliver?” and “What do we need to learn?” before committing work.
  • Challenge legacy items that remain high effort, low value.
  • Treat prioritisation as a learning process, not a one-off decision.
  • Use transparency to build stakeholder trust in how decisions are made.

4. Watch Out For…

  • Value being defined too narrowly (e.g. only by revenue).
  • Over-analysis that delays decision-making or stifles flow.
  • Risky or novel work being deprioritised due to uncertainty.
  • Prioritisation being owned by one role or disconnected from the team.

5. Signals of Success

  • Teams consistently work on what matters most.
  • Stakeholders understand and support how prioritisation decisions are made.
  • Delivery leads to real outcomes—not just output.
  • High-risk work is explored early, reducing downstream surprises.
  • Prioritisation adapts to feedback and strategy without drama.
Associated Standards
  • Backlogs are prioritised based on measurable business value

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering