An outcome scorecard is a one-page record of what an initiative was expected to change, what it actually changed once in production, and what decision that result should trigger in the portfolio. It is the main artifact of the Learn practice and the input to the next round of ranking in Align.
What should an outcome scorecard capture?
Four things, each in a line or two.
What was expected. The outcome hypothesis, the measure that should move first, where that measure stood before the work began, and the level it should reach by a stated date. Without a baseline and a date, any later number can be read as success.
What actually happened. The measured value, when it was measured, and where the number came from. A result with no source gets argued about instead of acted on.
What it cost. The capacity or money consumed so far, in whatever unit the portfolio already uses. A result only means something next to what was spent to get it.
What happens next. A decision to scale, sustain, or retire, a short statement of how confident the team is in the result and why, and the date of the next review that will look at it.
Keep it to one page. A scorecard that runs to three pages will not be read at a portfolio review, and the point of the card is that it gets read.
How do we write a useful outcome hypothesis?
State the change you expect in the world, not the deliverable. "Launch the new intake form" is a deliverable. "Cut average time from request to decision from six weeks to two" is an outcome, and it tells the reviewer what to measure. If the team cannot name a measure, the initiative may not be ready to leave the Approved state of the portfolio view.
Write the hypothesis, the measure, and the target when the work is approved, not when it ships. Filling them in at approval time takes ten minutes. Reconstructing them a year later takes a meeting nobody wants, and the reconstruction tends to match whatever happened.
When is it reviewed?
At the value review, every initiative that has reached Deployed brings its scorecard. The review reads the result and the decision and records a reallocation where one is warranted. Initiatives marked retire come off the view the same day, which is how the active count stays honest.
What does a good outcome scorecard look like?
A good scorecard is written before the work starts and finished after it lands. It measures a change for customers or the organization rather than the delivery of a feature, and two people reading it would agree on whether the target was met. It ends in a decision, not a status, so the portfolio can see which work earns more capacity, which holds steady, and which frees capacity for the next approved item.
The common failures are the reverse of that: targets added after the result is known, measures that count activity rather than change, and a decision row left blank because nobody wanted to say retire.
Where to get help
A 60-minute Portfolio Clarity Session is where to start, and it ends with what fits next. Putting the first scorecards in place for work already in flight is part of a PPM4Agile implementation.