There is a moment in the life of a growing marketing function when someone decides that strategy and execution are two different jobs. A strategist develops the plan. Executers implement it. The strategist’s job ends when the brief is delivered. The executer’s job begins. The two groups operate in different rhythms, with different information, evaluated on different outcomes.
This seems like it should work. It often doesn’t.
The failure is not always obvious immediately. The campaigns run. The reports get produced. The organization continues to operate. But something starts to happen in the gap between the strategy document and the work that gets done: decisions accumulate that the strategy didn’t anticipate. The market shifts slightly. The audience behaves differently than the brief assumed. The channel produces results that don’t fit the model. And because the person who set the strategy is no longer in the room, the person executing has to make judgment calls about what the strategy actually intended — and those calls compound across hundreds of small decisions that nobody is tracking.
Where the gap lives
The strategic intent, by the time it reaches execution, has usually passed through several interpretations. The brief gets translated into a creative direction. The creative direction gets translated into copy and creative assets. The assets get translated into channel-specific execution. At each step, something is lost or changed — not through negligence, but because translation is inherently lossy and the original intent isn’t always recoverable from the artifact.
“A strategy that cannot be executed is not a strategy. It is a preference. An execution that isn’t calibrated to clear strategic intent is not marketing. It is activity.”
The result is execution that is technically competent and strategically misaligned. The campaign runs well by its own metrics. The metrics don’t connect to the commercial outcome. The strategist looks at the results and concludes that the execution wasn’t faithful to the brief. The executer looks at the results and concludes that the brief didn’t account for reality. Both are partially right. The actual problem is the structure that separated them in the first place.
How organizations land in this structure
The separation of strategy and execution usually happens for understandable reasons. As organizations grow, specialization becomes necessary. You can’t have everyone thinking about everything. Strategy becomes a leadership function; execution becomes a team function. The distinction seems productive.
What gets lost in the transition is feedback. When the person who set the strategy is also running the execution, they see immediately when the reality differs from the plan. They adjust. The strategy evolves in response to what’s actually happening. When those two things are separated, the feedback loop breaks. The strategy stays fixed. The execution adapts — but informally, inconsistently, without updating the strategic record. The organization doesn’t know what it’s actually doing anymore, because what it planned to do and what it’s actually doing have diverged.
The signal to watch for
If the people executing the campaigns can’t clearly articulate the commercial reasoning behind the decisions they’re making, and if the people who set the strategy are surprised by how the execution looks in practice — the gap is already there. It may not yet be producing visible results, but it is producing invisible drag: time spent on briefs that don’t survive contact with reality, and execution that optimizes for the wrong things.
What keeping them together actually requires
Keeping strategy and execution integrated doesn’t mean the same person does everything. It means the people doing execution have enough strategic context to make good judgment calls when reality diverges from the plan — and the people setting strategy are close enough to execution to update the strategy when it needs updating.
In practice, this usually requires two things. First, strategy needs to be communicated in terms that are usable for execution — not as positioning statements and brand principles, but as clear answers to the questions that actually come up during execution: Who are we reaching? What does that person need to hear from us, and where are they in the buying process? What are we trying to produce from this investment, and how will we know whether we’re producing it?
Second, execution needs to be treated as a source of strategic information, not just a delivery mechanism. What the campaigns produce — not just in terms of clicks and conversions, but in terms of what the audience does and doesn’t respond to — contains real information about whether the strategy is right. Organizations that treat execution output as a feedback mechanism for strategy tend to improve faster than organizations that treat it as evidence that the strategy was correct.
When the separation is forced by scale
There are organizations where some degree of separation is unavoidable — where the volume of execution work makes it impossible for the strategy function to stay close to all of it. In those cases, the integration needs to happen through structure rather than through individual proximity: shared frameworks, clear decision rights, regular structured review of what execution is producing and how it maps to strategic intent.
The goal in those cases is not to eliminate the separation but to prevent it from becoming a wall. The strategy function needs to know what’s actually happening in execution. The execution function needs to know what the strategy is actually trying to achieve. The distance between them should be navigable — not so large that the feedback loop breaks and the two functions start optimizing for different things without anyone noticing.
The organizations where I have seen this work well are not the ones where strategy and execution are formally integrated in an org chart. They are the ones where the people doing execution understand why they’re doing it, and the people setting strategy are willing to update the strategy when the execution reveals that it was wrong. That willingness — to treat strategy as a hypothesis rather than a declaration — is rarer than it should be.
The gap between strategic intent and executed reality tends to accumulate at specific points — a briefing stage, a handoff, a channel where the translation gets lost. If there’s a place in your organization where you’ve watched that happen consistently, I’d find it useful to hear about it. The more specific the location, the more interesting the pattern. Reply: ask@reybelen.com