Your strategy exists in a deck. Your team is executing something else entirely. Every advisor you’ve hired has told you it’s a communication problem. It isn’t. The gap between your strategy and what’s actually happening isn’t a failure of alignment meetings, OKR cascades, or town halls. It’s a failure of architecture. Your strategy was designed at a level of abstraction your organisation literally cannot operationalise. The decision-making infrastructure that’s supposed to translate strategic intent into daily choices doesn’t exist. You don’t have an execution problem. You have a design problem.
The organisation performs alignment while structurally producing divergence
The executive team can articulate the strategy clearly. The slides are sharp. But walk two levels down and ask someone what they’re working on this week — it bears almost no resemblance to what’s in the deck. Teams are busy. Output is high. But the output is disconnected from strategic intent, and nobody can explain how their work ladders up without reciting memorised talking points. The quarterly planning ritual produces documents, not decisions. The all-hands mentions the strategy. The sprint planning doesn’t. Middle managers are translating the strategy into whatever makes sense to them, which means you have as many operational strategies as you have teams.
The fix everyone reaches for — more communication — actually makes it worse. Another all-hands, another strategy doc, another alignment workshop. These create the feeling of alignment without the infrastructure for it. The team leaves the offsite feeling unified. By Wednesday, everyone is back to executing their own interpretation. The organisation has learned to perform alignment while structurally producing divergence. And the more alignment rituals it adds, the more convinced leadership becomes that the problem is being addressed, while the underlying architecture remains unchanged.
The strategy was designed for the founder’s brain, not the organisation’s decision graph
The strategy was built the way technical founders build strategies: comprehensively, precisely, at a systems level. It describes the world accurately. It identifies the right opportunities. It even sequences them correctly. But it was designed for the founder’s brain — someone who holds the entire business model in working memory simultaneously. The organisation doesn’t work like that. It processes strategy through layers: executive to director to manager to IC. Each layer requires a translation function that converts abstract intent into concrete decisions. In most startups between 20 and 60 people, that translation function doesn’t exist.
There’s no mechanism that connects “we’re building the platform for X” to “this means your team says no to Y this quarter.” So every team fills the gap with their own interpretation. The result isn’t chaos — it’s organised divergence. Everyone is executing a strategy. Just not the same one. Arrival’s February 2024 UK administration is the extreme version: a micro-factory manufacturing thesis — strategically coherent — meeting an organisation that couldn’t translate the strategic architecture into operational execution across multiple sites, geographies, and manufacturing formats simultaneously. The strategy wasn’t wrong. The translation layer was never built.
Climate tech amplifies the gap because each operating model needs a different translation
The strategy-execution gap is especially acute in climate tech because organisations juggle hardware and software, government and commercial, mission and margin — each requiring a different operational translation of the same strategic intent. In earth observation, the deck says “analytics-first” but engineering resources stay allocated to satellite operations because the hardware operating model has its own gravitational pull. In energy markets, regulatory shifts invalidate the strategy faster than the org can adapt its decision infrastructure. In clean energy, companies trying to transition from project delivery to platform discover that the strategy was designed for the old operating model and the new one needs a completely different decision architecture.
I come from atmospheric physics, where the gap between a climate model and a weather forecast is entirely a question of infrastructure: the model is useless without the data assimilation pipeline, the downscaling, the delivery mechanism that puts actionable information at the point of decision. Organisations work the same way. Strategy without decision infrastructure is a model nobody can operationalise. The gap closes when the organisation stops treating strategy as a communication problem and starts treating it as an infrastructure problem — building the decision architecture that makes the strategy operational at the point where work actually happens.
For investors, the strategy-execution gap is the variable organisational due diligence is most likely to miss — and the one most likely to explain portfolio underperformance after the check is written. The deck is always good. The founder is always articulate. The strategy is usually right. And then you walk two levels down and the work is disconnected from the intent.
The strategy becomes real not when people understand it, but when the decision infrastructure makes it harder to deviate than to follow. Map where the translation layer breaks between strategic intent and daily operations.