The New Year Strategy Most CEOs Get Backwards

Every January, most CEOs sit down and write a number. Revenue target, margin goal, headcount plan. Then they build a strategy to hit it. The founders who actually break through skip that step entirely and start somewhere else.

I see it every year, usually in the first two weeks of January, when a founder walks into a planning session with a target already fixed in their head. Twelve million. Fifteen. Whatever the growth curve says should come next. The instinct is understandable — a number feels like clarity. It gives the year a shape. But a number is not a strategy. It is a hope with a due date.

The goal-first trap

Goal-first planning has a specific failure mode, and it repeats with almost mechanical consistency. The team sets the number, builds the initiatives to support it, and executes with real effort for eleven months. Then the number doesn't land — not by a catastrophic margin, just short, the way it was short last year and the year before. Everyone works harder. Nobody asks why the same shortfall keeps showing up in the same place.

That question — why does the same wall keep appearing — is the one goal-first planning is specifically designed to avoid. It's more comfortable to set a fresh target than to sit with an uncomfortable diagnosis about what actually capped you last year. Ambition feels like progress. Diagnosis feels like an admission.

A founder I worked with set the same revenue target three years running. Not similar numbers — the same number, almost to the dollar, written into three consecutive annual plans. Each year the plan looked different on paper: new hires, new channels, a new pricing structure. Each year the company landed within five percent of where it had landed the year before. The target wasn't the problem. Nobody had ever stopped to ask what was actually holding the number in place.

Diagnose before you prescribe

When we finally did the work, the answer wasn't a market problem or a talent problem. It was a single bottleneck: every deal above a certain size required the founder's personal involvement to close, and the founder could only be personally involved in so many deals a quarter. That ceiling had been quietly capping revenue for three years while three different growth strategies were built on top of it, none of which touched the actual constraint.

This is the distinction I bring to every planning session now, before a single initiative gets discussed: find the binding constraint before you write the plan. Not the thing that feels most urgent. Not the thing that shows up in the board deck. The one factor that, left unresolved, will cap the business regardless of what else you do well this year.

A binding constraint is rarely the thing an executive team is most eager to discuss. It's usually uncomfortable in a specific way — it often implicates the founder directly, or a hire that hasn't worked out, or a process everyone privately knows is broken but no one has scheduled time to fix. That discomfort is exactly why it survives one planning cycle after another. A market-sizing exercise is a pleasant way to spend an afternoon. Naming the internal mechanism that has quietly capped you for three years is not, and most planning processes are built, whether deliberately or not, to avoid the second kind of conversation entirely.

A goal you have missed three years running is not a motivation problem. It is information — and it has been trying to tell you something the entire time.

Constraint-first planning

The method I use with clients now runs in the opposite order from what most planning processes teach. Three steps, done before any target gets set.

Name the constraint honestly. Not the symptom — the mechanism. "We need more leads" is a symptom. "Every enterprise deal requires my personal presence to close" is a mechanism. The second version can actually be worked on.

Test whether it's structural or behavioral. Structural constraints live in the operating model — a process, a team gap, a system that doesn't exist yet. Behavioral constraints live in the founder — a decision they won't delegate, a standard they won't lower, a habit they won't break. Most constraints are a blend, and the honest ratio matters, because the fix is different for each.

Design the plan to remove it first. Growth initiatives get sequenced after the constraint work, not alongside it. Adding a new sales channel on top of an unresolved bottleneck doesn't multiply growth. It multiplies the number of things now waiting on the same choke point.

The founder with the flat revenue target spent the first quarter of that year doing something that felt, by his own admission, unambitious: building a second closer who could run enterprise deals without him. No new market. No new product. By the back half of the year, revenue moved past the number that had held for three years — not because the target changed, but because the thing capping it finally did.

What this changes about the year ahead

Constraint-first planning produces less exciting kickoff meetings. There's no big number to rally around in January, no bold market expansion to announce. What it produces instead is a plan that actually accounts for why last year happened the way it did — which means this year has a real chance of being different, rather than an optimistic repeat.

The number will take care of itself once the thing actually holding it down is gone. That is the order the work goes in, even though it is rarely the order the calendar invites suggest.