Walk into any monthly leadership review at a fifty-person-plus company and you'll see roughly the same theatre. Teams present their objectives. Owners walk through their key results. The reds get gentle questions. The owners explain. Notes are taken. Somebody says "great, let's revisit in four weeks." The room empties. Almost nothing has changed.
The default review feels rigorous because it has structure, slides, and a quorum. It rarely changes anything because it's asking the wrong question.
What an OKR review is actually doing
The OKR review treats every objective on the page as a given. The question on the table is how is each one tracking? The implicit assumption baked into the format is that the right things are on the list, and the only remaining variable is execution velocity against them. The conversation becomes a series of micro-status updates with a side of encouragement, occasional concern, and a structured opportunity for owners to demonstrate they have a plan.
This is fine for tracking. It is hopeless for steering. The OKR review will tell you, with high fidelity, that initiative seven is amber because the integration is harder than expected. It will not tell you whether initiative seven should still exist, given that initiative three is wildly overperforming and initiative eleven has produced evidence that the underlying market assumption was wrong.
The problem isn't OKRs. OKRs are a perfectly reasonable goal-setting framework. The problem is treating the review of OKRs as the moment when leadership actually decides anything. Decisions require a different question.
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 everything we now know, six or eight weeks in, is this still the right portfolio? The reds on the page stop being problems to solve and start being evidence to interpret. Sometimes the right response to a red is "push harder, we underestimated the work." Often the honest response is "this is the third signal that the assumption underneath this bet was wrong — 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 — even expected — to revise mid-quarter. That shift in framing changes everything that happens in the room, from who speaks first to what counts as a satisfying outcome.
The atmospheric difference is real, too. OKR reviews feel like school. Portfolio reviews feel like investing. The mental motion of an investor is to constantly re-rank a small set of positions against each other, kill the laggards, double down on the leaders, and resist the temptation to grind. Almost no leadership team operates that way against their own strategy, even though it's exactly the motion the strategy requires.
Three questions a portfolio review asks
The mechanics of running one are simpler than the framing suggests. Three questions, asked of the portfolio as a whole, not bet by bet.
The first: which bets are paying off faster than we expected, and what would it look like to double down this quarter rather than waiting for the planning cycle? Most companies under-invest in their winners because the operating cadence is annual; reinforcement is structurally late.
The second: which bets are signalling that the underlying assumption was wrong, and what's the honest case for killing rather than grinding? A bet that's amber for two consecutive cycles deserves a kill conversation, not a "let's give it another month." The kill conversation is the one that's structurally avoided.
The third: which capacity did we free in the last cycle, and what's the highest-value place to point it this week? Freed capacity that doesn't get redeployed quickly drifts back into whatever the team was already doing, which is almost never the highest-value thing available.
These three questions cannot be answered by looking at green/amber/red on a slide. They require looking at the bets as a portfolio — relative performance, relative cost, relative strategic fit, relative learning per euro spent. That comparative view is the entire point of the format.
Why teams default to OKR reviews anyway
Because killing a bet is socially expensive in ways the OKR format protects against. Someone owns the bet. Someone hired against it. Someone told the board about it at the last meeting, with confidence, in their own words. Killing it requires a public acknowledgment that we were wrong, which most leadership teams will spend extraordinary energy to avoid.
The OKR review lets everyone stay polite while the bet quietly underperforms for two more quarters. It's a structural mechanism for deferring discomfort. By the time the year ends and the bet is finally killed, eighteen months of capacity have been spent on it, the team is demoralised, and the kill is rationalised as "we ran the experiment and learned." The truth is the kill was knowable in month two and the format prevented it.
The portfolio review forces the kill conversation into the open. That's a feature, not a bug. The cost of an unkilled bet compounds — capacity, focus, narrative coherence, team morale. The cost of a clean kill is a single uncomfortable meeting and a re-pitched narrative. Trade the second for the first every time.
The Vindaris view
Reviews change behaviour when they change resource allocation. If a review can end without any reallocation happening, it was never a decision-making meeting — it was a reporting ritual with executives in it. The portfolio review only works when the system underneath it holds the strategic bets, the objectives that ladder to them, the work tagged to those objectives, the capacity each bet consumes, and a way to see all of those moving together in real time.
That's not a reporting feature. It's a different shape of operating system. When you have it, the portfolio view becomes possible week to week, not just at the QBR — and reviews stop being the place where status is performed and start being the place where the company actually steers.