Once a quarter, the leadership team blocks three hours on the calendar to "review the roadmap." Each owner walks through their slides. Reds get questions and a sympathetic nod. Yellows get a brief mention. Greens get a thumbs-up. The CEO summarises. Coffee is drunk. The team leaves feeling diligent, the kind of diligent that comes from having been present in a long, serious meeting where serious-looking things were discussed.
What didn't happen — and nobody quite notices it didn't happen — is the actual portfolio conversation. Nobody asked whether any of the items on the roadmap should still exist. The list of initiatives that was inherited from last quarter, which was inherited from the planning offsite six months ago, which was loosely related to the strategy as it was understood two years ago, walks out of the meeting intact. Everyone is on track to deliver things, some of which the company shouldn't be doing anymore.
This is not the same meeting. It looks the same. It uses the same room and the same deck template. But it's a different category of decision.
The two reviews and why they get conflated
A roadmap review and a portfolio review answer fundamentally different questions, and a leadership team that runs the first while believing it's running the second is making one of the more expensive mistakes available in operating model design.
A roadmap review asks: are we on track to deliver what we said we would? It is a delivery question. The owner of each initiative reports against a plan, the leadership team identifies blockers, and the conversation is mostly operational — resource constraints, dependency slips, scope clarifications. This is a useful meeting. Every leadership team should have it. It is not, however, a strategic meeting.
A portfolio review asks: given everything we now know that we didn't know when this initiative was created, should we still be doing it? It is a capital allocation question. The strategy may have shifted. A competitor may have moved. A customer segment may have changed. A new opportunity may be on the table that this initiative is implicitly competing with. The portfolio review is the meeting where initiatives are actively killed, deferred, merged or accelerated based on the current state of the world, not the state of the world when they were planned.
Most leadership teams have time on the calendar for the first kind of meeting and exactly none for the second. They then wonder why their portfolio is full of inherited initiatives that nobody can explain — initiatives that started for reasons that were valid eighteen months ago and are no longer load-bearing, but that nobody has the authority or the appetite to stop, because the only meeting that touches them is one that asks about delivery, not about existence.
What an actual portfolio review looks like
A real portfolio review has a different structure than a roadmap review, and the structure is what makes it work. Four properties tend to distinguish the meetings that actually move capital from the meetings that just feel like they do.
First, each initiative is re-justified against the current strategy, not the strategy that existed when it started. The owner has to argue, in two or three sentences, why this initiative is still the best use of the capacity it is consuming, given what the company now knows. The default isn't continuation — the default is "make the case." This is uncomfortable for owners and exactly the discomfort that the review exists to produce.
Second, initiatives that no longer map get killed, not "deprioritised." Deprioritisation is the polite version of killing that allows the initiative to keep consuming capacity at a reduced rate, which is the worst of both worlds — the team is still nominally working on it, just less effectively. A real portfolio review distinguishes between "this is still strategic and we're going to keep funding it" and "this is no longer strategic and we're going to free the capacity." There is no third option that lets a zombie initiative drift through another quarter.
Third, freed capacity is explicitly reallocated, not absorbed. When an initiative is killed, the three engineers, the half-marketer, the budget line — all of those have to be visibly moved to another initiative or returned to a reserve. Otherwise the capacity dissolves into the team's existing workload and no strategic benefit is captured.
Fourth — and this is the cultural change — the default answer is stop, and continuation requires argument. A portfolio in which everything keeps going by default is a portfolio that grows monotonically, because there are always more candidate initiatives than there are ones being killed. Inverting the default — making owners argue for continuation rather than against termination — is what turns the review from theatre into a capital allocation mechanism.
Why companies run the wrong review
The roadmap review is easier on everyone in the room. Nobody has to argue for the existence of their own work. Owners present progress against plans they wrote, against criteria they helped set, on a cadence they're prepared for. The room functions as a supportive audience. Nobody has to deliver bad news that costs someone else their headcount.
The portfolio review is harder for exactly the reasons the roadmap review is easy. Killing initiatives creates losers — owners whose work was terminated, teams who were reassigned, executives whose pet projects were ended. The political cost of running an honest portfolio review every quarter is high enough that most leadership teams quietly avoid it, run a roadmap review instead, and tell themselves they've done the strategic work. They haven't.
The Vindaris view
If your quarterly review cannot kill anything — if no initiative has been ended at one in the last four reviews — it isn't a portfolio review. It's a status meeting wearing a portfolio review's clothes. The test is simple: count the kills. A leadership team that ends three to five percent of its initiatives every quarter is running a real portfolio. A leadership team that ends zero is running a museum.
Run both meetings. Don't conflate them. The roadmap review tells you whether the work is on track. The portfolio review tells you whether the work should be on the list. Most companies are excellent at the first and structurally avoid the second, which is why their strategy and their actual work drift further apart with every passing quarter.