Growth Strategy vs Execution: Why The Gap Kills Growth

There's a tired debate in growth work about whether strategy or execution matters more. It's the wrong argument. The businesses that actually compound don't win because they have better strategy or better execution. They win because they've closed the gap between the two.

Strategy without execution rhythm is noise, a slide deck that ages in a shared drive while the team ships whatever's in front of them. Execution without strategic direction is also noise, a busy team producing campaigns, content, and activity that never adds up to a compounding growth engine. The problem is almost never that one is good and the other is bad. The problem is that they're disconnected.

This article is about what it actually takes to connect the two. The operating logic. The cadence. The cascade from annual ambition to weekly commitment. And the specific places where most growth teams lose the thread, because the thread loss is predictable, and avoidable if you know what to look for.

The Two Failure Modes

Growth operations fail in two characteristic ways. They look different, but they have the same root cause.

Failure Mode 1: Strategy Theatre

The first failure mode is the team that has a beautiful growth strategy and isn't actually running it. The deck exists. The OKRs are written. The quarterly plan is on a wiki page. And yet, if you look at what the team is doing this week, there's almost no visible connection between the strategy and the work.

The signs of strategy theatre: leadership can articulate the plan, but individual contributors can't. Weekly standups focus on what got shipped, not what got learned against the plan. Decisions about new campaigns, hires, or spend get made in the moment rather than against the strategy. The strategy gets reviewed "quarterly" in the sense that it gets dusted off for the board deck, but not in the sense that it actively shapes tactical decisions.

What makes this failure mode insidious is that it looks good from above. The strategy exists. The team is busy. The outputs are visible. It takes a real effort to notice that the strategy and the outputs aren't actually connected, and by the time someone notices, months have been spent on work that wasn't shaped by the direction that was supposed to govern it.

Failure Mode 2: Execution Without Direction

The second failure mode is the inverse. The team is shipping. Campaigns are live, content is publishing, sales is pitching, CRM is humming. The velocity looks great. But when you ask what the team is optimising toward, not at the annual goal level, but at the level of "what are we actually trying to learn or prove this quarter," the answers get vague.

The signs of execution without direction: lots of activity, limited learnings that carry forward. Channels added because they're available rather than because they fit the strategy. Campaigns judged on delivery (did we ship it?) rather than impact (did it move what it was supposed to move?). Every week feels productive; every quarter feels strangely like the last one.

This failure mode is often disguised as discipline. The team is reliable. They ship on time. They hit their sprint commitments. The problem is that the sprint commitments aren't connected to anything larger than themselves, so the velocity compounds into itself rather than into strategic progress.

Strategy theatre is direction without motion. Execution without direction is motion without direction. Either way, the business doesn't compound.

The Root Cause: A Missing Cascade

Both failure modes come from the same structural problem: there's no working cascade between the annual ambition of the business and the weekly commitments of the growth team.

A cascade is the mechanism that translates high-level intent into specific action. It's the thing that answers, at every level: given the layer above, what does this layer need to deliver? Without it, strategy and execution operate in separate universes. Strategy sits at the top, execution happens at the bottom, and there's no connective tissue between them.

Most growth teams have some version of this cascade, but in an incomplete or broken state. The annual goal is clear. The weekly sprints are clear. The quarterly and 90-day layers between them, the ones that actually carry the weight, are either missing, too abstract to be useful, or written once and then ignored.

The Cascade That Actually Holds Together

Here's the full cascade when it's working. Four layers, each feeding the next. Each layer is specific enough to generate the next, and each layer is reviewed on the cadence of the layer above it.

A few things are worth naming about this cascade. None of them are novel. All of them are routinely skipped.

First, each layer must translate to the next without ambiguity. If you can't look at your quarterly OKR and derive a 90-day plan from it, the OKR is too abstract. If your 90-day plan doesn't generate weekly sprint commitments, it's an aspiration document, not a plan. The test of whether a layer is well-formed is whether the next layer falls out of it with minimal debate.

Second, the cadence matters as much as the content. Annual objectives get reviewed annually but shape decisions all year. Quarterly OKRs get set every 90 days with a genuine review of what worked and what didn't. 90-day operating plans get updated monthly, not rewritten, but adjusted based on what's been learned. Weekly sprint commitments get set, shipped, and reflected on every week. Without the cadence, the cascade is just documentation.

Third, the cascade works in both directions. Top-down: the annual objective shapes the quarterly OKRs, which shape the 90-day plan, which generates weekly sprints. Bottom-up: weekly learnings feed into the monthly plan update, which shapes next quarter's OKRs, which feed into whether this year's objectives need revisiting. When the bottom-up flow is missing, the cascade becomes one-way pressure, and teams burn out executing a plan that's no longer supported by the ground truth.

Where the Cascade Breaks (And How to Spot It)

In practice, the cascade almost always breaks at one of three junctions. If growth feels disconnected, either directionless or strategy-heavy, one of these is usually the culprit.

Break Point 1: Annual Objective to Quarterly OKR

Symptom: the annual goal is clear, but the quarterly OKRs feel like a restatement of ongoing activity rather than a genuine quarterly commitment. "Increase pipeline" isn't a quarterly OKR, it's a permanent desire. "Generate £400k in Q2 pipeline from paid channels, with at least 30% from new ICP segment" is a quarterly OKR.

