Planned Course vs. Actual Path: Why Quarterly Reviews Find Strategic Drift Too Late
The plan on the wall and the work actually happening are almost never the same thing. Here's what the gap between planned and actual execution costs you, and how to see it in weeks instead of quarters.
Every strategic plan has two versions. The one on the wall, and the one actually being executed.
The version on the wall is the strategy the leadership team agreed to. It's clean, documented, signed off on, and probably rendered in a reasonable typeface. The version being executed is the aggregate of every decision every person in the company has made, every day, since the plan was approved.
Most of the time, these two versions start out roughly matched. And most of the time, they don't stay that way.
The drift between them — what the plan said and what the work actually is — is the most expensive thing in strategic execution. And the way most companies are set up to notice it, they can't catch it until it's already done the damage.
The two versions of every strategic plan: planned course and actual path
Imagine a ship leaving port with a navigation chart. The chart shows the planned route from here to there: the headings to maintain, the waypoints to hit, the expected arrival time. The captain signs off, the crew deploys, and the ship sets out.
Now ask a different question. Not "what does the chart say?" but "where is the ship right now?"
Those are different questions. A navigator who only looks at the chart is telling you where the ship should be. A navigator who only looks at the ship's position is telling you where the ship is. You need both — but more than that, you need to be able to see both at the same time, so you can notice when they've started to diverge.
Strategic execution works the same way. The planned course is the strategy the team agreed to. The actual path is the sum of the work actually being done. Most organizations have excellent visibility into the planned course — it's documented, tracked in tools, referenced in reviews — and surprisingly poor visibility into the actual path. They see activity. They don't see drift.
The strategist Stephen Bungay has written about this as the gap between plans, actions, and outcomes — three separate failure points where strategic intent can leak out. The planned-course-versus-actual-path gap is the second of those: between what was decided and what's actually being done. It's the one that's hardest to see from the top, because everything downstream of it — the activity, the reporting, the dashboards — keeps looking fine.
What strategic drift actually looks like in execution
Here's how the gap opens, in a specific case.
In January, the leadership team agrees that the company's top strategic priority is moving upmarket. The objective is clean: land five enterprise customers above $500K ARR by year-end. Every function nods. The plan is cascaded.
In week two, a Sales AE closes a mid-market deal at $120K. Good quarter, good logo, fast close. The leader celebrates. Pipeline fills with more mid-market prospects because that's what's converting. Nobody's doing anything wrong.
In week four, Product ships a feature aimed at the mid-market segment because that's where the revenue is landing. The product roadmap subtly reorients. Still inside the plan on paper — the feature is "for customer acquisition" — but the definition of "customer" has quietly shifted.
In week six, Marketing adjusts positioning to match what's converting. Now the website is speaking to mid-market buyers with more specificity than it's speaking to enterprise ones.
In week eight, the hiring plan is recalibrated. The next AE hire is a mid-market closer, not an enterprise one, because that's where the urgency is.
In week ten, the board deck shows pipeline growth, revenue traction, and roadmap progress. Every chart is green. The planned course still says move upmarket. The actual path has quietly turned into double down on mid-market.
In week twelve, the quarterly business review happens. Someone asks, "How are we doing on the enterprise motion?" And the answer is: we'll pick it up next quarter.
No single person made a wrong decision. Every individual choice was defensible. But the path has diverged from the plan by a lot, and the mechanisms the company has to notice that divergence only look once a quarter.
The cost of 90-day strategy feedback loops
The reason quarterly reviews fail at catching drift isn't that ninety days is a long time, though it is. It's that drift compounds.
A 5% divergence in week one is a trivial correction. The team has made one defensible decision that was slightly off the planned course; noticing it would cost a single conversation. That conversation doesn't happen because nothing on any dashboard flags the decision as drift — it wasn't a wrong decision, just an off-course one.
A 5% divergence in week one becomes a 10% divergence by week four, because subsequent decisions build on the first. The next hire is made in the drifted direction. The next roadmap choice is made in the drifted direction. The team is now making coherent decisions, but coherent with the drift, not with the plan.
By week eight, the divergence has momentum. Dependencies have formed. Resources have been committed. The cost of correcting the path now isn't a conversation; it's a reorganization. People have started jobs tied to the drifted direction. The pipeline is full of deals that match the drifted ICP, not the planned one. Correcting course means reversing decisions that made sense at the time.
By week twelve, when the review happens, the drift is structural. It can still be corrected — most can — but the correction will be expensive, contentious, and slow. And here's the kicker: most of that cost could have been avoided if anyone had seen the divergence in week two.
The feedback loop isn't the wrong length because ninety days is too long. It's the wrong length because drift compounds faster than ninety days, and a feedback loop has to be shorter than the thing it's trying to catch.
Why mid-market companies stay on quarterly reviews anyway
If the argument for faster feedback is this obvious, why is quarterly still the default?
Partly because the tools most companies use are built around quarterly cadences. OKR platforms refresh quarterly. Reviews are scheduled quarterly. The reporting rhythm fits the financial calendar. Everyone's calibrated to ninety-day cycles because the system runs on ninety-day cycles.
Partly because real-time visibility sounds like a recipe for chaos. Leaders imagine being dragged into course-correction conversations every week, second-guessing their teams, turning the business into a feedback-loop treadmill. That fear is legitimate — if the only thing you build is faster monitoring, you do end up with that problem.
But the fear conflates two different things. Watching the planned-course-versus-actual-path gap in real time isn't the same as intervening on every fluctuation. The point isn't to correct every drift. The point is to see drift when it's cheap, so you can choose whether to correct it, accept it, or formally change the plan to match.
All three are legitimate responses. What isn't legitimate is to not know the drift is happening.
How to close the gap between planned and actual execution
Closing the gap between planned course and actual path doesn't require abandoning quarterly planning. It requires adding a layer underneath it — a continuous one.
In practice, that means a few things.
It means instrumenting the plan, not just documenting it. A plan that lives only as a slide deck or a wiki page is a plan you can only check against reality in set-piece reviews. A plan that's connected to the work being done — linked to the resources deployed, the decisions made, the signals showing up in the business — is a plan you can check against reality continuously.
It means separating signal from noise deliberately. Not every deviation is drift. A mid-market deal that closes in week two doesn't mean the enterprise motion has failed; it might just mean the AE got lucky on a fast cycle. The question is whether the pattern of decisions is accumulating in a direction that diverges from the plan — and that's a question real-time monitoring can answer in a way quarterly reviews can't.
It means changing what reviews are for. If drift is being surfaced continuously, the quarterly review stops being the place where the org discovers it's off course. It becomes the place where the org decides, with full visibility, whether the planned course is still the right one — or whether reality has taught it something worth updating the plan around.
And it means accepting that strategy is less an artifact and more a conversation. The plan on the wall is a snapshot of the best understanding the team had in January. By April, the team knows more. The question isn't whether that's legitimate; it's whether you have a way to update the plan as understanding grows, or whether you're stuck pretending January's version is still the operating reality.
A real-time check you can run this week
The next time you walk past the strategy slide on the wall, try this.
Instead of asking whether the plan is right, ask whether the work happening in the building matches it. Not in aggregate — not "are we hitting our numbers" — but in direction. Are the decisions being made this week the decisions someone executing that plan would be making? Are the hires, the deals, the roadmap choices, the resource shifts all pointing the same way the plan points?
If you can't answer that question quickly, you don't have a visibility problem in some abstract sense. You have a drift problem you won't see until your next quarterly review.
And by then, the correction will be ten times more expensive than it had to be.
DriftlineAI gives leadership teams continuous visibility into the gap between the plan and the path — so drift is surfaced in weeks, not quarters, and course corrections happen while they're still cheap. Book a walkthrough to see how.