When organisations feel pressure to change, speed becomes the dominant virtue. Initiatives are accelerated. Timelines are compressed. Leaders push to show momentum. Speed feels decisive. It signals urgency. It reassures stakeholders that action is being taken.
But speed, on its own, rarely determines whether change succeeds. Sequencing does.
The false trade-off between speed and discipline
In many organisations, sequencing is treated as a luxury. When external pressure rises, leaders assume they must choose between moving quickly and being thoughtful. Sequencing is framed as hesitation. Discipline is framed as delay.1 This is a false trade-off. Poor sequencing creates more drag than slow execution ever does.2 It amplifies confusion, increases rework, and accelerates fatigue. Speed without sequence does not create momentum. It creates noise.
What sequencing actually means
Sequencing is not about doing things one at a time. It is about being deliberate in how changes build on one another. Effective sequencing clarifies:
- which changes are foundational
- which depend on others holding first
- what must stabilise before the next shift
- where capacity will be most strained
- when behaviour needs time to settle
Without this clarity, organisations ask people to adapt to moving targets.
Why speed often increases meaning overload
When multiple changes are pushed forward simultaneously without clear sequence, people are forced to improvise.
They make assumptions about priority. They guess which rules still apply. They hedge by partially adopting everything. This increases meaning overload.3 People spend more time interpreting intent than executing work. Decisions slow, not because people are lazy, but because acting confidently feels risky.
Ironically, efforts to move faster often produce the opposite result.
The compounding cost of poor sequencing
Poor sequencing does not fail loudly. It fails incrementally. It leads to:
- repeated rework as earlier changes are revisited
- benefits delayed because prerequisites never held
- uneven adoption across teams
- rising stabilisation and support costs
- declining confidence in leadership direction
These costs are rarely attributed to sequencing. They are explained away as execution challenges or resistance. By the time sequencing is questioned, value has already leaked.
Why leaders default to speed
Speed is visible. It can be measured, reported, and defended. It fits neatly into governance cycles and external expectations.
Sequencing requires judgement. It forces leaders to acknowledge dependency, capacity limits, and trade-offs. It requires saying no, or not yet, in environments where momentum is prized. Under pressure, speed feels safer.
But safety at the top often transfers risk downward into the organisation.
Translating sequencing into enterprise risk
When sequencing is poor, the risks are concrete. They include:
- investments that do not deliver expected return
- initiatives that stall or reset repeatedly
- benefits that never fully materialise
- increased operational friction
- erosion of confidence in transformation efforts
In public sector contexts, poor sequencing can also increase scrutiny when outcomes fail to align with commitments. These are not change management issues. They are enterprise performance risks.
What effective sequencing looks like in practice
Organisations that sequence well are disciplined about a few things. They are explicit about:
- what must be stable before moving on
- which behaviours need time to embed
- what can wait without undermining credibility
- where speed genuinely matters and where it does not
They treat sequencing as a strategic decision, not a scheduling exercise. This does not slow the organisation. It prevents it from outrunning its own capacity.
Reframing speed as a consequence, not a goal
Speed is an outcome of clarity, not a substitute for it. When priorities are coherent, dependencies are respected, and meaning is clear, organisations move faster naturally.4 Decisions are made with confidence. Adoption is more consistent. Less energy is wasted on rework. When sequencing is ignored, speed becomes performative rather than productive.
A better question for leaders
Instead of asking, “How fast can we move?” leaders would be better served asking, “What needs to hold before the next shift makes sense?”
That question protects capacity, reduces fatigue, and increases the likelihood that change will actually stick. This is one way of thinking about why change succeeds or fails. Other pieces go deeper into how organisations can design change in ways that respect capacity and protect value.
-
Mintzberg, H. (1994). “The Fall and Rise of Strategic Planning.” Harvard Business Review, 72(1), 107–114. Mintzberg’s critique of formal strategic planning argues that planning processes are systematically biased toward action over preparation — discipline is framed as hesitation because sequenced, deliberate planning produces no visible output until it concludes. Organisations under pressure conflate speed of activity with progress, treating thoughtful sequencing as a luxury rather than recognising it as the precondition for speed that is productive rather than performative. ↩︎
-
Beer, M., Eisenstat, R. A., & Spector, B. (1990). “Why Change Programs Don’t Produce Change.” Harvard Business Review, 68(6), 158–166. Beer and colleagues’ research demonstrates that programmatic change launched without task alignment and sequenced capability development creates drag rather than momentum — each subsequent initiative encounters the unresolved residue of the previous one. Poor sequencing does not fail immediately; it accumulates rework, slippage, and inconsistency that erodes the organisation’s confidence in the change’s direction of travel. ↩︎
-
Sterman, J. D. (2000). Business Dynamics: Systems Thinking and Modeling for a Complex World. McGraw-Hill. Sterman’s analysis of simultaneous change in complex systems shows that parallel initiatives without sequencing create competing feedback loops that produce partial adoption as the rational adaptive response — each loop is only partially reinforcing, so behaviour hedges across all of them. The result is the precise pattern described: people partially adopt everything and commit fully to nothing, consuming more interpretive effort than sequential change would require. ↩︎
-
Porter, M. E. (1996). “What Is Strategy?” Harvard Business Review, 74(6), 61–78. Porter argues that competitive advantage is created not by any single activity but by mutually reinforcing activity systems — the fit between activities is what makes strategy robust and difficult to imitate. Applied to sequencing: coherent change creates interdependent reinforcing shifts where each preceding change creates the conditions for the next to succeed. When priorities are coherent and dependencies respected, the organisation’s activity system develops the internal fit that produces natural momentum. ↩︎