What leadership actually needs to see in a portfolio review

Many portfolio reviews follow the same pattern. A long deck of project status slides, mostly green, a few amber. A discussion of the red ones. Some questions about dates. The meeting ends without a single decision about where to invest.

Leadership visibility isn't about seeing more status. It's about seeing the choices that need to be made, with enough evidence to make them. A good portfolio review is built around those choices.

What leaders actually need

Executives reviewing a technology portfolio are trying to answer five questions, the same five that make up the PROVE method:

1. Is each request solving a real problem with a measurable objective? (Pinpoint the opportunity)
2. Are we investing in the most valuable things, including the health of what we already run? (Rank by value)
3. Who is accountable for each commitment, and on what case? (Own the decision)
4. Can we trust our commitments? (Validate delivery)
5. Is the work paying off? (Evaluate the outcome)

A status slide per project answers none of these directly.

Five views that give real visibility

1. Decisions needed

Start the meeting with the list of decisions leaders must make today: new investments awaiting approval, initiatives asking to change scope or date, proposals to stop or pause. Each with a recommendation and the evidence. If there are no decisions needed, the meeting can be short.

2. The portfolio on one page

A value vs. complexity matrix or a ranked list shows the whole portfolio at once. Leaders can see at a glance whether capacity is going to high-value work and how much is in the "reconsider" zone.

3. Commitments at risk

Not every amber item, just the commitments whose forecast has moved past the committed date, or whose key assumptions have changed. For each: what changed, what the options are, and what the team recommends. See Leading indicators of project trouble.

4. Outcomes against targets

For recently completed investments, did the outcome measures move? This is the view most reviews lack, and the one that most improves future decisions. See Benefits realization.

5. Capacity and health

How much capacity is committed versus available, and how much is going to unplanned work and technical health. Trends matter more than snapshots. See IT capacity planning.

A 60-minute agenda

Decisions come first, while attention is fresh. Status that doesn't need discussion is available in the pre-read or the tool, not presented.

Show what you don't know

Leadership often sees a dashboard of confident numbers that hide large gaps. Be explicit about missing evidence: how many initiatives lack outcome measures, how many have unscored value, which forecasts have low confidence. Showing gaps builds trust, and it's often the trigger for leaders to insist that the evidence is collected.

Record decisions in the meeting

Every decision made in the review should be recorded before the meeting ends: what was decided, by whom, why, and what happens next. Decisions recorded later tend to drift from what was actually agreed. See Designing a project approval workflow.

Common mistakes

• Presenting every project. If 40 initiatives each get two minutes, the meeting is over before any decision.
• Status only in color. Green, amber and red mix up four different questions. Show the specific concern.
• No pre-read discipline. If leaders don't review the material beforehand, keep the pre-read to one page.
• Never reviewing outcomes. Without outcome evidence, the review can only discuss delivery.

How Aizu helps

Aizu gives leaders the portfolio views a review needs: a value and complexity matrix, a risk matrix, items awaiting decisions, open gates, delivery confidence, and outcome targets against measured actuals, filterable by department and product. Coverage counts show where evidence is missing, so blank means unknown rather than zero. Approval decisions are recorded with their rationale, which makes the next review's starting point clear. Related: Why IT dashboards fail to drive decisions.