Prioritising Improvement Opportunities

Prioritise improvement opportunities using transparent criteria that reflect expected value, urgency, risk reduction, effort, dependency and confidence in the evidence. Processes become useful when people adopt them, leaders govern them and evidence drives improvement, so priority should follow evidence rather than whoever asks loudest.

• Define transparent criteria and make the resulting decisions visible to everyone who depends on them.
• Score with cross-functional input, so the priority reflects the end-to-end service rather than local efficiency.
• Check capacity and dependencies. Ignoring change capacity is a named pitfall, as is treating scores as false precision.
• Revisit priorities as evidence changes. In the article's example, a low-cost knowledge fix outranks a complex automation because it addresses the same demand sooner with stronger evidence.
• Measure portfolio value, priority stability and blocked improvement age as a set, each with an agreed baseline, data source and owner. Treat choosing the loudest request as a design test the approach should help prevent, record assumptions with a date for checking them, and review results with delivery teams and affected consumers, because operational success and experienced value can diverge.