The Strategy Assumes Capabilities That Don’t Exist

This is part 4 of a 6 series post on execution

I used to write strategies that sounded confident as hell. Decisive. Aspirational. The kind that make you feel smart just reading them.

“We’re going to move upmarket.”

“We’re going to become a platform.”

“We’re going to win on mobile.”

If you squinted hard enough, you could almost hear Morgan Freeman narrating the future. And then execution would wobble like a shopping cart with one busted wheel. You know it’s broken, but you push it anyway, pretending it’ll sort itself out by aisle three. It never does. You just learn to steer around it like it’s part of the plan. Meanwhile, the team cares. The values are on the wall. Trust. Teamwork. Dedication. The corporate version of Live. Love. Laugh. Everyone is trying. Everyone is busy. And somehow… nothing quite lines up. That used to confuse me. It shouldn’t have. Because the strategy was quietly assuming something we didn’t actually have.

We treat capabilities like they’re a side effect. Like if we just declare a direction loudly enough, the skills will materialize out of sheer corporate willpower. Strategy as manifestation. Vision board leadership. Say it three times in a QBR and suddenly your team knows how to do enterprise sales.

Capabilities aren’t intentions. They don’t show up because a slide deck said so. They’re built. Slowly. Painfully. With real investment — time, money, reps, and a willingness to look incompetent for a while.

If the strategy requires mobile expertise and no one on the team has ever shipped a mobile product, optimism doesn’t close that gap.
If the strategy depends on an enterprise sales motion and everyone grew up in self-serve or SMB land, that capability doesn’t just appear because the pricing slide changed.

For a long time, I avoided slowing down to build capability. It felt inefficient. Like overhead. Like something we could “figure out along the way.”

That was a mistake. Because capabilities aren’t downstream of strategy. They are the strategy. Or at least the part that determines whether the strategy survives contact with reality. I didn’t fully understand that until I saw a company take it seriously.

Facebook gets talked about like this masterclass in vision. And sure, they were. But that’s not the interesting part. The interesting part is they didn’t lie to themselves about what the strategy required.

When they said “mobile-first,” they didn’t mean it as a slogan. They meant it as an operational reset. Zuckerberg said it plainly: they trained all their engineers to do mobile first. Not a new deck. Not a reorg. Not a tiger team. They trained everyone. Which sounds obvious until you realize how rarely anyone does that.

Most companies say “mobile-first” and keep building like it’s desktop with a smaller screen. They setup small “innovation teams” for what is inevitably a big shift in the market place. Ask Blockbuster. I’m certain they had website just like Netflix’s. Facebook looked at the gap and said, “we don’t know how to do this yet,” and then forced themselves to learn. They rewired workflows. Built new muscle memory. Took the productivity hit. They treated the strategy like a capability problem, not a branding exercise.

And that’s why it worked. Strategy didn’t lead execution. Capability did. This is the part nobody wants to talk about. Because it’s the part that makes you look stupid for a while. Strategy is sexy. Capabilities are humbling. Strategy is a sentence. Capabilities are a system. And we’ve quietly entered a world where that difference matters more than ever.

Not that long ago, advantage came from what you had. Better infrastructure. More data. Bigger teams. You could win just by having more stuff than the other guy. Now? Most of that is table stakes.

Everyone can access the same tools. Spin up the same infrastructure. Build something that looks impressive in a weekend. It’s like we handed everyone a Ferrari and said, “good luck.” Turns out, most people don’t know how to drive stick.

So the advantage shifts. It’s no longer about what you have. It’s about what you can do — repeatedly, under pressure, when things break and nobody’s coming to save you. And this is where most strategies quietly fall apart.

GenAI is just the latest example of this pattern. Everyone has access to the same models. That’s not the advantage. The advantage is whether your team knows how to use them in a way that survives contact with reality — and can keep doing it.

Capabilities are the difference between something that demos well… and something that actually works when it matters.

If you get this right, you win. Because capabilities compound. Tools don’t.

The team that learns how to evaluate, integrate, and operationalize new tools gets better at choosing them. That makes their systems better. That creates better feedback loops. That makes them faster. And now they’re pulling away.

Meanwhile, another team is still in a meeting arguing about which tool to use instead of getting better at using any of them. Six months later, the gap isn’t small. It’s structural. And here’s the part that doesn’t show up in strategy decks: capabilities reveal themselves under constraint.

When the system is under load. When the model is wrong. When the customer is pissed. When someone still has to make a call. That’s when you find out who can debug reality… and who can only narrate it. Which is why this requires something deeper than skill building. It requires identity change.

People have to feel slow again. Experts have to become beginners. Productivity dips before it rises. And most companies bail right there. They call it execution issues. It’s not. It’s that they didn’t want to pay the capability tax. But if you do — if you actually build the muscle — something flips. You stop hoping the strategy works. You start knowing your team can. And at that point, the strategy almost becomes… boring. Because the real thing — the thing that actually matters — is no longer what you say you’re going to do.

It’s what your organization has proven it can do again. And again. And again. That’s the part no one can copy. Not the idea.

The behavior.

And behavior, once embedded, is a lot harder to steal than anything you’ll ever put in a slide.

This is part 1 of a 6 part series on execution

1. I Blamed Execution. The Truth is Much Harder.
2. They never truly believed in the strategy.
3. Incentives, rewards, and mechanisms reinforced behaviors that conflicted with the strategy.
4. We hadn’t developed the skills the strategy required.
5. We had the wrong people for the strategic choices we made.
6. We measured execution poorly — or not at all.