The default leadership review is an OKR review. Teams present their key results. Leadership asks about the reds. Owners explain. Notes are taken. The meeting ends.
It feels rigorous. It rarely changes anything.
What an OKR review is actually doing
The OKR review treats every objective as a given. The question is how is it tracking? The implicit assumption is that the right things are on the list, and the only variable is execution against them. The conversation becomes a series of micro-status updates with a side of encouragement and concern.
This is fine for tracking. It is hopeless for steering.
What a portfolio review does instead
A portfolio review treats the set of bets itself as the variable. The question changes from how is each KR doing? to given what we now know, is this still the right portfolio? The reds are not problems to solve — they are evidence to interpret. Sometimes the answer is "push harder." Often the honest answer is "kill it and redirect the capacity."
An OKR review assumes the plan was right. A portfolio review treats the plan as a hypothesis you're allowed to revise mid-quarter.
Three questions a portfolio review asks
- Which bets are paying off faster than we expected? Double down.
- Which bets are signalling that the underlying assumption was wrong? Kill or redirect. Don't grind.
- Which capacity did we free, and what's the highest-value thing to point it at this week?
These questions cannot be answered by looking at green/amber/red. They require looking at the bets as a portfolio — relative performance, relative cost, relative strategic fit.
Why teams default to OKR reviews anyway
Because killing a bet is socially expensive. Someone owns it. Someone hired against it. Someone told the board about it. The OKR review lets everyone stay polite while the bet quietly underperforms for two more quarters.
The portfolio review forces the kill conversation. That's a feature, not a bug. The cost of an unkilled bet compounds. The cost of a clean kill is a single uncomfortable meeting.
The Vindaris view
Reviews change behavior when they change resource allocation. An execution layer that holds the strategic bets, their underlying objectives, the work tagged to them, and the capacity they consume makes the portfolio view possible in real time — not just at the QBR. That's when reviews stop being reporting rituals and start being where the steering happens.