Why Marketing Transformation Doesn't Scale

There's a powerful case for treating tactics as strategy.

Move fast. Be native to every platform. Produce at volume. Win the algorithm. Some of the most influential voices in marketing argue that this is the work, that speed and platform fluency matter more than grand strategic frameworks. And for some companies, they're right. Social-native brands, lean startups, small teams where everyone holds the whole brand in their heads can operate this way and win.

The problem is what happens when you try to run that playbook at scale.

A few weeks ago, I was talking with the CEO of a creative agency that's increasingly moving into strategy work. She mentioned something that stopped me: many of the companies she works with have absorbed the tactics-first mindset completely. They're not unsophisticated. They're executing well, fast content, sharp creative, native to every platform. But there's no accumulation from one effort to the next. No principles guiding what it all should express. No foundation underneath the speed.

When you're twenty people, you don't need that foundation. Everyone already knows what the brand stands for. The founder is in the room. Coherence is automatic.

When you're a thousand people across thirty markets, it isn't. You fragment. The tactics stay sharp but they disconnect from each other. Speed without coherence. Volume without accumulation. And then surprise when the brand doesn't compound.

That's the first version of a pattern I keep seeing, but it's not the only one. More sophisticated companies fall into more sophisticated traps. And all of them share the same underlying flaw. I'm using marketing as the lens here because it's where the pressure is most acute right now (the agency restructurings, the arrival of AI, the collapse of old models). But the pattern runs deeper than marketing.

Four Approaches That Don't Scale

Execution without architecture. In marketing, this looks like the tactics-first mindset: fast, native, high-volume execution. Works brilliantly at small scale. Breaks at large scale, because coherence can't be maintained through proximity when the team spans continents and the brand touches a thousand different contexts every day. There's nothing to build on.

The false trade-off. More sophisticated. In marketing, it shows up as the brand-versus-performance debate: recognition that brand building and performance marketing serve different purposes, one creating demand and the other harvesting it. But the pressure to prove ROI pushes budgets toward what's measurable. Short-term activation wins; long-term brand gets starved. You're perpetually harvesting demand you never built, and eventually the field runs dry.

The tool trap. New martech stack, new data platform, new AI tools. It feels like progress. But this is where the most money gets spent and the least value gets built. Early adopters figure out how to make the tools work. Results improve, for a while. Then those people move on, the consultants finish their engagement, and the gains erode. Training doesn't fix it. It just moves the dependency from the vendors to the people who got trained. When they leave, the capability leaves with them.

Rented expertise. The most sophisticated of all, and the hardest to see. You diagnose a capability gap correctly. You hire the right agency, bring in the right consultant, build the right specialist team. The response is smart, targeted, effective. But the capability concentrates in the specialist rather than spreading across the company. When the engagement ends or the team disbands, the ability to operate goes with them. The company felt modern and proactive. It never learned to do it itself.

Four approaches. Each more advanced than the last. None of them scale.

If you're not in marketing, you've still seen this pattern. Swap "brand" for "sustainability" or "AI adoption" and the four approaches look exactly the same. The ingredients change. The trap doesn't.

This is the pattern I named last month: most strategic investments depreciate. The investment was real; the return was rented, not built.

What Scales Instead

None of the four approaches are wrong. You need execution speed. You need to navigate the trade-offs. You need good tools and specialist knowledge. The problem isn't any single ingredient — it's treating each one as sufficient, or pursuing them in isolation. Without principles connecting them, every investment depreciates on its own.

I learned this the hard way. Years ago, I led work on how sustainability shows up in our brand — the communications, product design, packaging, retail experience, the whole system. The easy path would have been training. Workshops for designers. Sessions for retail teams. It would have worked locally, but it wouldn't have scaled. Every new hire, every new market would need the same training. And when trained people moved on, the understanding would leave with them.

Instead, we built principles specific enough to guide choices: what sustainability means for a product designer making material decisions, for a retail team designing store experiences, for a customer service rep answering environmental questions. Not "here's what sustainability means" but "here's how to make sustainability-consistent decisions in your context."

Training would have created 500 people who understood sustainability. Infrastructure created a company that makes good sustainability decisions, including people who joined years after the work was done and never attended a single workshop. If you've led transformation at any scale, you've seen both versions. The second is rarer. And you can feel the difference the moment you walk into the room.

A caveat: infrastructure isn't automatically good. The wrong infrastructure (rigid processes, outdated principles, systems that encode yesterday's thinking) can prevent transformation rather than enable it. "We've always done it this way" is often infrastructure speaking. The question isn't whether you have infrastructure. It's whether it enables judgment or boxes it in. Rules that box people in go stale the moment the context changes. Principles that enable judgment flex across situations they were never designed for.

This is where the departure test — which I explored in depth last month — becomes practical. If the people who built it left tomorrow, would it keep working? If it's enabling judgment, it'll survive the departure. If it's boxing people in, it was never really infrastructure. It was someone else's decisions disguised as a system.

