Execution Beats Strategy
Perfect strategy with poor execution teaches you nothing. Good-enough strategy with perfect execution compounds.
- Difficulty
- Easy
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 95%
Vora's argument is not that strategy is unimportant but that it is unlearnable without an execution machine. If your strategy is perfect and your execution is poor, you lose and you learn nothing — you cannot tell whether the strategy or the execution failed. If your strategy is merely good enough and your execution is excellent, you still don't win immediately, but you know the execution was sound, so you can update the strategy, relaunch, and iterate until it is right. Roughly 20% of time on strategy, the bulk on getting it to market and improving the machine.
Origin
A lesson Vora says she was well trained in at Meta, where 'execution eats strategy for breakfast' was said often. She explicitly disclaims coining the phrase — it is a riff on Drucker's 'culture eats strategy for breakfast'. She has written a post called 'Execution beats strategy every time'.
Core principles
- 01Customers never see the whiteboard. They see the product in their hands.
- 02A loss with bad execution is an uninterpretable experiment — you learn nothing about your strategy.
- 03For strategy to be useful it has to change the team's behaviour in a way that creates better customer outcomes.
- 04Strategy is glamorous and execution is not, which is exactly why the allocation drifts wrong.
- 05Seniority does not shift the ratio as much as people expect — senior leaders still work mostly on the execution of the system.
How to run it
- 1
Get a good-enough strategy, fast
You cannot win on a bad strategy, so spend real time here — but target roughly 20% of your time, and aim for 'pointed in the right direction', not perfect.
Watch out The bad strategy is still fatal. 'Execution beats strategy' does not license direction-less work.
- 2
Apply the change test
Ask what will actually change for the customer as a result of this strategy. If the products you build, the prioritisation, or the portfolio allocation don't change, the exercise was a team-bonding session, not a strategy.
Pro tip Concrete change candidates: which products get prioritised, how people are moved between bets, what gets deprioritised now.
Watch out A shiny five-year plan that changes nothing about what you build or how you build it has produced only a feeling.
- 3
Spend the bulk of your time building the execution machine
Confirm the strategy makes sense to customers, get it into the market, and build the system that keeps making it better. Bring the donuts, look at the dashboards, rewrite the spec, grind it out.
Watch out Going away for a year to build a perfect plan means shipping into a market that has changed, customers whose needs have changed, and a different competitive landscape.
- 4
Read the result cleanly
With execution known-good, a loss is now interpretable: it was the strategy. Update the strategy and relaunch through the machine you already have.
- 5
Loop with customer feedback until the strategy is right
Keep cycling: strategy, execute, learn, update. The execution machine is the thing that makes iteration cheap, so it is the asset worth owning.
Pro tip As a senior leader, 'execution' becomes understanding what is slowing people down and unblocking it, tracking how the market is shifting, and constantly improving the system.
In the wild
A team with a perfect strategy but poor execution never gets the strategy to market. They lose, and all they know is that they lost — not whether the strategy or the execution was at fault.
→ Zero learning banked. The next cycle starts from the same ignorance.
Lenny assumes seniority buys more time on vision and strategy. Vora pushes back: even at high levels, most of her time goes to making sure strategy reaches the market — understanding what's slowing people down, unblocking it, tracking market change, absorbing customer feedback.
→ The focus shifts to executing on the system rather than executing on the feature, but the ratio barely moves.
Common mistakes
Confusing the glamour of strategy with its value
Strategy is fun — pie-in-the-sky thinking, second and third order effects, the word 'strategy' in your title. Execution is nuts and bolts and sometimes boring. The mythology, not the maths, is what drives over-allocation.
The year-long plan-then-build
Perfect strategy, go away, build for a year, ship. By launch the market, the customers, their needs and the competition have all moved. You could have solved the problem faster with ongoing feedback.
Treating strategy work as its own output
Strategy exercises make teams feel good and connected, which has some value. But if nothing changes in the products, the prioritisation or the portfolio allocation, that feeling is the entire return.
Is it for you?
Best for
PMs and product leaders who have been told to 'be more strategic' and are drifting into whiteboard work while the roadmap stalls.
Not ideal for
Teams executing hard and fast in a genuinely wrong direction — they need the strategy work first, not more machine.
From the transcript
“if you have great strategy perfect strategy but poor execution you don't win because your strategy never makes it to the market and what's even…”
“you should spend some time maybe it's like 20% of your time but the bulk of your time should be like confirming that strategy actually…”
“I try to like always come back to what's going to change for the customer”
From the episode
Making an impact through authenticity and curiosity
Ami Vora (CPO at Faire, ex-WhatsApp, FB, IG)