Most strategies fail not because the ideas are wrong, but because everything is attempted at once. When you have ten good moves and the capacity for two, order matters more than ambition. This article shows you how to sequence strategic moves so limited resources create momentum, one win funding the next, instead of a dozen half-finished efforts that all stall.
Why Sequencing Beats Prioritizing
Prioritizing tells you what is important. Sequencing tells you what comes first. They are not the same. A high-priority move can still be the wrong thing to start, because it depends on capabilities you do not yet have.
The root cause of poor sequencing is treating a strategy as a list rather than a chain. Items on a list feel parallel. Links in a chain have direction. Some moves unlock others. Some fund others. Some de-risk others. Ignore that order and you spend early energy on work that cannot pay off until later.
The Three Questions That Set Order
- Dependency: Does this move require something a different move must build first?
- Leverage: Does this move make later moves cheaper, faster, or more certain?
- Proof: Does this move produce evidence that reduces a big unknown?
Moves that score high on leverage and proof usually belong early, even when they feel small. Moves with heavy dependencies belong later, no matter how exciting they are.
Tempo: The Underrated Half of Sequence
Order decides what comes first. Tempo decides how fast and how spaced. Running every move at full speed exhausts teams and hides which effort actually moved the number. A deliberate tempo does the opposite: it concentrates force on one front, confirms the result, then shifts.
This is why staged rollouts outperform big-bang launches so often. Not because the product is better, but because each stage returns information you use to adjust the next.
A Real Scenario
A regional retailer wanted three things: open new stores, launch e-commerce, and build a loyalty program. All three were funded. The team split resources evenly. Twelve months later, all three were behind.
The fix was sequence, not more money. They started with loyalty, because it produced customer data (proof) and raised repeat purchase rates on the existing base (leverage) at low cost. That data then told them which regions justified new stores and what the online catalog should feature. The same budget, reordered, turned a stalled year into a compounding one. The lesson is not that loyalty is always first; it is that the move producing usable information belonged before the moves that consumed it.
Common Mistakes and How to Fix Them
Mistake: Starting with the most visible move
Visible moves attract attention and pressure. Fix: rank by leverage and proof first, then let visibility break ties.
Mistake: Running everything in parallel to look decisive
Parallel effort feels productive but dilutes force and blurs cause and effect. Fix: limit work in progress. Finish and confirm before opening the next front.
Mistake: Sequencing once and freezing it
A sequence is a hypothesis, not a contract. Fix: revisit order after each completed move, because results change what should come next.
Mistake: Confusing quick wins with foundational wins
Easy early wins feel good but may not unlock anything. Fix: prefer early moves that later moves depend on, even when they take longer.
Action Steps
- List every strategic move, then draw the dependencies between them.
- Score each move on dependency, leverage, and proof.
- Place high-leverage, high-proof, low-dependency moves first.
- Set a work-in-progress limit; commit to finishing before starting.
- Define what result would prove a move worked before you begin it.
- Re-sequence remaining moves after each completion.
Conclusion
You rarely lose because you picked bad moves. You lose because you ran them in the wrong order at the wrong tempo. Your next step is simple: take your current strategy, map the dependencies, and identify the one move that makes the most others easier. Start there.
Frequently Asked Questions
How is sequencing different from a roadmap?
A roadmap shows dates. Sequencing shows the logic of order and dependency. A roadmap can be built on a bad sequence and still look organized. Get the sequence right first, then attach dates.
What if two moves genuinely have no dependency?
Then use leverage and proof to break the tie. Choose the one that makes the rest cheaper or removes the biggest unknown. If they are equal on all counts, pick the cheaper one so you preserve capacity.
Doesn’t focusing on one move slow everything down?
It slows the start of some moves but speeds their finish. Concentrated effort completes work faster and produces cleaner signals about what worked, which usually accelerates the whole strategy.
How often should I re-sequence?
After every completed move, and whenever a major assumption changes. Sequence is a living hypothesis about order, not a fixed plan.
References
- Richard Rumelt, Good Strategy Bad Strategy — on coherent action and the chaining of moves.
- Roger Martin and A.G. Lafley, Playing to Win — on cascading strategic choices.