Strategy is what people do
A strategy does not fail in a slide deck. It fails in the weekly choices the organization keeps making when no one is watching.
Most strategy debates stay at the level of ideas: right market, durable advantage, enough focus. Those questions matter. But I have watched strong strategic direction stall for reasons that had little to do with the quality of the idea. The roadmap kept shifting because short-term revenue won. Teams optimized local metrics that undermined the broader goal. A new initiative sounded aligned in a meeting and then died quietly in the operating backlog.
The strategy was not wrong. The organization was not built to carry it.
The strategy people actually follow
Every organization has the strategy leaders describe, and it has the strategy implied by what gets measured, promoted, celebrated, and tolerated. When those diverge, people are rational to follow the second one.
A company can say it is prioritizing quality, retention, or long-term platform work while still compensating teams for shipping volume, closing quarter-end deals, or hitting activity metrics that reward motion over outcomes. People notice. They adapt. The stated strategy loses credibility one local decision at a time.
That is why “poor execution” is often a polite label for something more precise. The strategy was never translated into an operating model: who owns the outcome, what gets cut when capacity is tight, and what gets escalated versus quietly absorbed when two teams read the priority differently.
Local rationality beats central intent
Most strategy fails at the edges. A regional team discounts to hit a target. A product team ships a feature that helps its own metric but adds complexity elsewhere. A support organization optimizes handle time in a way that erodes trust. Each decision can be understandable in isolation. Together they undo a strategy that looked coherent from the top.
In marketplace and operations contexts, this shows up quickly. Leaders can prioritize density, reliability, or partner quality while the local system still rewards coverage spikes, campaign volume, or the deal that closes this month. The field does not ignore the strategy. It follows the scoreboard it was given.
Strategy has to be specific enough to guide tradeoffs in the field, not just inspiring enough to survive a town hall. People need to know what to do when the right long-term choice conflicts with the metric in front of them.
Focus is visible in what stops
One of the most common failure modes is that nobody stops anything. New priorities arrive, but old commitments remain fully funded, fully staffed, and fully defended by the people whose success depends on them. The organization becomes strategically plural: many directions, each with a plausible internal champion.
Real focus is visible in what gets cut, delayed, or de-emphasized. If everything remains important, nothing is. Documents and kickoffs do not create focus. Capacity decisions do.
Operating rhythm is strategy in public
The weekly forums of a business (reviews, prioritization meetings, deal desks, exception huddles) are where strategy either becomes real or gets renegotiated into something else. If those rooms keep rewarding the old tradeoffs, the strategy is already losing, no matter how clear the narrative was last quarter.
This is also why a shared operating picture matters. When teams do not start from the same facts, they cannot hold the same priorities. The strategy splinters into local stories, each technically defensible, none of them coherent as a whole.
When the Tuesday behavior is fuzzy, the document was never the strategy.
A better test
Instead of asking whether a strategy is smart, I find it more useful to ask: “What would someone in the middle of the organization do differently on a random Tuesday because this strategy exists?”
If the answer is unclear, the problem is probably not insight. It is incentives, ownership, subtraction, and the everyday rhythm that turns intent into behavior. Strategy that survives contact with the organization looks less like a document and more like a habit the system can repeat without heroics.