From Sitting Up to Running

It starts with sitting up. The basics are documented. Rules exist. Without them, chaos. But rules don't scale because every new context needs someone at the centre to translate. Tools are present but disconnected from any shared logic. Specialist knowledge concentrates in a few heads. Speed exists, but it's directionless, fast without being coherent. And the big trade-offs (in marketing: brand versus performance; in sustainability: compliance versus value creation) sit unresolved, usually fought over in budget cycles.

Then crawling. Principles get spelled out — how to think, not just what to do. People start to get it, but it's patchy. The trade-offs are being named, people can see they're connected rather than opposed, but they haven't been resolved through shared principles yet. Tools are starting to serve the principles rather than operating on their own. Specialist knowledge is beginning to transfer, inconsistently. You've got understanding without confidence.

Walking changes the feel of a company. Principles are embedded and practised. People make decisions without checking with the centre. The trade-offs that paralysed earlier stages are now navigated through principles: people know which way to lean and why. Specialists coach rather than own. Their job shifts from doing the work to building others' ability to do it. Tools are used through the lens of principles. New hires pick it up from colleagues, not documentation. You're moving, but stretch too fast and you'll stumble.

Running is where infrastructure starts to sustain itself. Capability builds across every team, every market. Speed and coherence reinforce each other: fast execution strengthens the brand rather than fragmenting it. Trade-offs are navigated instinctively. Tools strengthen the whole system rather than adding isolated capabilities. Specialist knowledge has spread. The company no longer depends on the people who brought it in. People who joined years after the work was done operate with the same judgment as those who built it.

In brand, this progression is concrete. A company sitting up has brand guidelines and a brand team everyone depends on, and the brand-versus-performance debate runs unresolved underneath every budget meeting. Crawling, it has principles like "local relevance strengthens global brand" but people aren't sure how far they can push. Walking, teams develop campaigns and share them with the brand team for feedback, not approval. Running, a team in Singapore develops a Lunar New Year campaign, launches it, and shares learnings with the team in Brazil planning for Carnival. The brand team isn't involved in either, and no one's arguing about brand versus performance because the infrastructure makes it one conversation.

Most transformations invest in helping companies sit up better. Nicer documentation. Clearer templates. Fancier tools. More training. Each of those matters. You can't skip from sitting up to running without them. But they only drive the progression when connected by principles. Without that connective tissue, you get better-equipped people still waiting for someone at the centre to approve their work.

Building this isn't a quarter's work. For most companies, moving from sitting up to walking takes 12–18 months. Reaching running, where infrastructure is truly self-sustaining, often takes 2–3 years. The investment is front-loaded; the returns compound over time. But the early signs show up much sooner. Within a few months, you'll notice the questions changing. Fewer people asking "can I do this?" and more asking "here's what I'm thinking, does this hold?" The volume of escalations drops. Local teams start making decisions they previously would have referred upward. The quality of mistakes shifts: from random guesses to principled attempts that miss intelligently.

None of these show up in a dashboard. All of them tell you something is shifting.

The Path Forward

Consider what rented capability actually costs. Every time capability walks out the door, you're not starting from zero. You're starting from zero having already spent the budget to get somewhere. A company that restarts its transformation every three years doesn't spend 1x. It spends 3x for 1x of value. The board paper never frames it that way, but the pattern is stark.

The four approaches aren't wrong. They're incomplete. They don't add up on their own. They compound only when connected by principles that guide how they're used, and embedded in infrastructure that doesn't depend on the people who built it.

In marketing, this means brand can't be built by the marketing team alone. Customers don't experience your brand in silos. They don't separate your ad from your pricing from your call centre from your checkout. Everyone who touches the customer builds brand, whether they know it or not. And they need infrastructure: shared principles that enable good decisions without anyone else being in the room. That's an enterprise problem, not a marketing problem.

If you're leading marketing transformation, the question isn't "how do we improve our brand marketing?" It's "what infrastructure would let a thousand people make brand-building decisions without checking with us first?" Are we helping people sit up better, or building what helps them run?

If you're on a board approving transformation budgets, ask a question that rarely appears in business cases: what's the half-life of this investment? Not the projected ROI. The structural durability. Will this capability be worth more in three years or less? If the honest answer is "less," you're not approving an investment. You're approving an expense with a transformation label.

And if you're a CEO, ask yourself: where am I the human switchboard? Where does quality depend on my judgment rather than on systems others can use? Every place you find one is a place where capability is concentrating rather than spreading, and where the company is more fragile than it looks.

These questions apply whether your transformation is about brand, sustainability, AI, or any other capability you need at scale. The ingredients change. The trap doesn't. And the way out is always the same — principles that enable judgment, embedded in how decisions get made, spreading without depending on the people who built them.

The ingredients you can buy. The connective tissue you have to build.

Next month: why the landscape shifting around you makes this more urgent than you think.