Fix: the quarterly OKR should feel like a choice. What are we specifically going to prove or achieve in the next 90 days that moves us materially toward the annual objective? If the OKR could be written identically three quarters in a row, it's not doing its job.

Break Point 2: Quarterly OKR to 90-Day Operating Plan

Symptom: there's a clear OKR, but the operating plan is either missing or is really a backlog in disguise. "Build out content, run paid campaigns, optimise CRM" is not a 90-day plan, it's a list of activity areas.

Fix: the 90-day plan should name the specific initiatives that will run, in what order, with what expected outcomes. Not a wishlist, a deliberate selection. A 90-day plan that includes everything the team could do is useless. A 90-day plan that includes the 4 to 6 things that will actually happen is the whole point.

Break Point 3: 90-Day Plan to Weekly Sprint

Symptom: the plan exists, the team is shipping, but the weekly work looks strangely unconnected to the plan. People are doing things. The things don't add up.

Fix: every weekly sprint needs to explicitly reference which 90-day initiatives it's advancing. Not as a reporting exercise, as an operating discipline. If a piece of work can't be traced to a named initiative in the 90-day plan, either the plan is incomplete or the work shouldn't be happening.

Pattern we see: A UK-based scaleup we worked with had a solid strategy deck, clear annual goals, and a highly disciplined sprint process. What they didn't have was the middle. Their quarterly OKRs were vague aspirations and their 90-day plan didn't exist in a meaningful form. The sprint work was disciplined; it was just disciplined in 50 different directions at once. Installing the 90-day plan layer (a single-page doc updated monthly, naming the 5 initiatives in flight) produced more strategic clarity than any amount of off-site planning had.

The Operating Rhythm That Makes the Cascade Live

A cascade that exists on paper but isn't operated is the same as no cascade. The thing that turns the framework into a working system is the rhythm, the regular, named moments where the cascade is reviewed, adjusted, and re-connected to the work.

The minimum operating rhythm looks like this:

• Weekly sprint review and planning (30 to 45 minutes). What shipped? What did we learn? What are we committing to next week, and which 90-day initiative does it serve?
• Monthly 90-day plan review (60 to 90 minutes). Where are we against the plan? What's working, what's blocked, what needs to change? Is the plan still the right plan, or have we learned something that requires adjustment?
• Quarterly OKR closeout and reset (half-day). What did we actually achieve this quarter, honestly? What do we now commit to for the next 90 days? What's the updated 90-day plan that flows from it?
• Annual strategy review (one to two days). Is the annual objective still right given what we've learned? What are the commitments for the year ahead?

The specific durations are flexible. What matters is that each layer of the cascade has a named moment where it's reviewed, and that the review is genuine rather than ceremonial. A weekly sprint review that doesn't ever result in changed commitments isn't a review, it's a status update. A quarterly OKR closeout that doesn't honestly grade what was achieved isn't a closeout, it's theatre.

The single biggest differentiator between teams that run a real cascade and teams that run a ceremonial one is whether the rhythm ever produces hard conversations. If nothing ever gets killed, nothing ever gets re-prioritised, nothing ever gets admitted as a miss, the rhythm isn't working. The point of the cadence is to surface the reality and force the adjustments. A rhythm that never forces adjustments has stopped doing its job.

Where This Sits in the NBT Growth Model

The cascade described above is the operating logic that connects Stages 2, 3, and 4 of the NBT Growth Model. The Route Formulation in Stage 2 sets the strategic direction. Navigation in Stage 3 is the execution that runs against that direction. OKR-Driven Optimisation in Stage 4 is the feedback loop that closes the cascade and feeds the next cycle.

None of it works without the cascade. A Growth Route without an OKR cascade is a strategy document. Navigation without a 90-day plan is activity without direction. Optimisation without weekly review rhythm is measurement without learning. The cascade is what turns the four stages from a framework into a functioning operating system.

This is also why we push back hard when teams want to skip to Stage 3, "just start running campaigns, we'll figure out strategy later." That shortcut doesn't save time. It just defers the cascade work until after you've spent budget on activity that was never going to compound.

A Quick Test: Is Your Cascade Working?

The fastest way to check whether your growth team has a working cascade is to ask three people at different levels of the organisation the same question: what are the two or three things growth is specifically trying to prove or deliver this quarter?

If the CEO, the Head of Growth, and an individual contributor all give you broadly the same answer, with meaningful specificity, not just "grow revenue," your cascade is working. If the answers diverge, or if the specificity drops off the further down you go, your cascade has a break somewhere in the three junctions above. Find the break, and the fix is usually faster than adding more strategy, more activity, or more hires.

If the CEO, the Head of Growth, and an individual contributor don't give you broadly the same answer, the cascade has a break. Find it.

The Connective Tissue Is the Work

The industry has spent a lot of energy arguing about whether strategy or execution matters more. The businesses that actually compound understand the question is wrong. Both matter. What decides whether a growth team produces returns is the connective tissue between the two, the cascade, the cadence, the operating rhythm that turns direction into motion and motion back into direction.

Most teams don't lack strategy or execution capability. They lack the infrastructure that connects them. Installing that infrastructure, even minimally, produces more growth than hiring another marketer, buying another tool, or commissioning another strategy deck.

If you want an honest read on whether your growth operation has the connective tissue in place, or where the breaks are, get in touch for a strategy call. We'll walk through the cascade with you and show you where the next highest-leverage fix sits.