The Strategy That Cannot Be Sequenced: Why Initiatives Fail When the Order of Operations Is Left Unresolved

Most senior leaders are skilled at choosing what to pursue. The harder discipline, and the one that receives far less deliberate attention, is choosing what to pursue first, and why that order is the only one that will actually work.

Sequencing is not the same as prioritization. A prioritized list tells an organization which work matters most. A sequence tells it which work must be completed before another work can realistically begin, because the second initiative depends on a capability, a decision, a cultural condition, or a structural change that the first one produces. When organizations conflate these two tasks, they approve a coherent portfolio on paper and then watch it fragment in practice.

Why Sequence Gets Skipped

Strategic planning processes are typically designed to evaluate individual initiatives on their own merits: expected return, resource requirement, alignment to strategic intent, level of risk. These are the right questions to ask, but they are insufficient. An initiative that scores well on every dimension in isolation may still be structurally dependent on another initiative that has not yet landed.

The reason sequence rarely appears explicitly in planning discussions is that surfacing it requires a different kind of thinking. Rather than evaluating what an initiative promises, leaders must think through what an initiative assumes, specifically, what organizational state it assumes already exists when it begins. That analysis is more cognitively demanding and less politically comfortable than approving a project on its stated merits.

There is also a social pressure dynamic. When a leadership team has developed genuine enthusiasm for three or four major initiatives, sequencing them forces an uncomfortable conversation: some of this work cannot start yet, and some of the people in this room will need to wait. That conversation often does not happen, and the organization pays for it in execution.

The Dependency That Is Not Documented

Consider a hypothetical situation that is common in practice. An organization decides simultaneously to expand into a new customer segment, restructure its operating model to reduce cost, and invest in a new product development capability. Each of these is a legitimate strategic ambition. None of them is wrong.

But the operating model restructuring, if done first and done well, changes how resources are allocated and how work is approved. The product development investment depends on resource allocation working the way the new model intends. The customer segment expansion depends on the new product capability being functional. The sequence, if mapped explicitly, is obvious: restructure, then build the capability, then expand.

Launched simultaneously, the restructuring creates uncertainty that slows the capability build. The capability build proceeds on assumptions about resource access that the restructuring is actively changing. The segment expansion moves forward on a capability that is not yet stable. Each team is working in good faith. The system is working against all of them.

How to Surface the Hidden Order

A practical approach to sequencing analysis begins with a question leaders rarely ask aloud: what does this initiative need to be true about our organization before it can deliver its intended result?

For each major initiative in a strategic portfolio, the leadership team should identify two to three critical preconditions. These might be structural (a particular function must have clear authority), cultural (managers must be willing to surface problems early), capability-based (the organization must be able to acquire and retain a specific talent profile), or informational (the organization must have operating data that current systems do not yet produce).

Once preconditions are identified, the team maps them against the portfolio. If Initiative B requires a precondition that Initiative A produces, then A must either complete or reach a stable enough state before B can be designed with reliable assumptions. If two initiatives require the same precondition and neither produces it, that precondition is an unplanned dependency that belongs on someone's work list before the planning cycle closes.

This exercise rarely takes long, and it consistently surfaces decisions that the planning process otherwise leaves to chance.

When Parallel Progress Is Possible and When It Is Not

Sequencing analysis does not always conclude that everything must happen serially. Some initiatives genuinely operate independently because their preconditions do not overlap and their outputs do not feed one another. In those cases, parallel progress is appropriate and efficient.

The discipline is in being explicit about which work qualifies for parallel execution and which does not. Without that clarity, organizations default to treating everything as parallel because parallel launch feels like speed. In most cases, it is the opposite. It is the structure that ensures every team spends the first six months of a multi-year initiative working around conditions that another team was supposed to create.

A useful working test: if one of these initiatives were to stall significantly, would it directly impede another initiative's ability to operate as designed? If the honest answer is yes, those two initiatives are in sequence regardless of what the launch plan says.

The Sequencing Conversation as a Leadership Act

For directors and senior leaders, the sequencing conversation is also a communication responsibility. Teams executing individual initiatives need to understand not only what they are building but where they sit in the larger construction order. A team that knows it is producing something another team depends on governs its commitments differently than a team that believes it is simply delivering a project.

When that context is withheld, either because the organization has not worked it out or because communicating it feels too complex, teams make local decisions that are individually rational and collectively disruptive. The team building the foundation makes a pragmatic shortcut. The team building on top of it designs around a foundation that no longer matches what is being delivered.

Communicating sequence is not a briefing exercise. It is the act of giving each team the logic it needs to make good decisions when conditions shift, and conditions always shift.

The Discipline That Compound Returns Require

Strategic initiatives do not produce value the moment they launch. They produce value when the organizational change they intended has fully taken hold. That moment arrives earlier, and at lower cost, when the work was sequenced correctly from the beginning.

The leaders most effective at this are not necessarily the ones who plan the most. They are the ones who slow the planning conversation down long enough to ask, in a specific and rigorous way, what this work needs before it can succeed, and whether the organization is committed to providing that before the starting gun fires.