There is a meeting in most leadership calendars called something like "Weekly Leadership Sync" or "Monday Morning Standup" or "EXCO Operating Review." It runs for sixty minutes. It covers every project. Everyone reads from slides they assembled the night before. Nothing changes as a result of it. The room files out reasonably satisfied, and the same conversation runs again next week with marginally different numbers.
That meeting is now your strategy review. It replaced the real one so gradually nobody in the leadership team can tell you exactly when the substitution happened.
What a real strategy review actually does
A strategy review answers three questions, and only three: Are we still pointed at the right objectives? Are the bets we made last quarter still the right bets given what we now know? What needs to change — not just update — based on the last twelve weeks?
Most weekly syncs answer none of those. They answer a completely different set of questions: what happened last week, what will happen next week, and is anyone formally blocked. That has value. It's operational hygiene, and a company that skips operational hygiene falls apart. But operational hygiene is not strategy, and the two things are not interchangeable, no matter how senior the people in the room are.
Status updates make leadership feel informed. Strategy reviews make leadership decide. The two feelings are opposites, and the moment a leadership team can no longer tell which one it's experiencing, the strategic correction mechanism has quietly stopped working.
How the substitution happens
The shift is almost always innocent, which is exactly what makes it hard to notice. It usually goes something like this.
A QBR gets cancelled because the quarter is unusually busy — the CRO is travelling, the product launch is in week eleven, somebody's resignation needs handling. The monthly strategy session that was supposed to bridge two QBRs gets shortened to thirty minutes "just this once." Those thirty minutes get consumed by a project update that needed escalation, because escalation has nowhere else to go. The next month the strategy session is a "quick check-in." Then it stops existing entirely, absorbed into the weekly sync that was already there.
Six months in, the company is running purely on operational cadence with no strategic correction mechanism at all. Nobody decided to remove it. It just stopped being scheduled. The leadership team continues to feel busy and informed, and the strategy continues to drift, and the QBR when it finally happens is mostly a post-mortem on drift that nobody had the cadence to catch.
Three signals your strategy review has been replaced
Walk into your next leadership meeting and check for these. If two of the three are true, the substitution has already happened.
The agenda is a list of projects, not a list of questions. Strategy reviews start from questions — is this bet still right, is this customer segment still the priority, has the market moved. Status updates start from projects — here is project A, here is project B, here is project C. If your agenda is structured by project name, the meeting cannot produce a direction change, because direction change isn't on the agenda.
The decisions made are execution decisions, not direction decisions. "We need to unblock X by reassigning two engineers" is execution. "We need to stop X entirely and redirect that capacity to Y because the bet no longer makes sense" is direction. Execution decisions are necessary; direction decisions are the whole point of a strategy review. If your meeting only produces the first kind, it isn't reviewing strategy. It's grooming a backlog.
Nobody has changed a goal based on what the meeting surfaced. This is the cleanest test. Look at your top-level objectives at the start of last quarter and at the end. If the list is identical — same goals, same targets, same owners — then either you nailed the strategy perfectly twelve weeks in advance, or your strategy review isn't actually reviewing anything. The second explanation is almost always the correct one.
What to put back
The minimum viable strategy review is ninety minutes, quarterly, with exactly three things on the agenda: goal performance and what it implies, the status of each strategic bet against current market reality, and one explicit decision that will change how the team works next quarter. If the meeting produces no direction change, cancel the next one and replace it with a smaller, more honest conversation among the three people who actually need to make the call.
The thing that makes this meeting work isn't the agenda. It's the data the meeting can stand on. A strategy review with no live picture of goal-to-work-to-capacity becomes a slideshow, and a slideshow always degrades into status. If the room can see, in real time, which work is moving which goal and which engineer is allocated where, the meeting has somewhere to go. If it can't, the room defaults to project updates because project updates are the only thing the data supports.
The Vindaris view
Most companies don't need more meetings. They need to recover the one meeting they've already lost. The weekly sync that ate the strategy review isn't malicious — it's what fills the vacuum when the strategy review stops producing direction changes that justify its calendar slot. Put the cadence back, ground it in data that surfaces the direction-change conversation rather than the status-update conversation, and the meeting will earn its ninety minutes again. Otherwise, your strategy is being executed by whoever happens to be in the weekly sync that day — and that isn't strategy execution. That's drift with a recurring invite.