An initiative tops the digital-transformation scoring sheet, yet its impact estimate comes from one unsupported opinion. Another initiative has newer evidence and ranks second. Before purchasing an ordered delivery roadmap, examine the inputs behind the ranking: organized arithmetic does not turn assumptions into facts.
Separate a score from its evidence
Reach might come from a clear log, impact from an interview and effort from an initial estimate not yet reviewed technically. Not every input must be measured, but each must be identified as measured, estimated or unknown, with its owner and date.
This examines initiative-ranking foundations before contracting rather than repeating first-process selection or designing a pilot for one project's assumption. Ask why one initiative leads another and which changed information could reverse the order, instead of accepting an apparently final list simply because it is sorted.
A fictional stationery distributor
A distributor compares quotation follow-up with internal approval automation. One manager expects a large follow-up impact; approval volumes and waiting have clearer records. This establishes no superior initiative. It shows different evidence strength and why the highest claimed impact still requires questioning.
Use consistent periods and units when estimating people or events, distinguishing repeat users from repeat transactions. An initiative affecting a small team can still matter despite lower reach. Suppliers should connect estimates to your organization's objective rather than choose units favoring their preferred project.
An evidence ledger for two rows
Begin with two initiatives so the reasoning remains inspectable, expanding later if needed. Attach a reviewable reference to each score or explicitly identify an estimate and its represented population. Missing data is not zero: an unknown may change the decision rather than establish no impact.
| Estimate | Evidence question | What exposes a fragile ranking |
|---|---|---|
| Reach | Which period, population and record support it? | Different periods or a narrow sample |
| Impact | What is supported and what remains opinion? | Optimism alone creates the lead |
| Effort | Are relevant parties and dependencies included? | Excluded external work changes comparison |
| Exception | Why might a lower-scoring initiative go first? | A necessary dependency or disclosed constraint |
Then change an explicit assumption within a reasonable range explained by the specialist and examine whether order reverses. This is decision-sensitivity review, not a live experiment or calculated probability of success. If the ranking changes easily, identify missing knowledge before a larger commitment.
A method can help without deciding for you
GOV.UK guidance links priorities to performance analysis, user research and stakeholder involvement through a clear method suited to lifecycle and capacity. Use that principle to request evidence explanations without imposing government procedures on a private business or one universal review timetable.
The original RICE article compares reach, impact, confidence and effort using internal estimated scales and acknowledges dependencies can override order. Its confidence percentages are neither measured success probabilities nor search volumes. You need not buy a tool or copy its template to ask for supporting evidence.
What should the consultant deliver?
Request candidates with evidence, assumptions, dependencies and exception reasons, followed by documented decisions on what proceeds or waits and why. Weak evidence should produce explicit limits and clarification needs rather than claims of an optimal possible plan or promised dates and returns.
When management and staff disagree, preserve the disagreement, resolution rationale and approver. Do not hide an unknown estimate inside an average. You are purchasing an explainable, reviewable decision process, not a guarantee that the order survives changing information and constraints.
Review starting digital transformation and paid discovery deliverables, then discuss Nextwave consulting with two evidence-backed rows before approving the remaining roadmap.
Method references and limits
The prioritization guidance updated in 2018 and factor and limitation sections of the original 2018 RICE article were read on 4 November 2026. Prepared with AI assistance and information and translation review.
