PROVE · E · EVALUATE THE OUTCOME
Closing the loop: using outcome data to fund the next decision
Outcome reviews only matter if they change the next funding decision. How to feed measured results back into estimates, priorities and business cases.
Many organizations that do measure outcomes stop there. The post-implementation review is completed, the findings are filed, and the next round of investment decisions is made exactly as before, with the same optimistic estimates and the same assumptions.
Closing the loop means using what you learned to make the next decision better. It's the step that turns project value management from a reporting process into organizational learning.
The loop
The five steps of PROVE form a cycle:
- Pinpoint the opportunity and the objective that will show it worked.
- Rank investments based on expected value and complexity.
- Own the decision, with a named owner and a recorded rationale.
- Validate delivery with honest forecasts.
- Evaluate whether the expected value arrived, and learn what that means for future estimates and choices.
- Back to Rank, with better information.
Most organizations do the ranking and the delivery. Some measure the outcome. Very few consistently feed what they learned back into the next ranking. That last move is what this article is about.
Three ways outcome data should change decisions
1. Calibrate estimates
If similar investments have consistently delivered 60 percent of their promised benefit, the next business case for that type of work should be discounted, or at least challenged. The same applies to costs and timelines. Keep a simple record:
| Investment type | Avg. benefit achieved vs. promised | Avg. cost vs. estimate | Avg. duration vs. forecast |
|---|---|---|---|
| Process automation | 85% | 110% | 1.2× |
| Customer-facing portals | 55% | 130% | 1.4× |
| Platform upgrades | n/a (risk) | 140% | 1.6× |
| Reporting and analytics | 70% | 100% | 1.1× |
Even a rough table like this changes conversations. A portal business case promising $1 million a year now prompts the question: what makes this one different from the ones that delivered 55 percent?
2. Continue, change or stop
Outcome data should feed decisions about current investments too. If the first phase of a program missed its outcome target, the second phase deserves a fresh look before funding continues. Was the target unrealistic, was adoption the problem, or is the approach wrong?
3. Rebalance the portfolio
Across many outcomes, patterns emerge. Perhaps internal efficiency work consistently pays off while new customer channels struggle. That's strategic information about where to invest, and it only exists if outcomes are measured and reviewed together. See What leadership needs in a portfolio review.
Making it practical
Keep outcomes in the same system as decisions
When outcome reviews live in a document folder and investment decisions live in slides, the connection is never made. Keep outcomes attached to the investment record, so the next decision forum sees them naturally.
Review lessons quarterly
Once a quarter, look across recent outcome reviews and ask: what should we change about how we estimate, assess or prioritize? Make one or two concrete changes each time, such as adjusting a value scale definition or adding a gate question.
Ask about evidence in every business case
Make it a standard question in the approval workflow: "What happened the last time we invested in something similar?" If no one knows, that itself is useful information.
Recognize honest learning
The loop only works if people report outcomes honestly, including shortfalls. Leaders who respond to a missed target with curiosity rather than blame get better data. See The post-implementation review.
Common objections
"Every project is unique." Every project is different in detail, but similar types of work tend to share patterns of optimism. Calibration doesn't require identical projects.
"We don't have enough outcome data yet." Start now. Even five or six outcome reviews begin to show patterns. The cost of starting late is permanent.
"This will discourage ambitious proposals." It encourages honest ones. Ambitious proposals with realistic estimates are easier to fund with confidence.
How Aizu helps
In Aizu, the decision record, its assumptions and the outcome measurements stay attached to the same initiative. Objectives, key results and KPIs carry targets and recorded actuals over time, and portfolio views distinguish work completed from value achieved. When the next similar request arrives, the evidence from earlier investments is in the same place as the decision being made. Related: Benefits realization.
Frequently asked questions
What does closing the loop mean in portfolio management?
Using measured outcomes from completed investments to improve future decisions, such as calibrating estimates, continuing or stopping current work, and rebalancing the portfolio.
How many outcome reviews do we need before patterns appear?
Even five or six reviews of similar types of investment can reveal useful patterns, especially in how benefits and costs compare with estimates.
Who should own portfolio learning?
The portfolio office or PMO usually facilitates it, but the decision forum must act on it by changing how investments are assessed and approved.
