Plan Autopsy —
Section 01 of 04

Every revenue plan rests on a small number of load-bearing assumptions. If those assumptions aren't named explicitly — and tested against real data — the plan is theoretical at best and delusional at worst. The first week of February is the earliest point at which real data exists to run the test.

If a revenue leader cannot immediately name the three load-bearing assumptions in the plan — the ones the entire model sits on — the plan was never stress-tested. It was assembled. And if none of those assumptions has been tested against real data from the first 38 days, the plan is still theoretical.

January is the plan's first contact with reality. It is not a warm-up. It is not a baseline-setting exercise. It is the first test of whether the assumptions embedded in the plan hold when they meet customers, reps, and markets that don't know they're supposed to behave as modelled.

January is not a grace period. It is the first data point. If actual performance diverged from forecast and nobody has documented why, the divergence will repeat. The plan will manage around the gap rather than close it.

SKO decks announce initiatives. February tests whether those initiatives had the resources, the ownership, and the urgency to survive first contact with the operational calendar. Most don't. The ones that die quietly are the most dangerous because the plan still assumes their output.

Strategic initiatives die quietly. Nobody announces the abandonment. Resources get redirected without a decision. If the answer to this question takes more than 60 seconds to produce, the plan is already running on a different set of priorities than the one presented at the SKO.

No plan survives first contact whole. The question is not whether the plan is behind somewhere — it is whether the team has acknowledged where it is behind and documented a specific response. The absence of a documented response means the plan is being managed by optimism, not by action.

Every plan is behind somewhere by February. The question is whether that lag has a documented response or whether it is being managed by optimism about Q2. A plan without a documented response to its first failures is not a plan. It is a wish.

Plans are written in a moment. Revenue plans written in October or November are already three to four months old by February. In that time, competitors have moved, buyers have shifted, economic conditions have changed, and some of the markets the plan was built on have behaved differently than the model assumed.

Plans are written in a moment. Markets move continuously. If the competitive landscape, buyer behaviour, or economic conditions have shifted since November and the plan hasn't been updated to reflect that, the plan is operating on stale intelligence.

Revenue plans contain embedded assumptions about rep capability — ramp time, conversion rates, average deal size, activity volume — that are typically derived from historical averages or aspirational targets. February is the first month in which new hires are being tested, new products are being sold, and new markets are being worked. The gap between assumption and reality shows up here first.

SKOs build plans on the assumption that reps will ramp, convert, and execute at modelled rates. February is the first test of whether those assumptions hold. If ramp is slower, conversion is lower, or execution is inconsistent, the capacity model that underpins the plan is already wrong.

Revenue plans are written as if revenue is the only function in the company. In practice, revenue targets depend on marketing pipeline that hasn't been created yet, product releases that haven't shipped, and customer success capacity that is already stretched. The moment any of those dependencies slips, the revenue plan slips with it — whether or not anyone has acknowledged the connection.

Revenue plans almost always depend on marketing pipeline, product launches, and customer success capacity that other teams own. If those dependencies have slipped and the revenue plan hasn't been updated to reflect the delay, the plan is projecting outcomes from inputs that no longer exist on the same timeline.

Plans without a regular, named, cross-functional review cadence become orphans. Accountability diffuses. Each function manages to its own metrics rather than to the shared plan. By February, the plan exists as a document that everyone references but nobody owns.

Plans without a named owner and a regular review cadence drift. If the people accountable for the plan haven't reviewed it together since the SKO, the plan is being executed but not managed. Those are different things.

Revenue leaders who are managing a Q1 gap almost always answer it by pointing to Q2. Q2 will recover. Q2 is bigger. Q2 has a new product, new pipeline, new hires. The question is whether the inputs that Q2 requires are currently being built. If they aren't, Q2 is a projection with no foundation.

Q2 outcomes are determined by Q1 inputs. If the pipeline, the hiring, the product readiness, or the market development required to hit Q2 numbers isn't already underway, the plan for Q2 is a projection with no foundation. The time to address that is in February, not April.

This question is the most dangerous one in the framework because it requires intellectual honesty from people who have staked professional credibility on the plan being right. It also produces the most valuable output: an honest picture of what the business knows but hasn't yet said in a room where it matters.

This is the most important question. If the honest answer is "nothing" — the plan is either genuinely robust or nobody is willing to say what they know. If the honest answer surfaces material changes, those changes need to happen now. The longer a plan operates on assumptions that the team knows are wrong, the harder the eventual correction becomes.