Why Strategy Is Choreography: What Plane Boarding Teaches Us About Corporate Deals and Integration

What if the reason deals fail is not that companies picked the wrong partner, but that they chose the wrong order of operations?

We intuitively solve messy problems by piling resources into them: buy the underperformer, merge systems, roll out a single brand, then hope the parts learn to behave. That approach is the equivalent of boarding a full airplane by calling rows from back to front while everyone jostles in the aisle. It feels orderly, but it is slow, costly, and guaranteed to produce frustration.

This piece makes a simple claim: strategy is choreography, not brute force. The sequences leaders choose when they integrate, divest, or reorganize determine outcomes as much as, or more than, the assets they move. By treating integration like a boarding problem, leaders can reduce friction, reveal hidden constraints early, and turn messy consolidations into high-velocity value creation.

The hidden cost of naive sequencing

When a company buys a struggling business, what do leaders usually do? They announce the deal, set an integration timetable, combine teams, and begin the technical work of merging systems. That is the natural order. It is also often the wrong one.

The most common failure modes are familiar: customer churn spikes, operational costs rise, the merged entity fails to capture promised synergies, and leadership discovers late-stage incompatibilities that were visible only after the systems were merged. These problems are not always about valuation or due diligence. They often trace back to sequencing: the order in which people, processes, and systems are combined.

An everyday analog helps. Most airlines still board passengers by rows or priorities that make sense at first glance. It looks fair and orderly. But experiments and simulations show that this approach is one of the slowest possible. The reason is simple: customers block one another in the aisle while stowing luggage, turning the boarding process into a cascading queue. Better approaches exist that dramatically reduce total boarding time by sequencing boarding so that interference is minimized.

Translating that insight to business: the wrong sequence creates interference. Teams wait on one another. Systems block others. Customers experience cascading interruptions. The result is lost time, higher costs, and damaged trust. The solution is to map dependencies and choreograph the sequence so that blocking is avoided and work can proceed in parallel where possible.

The choreography principle: three core patterns

From the boarding problem we can extract three principles that apply to integration and corporate redesign. These are not metaphorical. They are prescriptive rules for sequencing complex, interdependent changes.

1. Reduce interference by sequencing high-friction moves first.

If window seat passengers board after people seated in the aisle have already stowed bags, the aisle becomes a bottleneck. In integration terms, high-friction items are those that will block others if postponed: critical contracts, differential regulatory approvals, key data migrations, or centralized services that all lines of business rely on. Prioritize these items early so they do not become aisle-blockers later.

2. Parallelize where interactions are minimal.

Boarding models that reduce total time do so by permitting multiple passengers to stow luggage simultaneously without crossing paths. In business integration, that means identifying components that can be absorbed in parallel because they do not share dependencies. For example, a back-office finance function in one geography might be integrated with minimal coordination to a similar function elsewhere, while customer-facing systems require sequential care.

3. Choreograph the sequence down to the seat level.

The most efficient boarding methods are not just “outside in” or “back to front.” They specify an order of entry designed to prevent any one passenger from waiting for another. The equivalent in corporate change is to choreograph the small moves: which API is migrated first, which product SKU is delisted, which contracts are renewed and when. The more precise the choreography, the lower the friction.

These three patterns form the foundation of a new approach to integration: choreography as strategy.

A practical framework: the Sequencing Matrix

To operationalize choreography, use a simple two axis framework called the Sequencing Matrix. Plot each integration workstream on these axes:

• Dependency intensity: how many other workstreams or systems depend on this one. High dependency items will block many others.
• Friction cost: how costly, risky, or time consuming will this item be to change or move? High friction means complexity, regulatory risk, or customer sensitivity.

This yields four quadrants with distinct plays:

Quadrant 1: Low dependency, low friction. These items are your quick wins. Parallelize them early to build credibility and free resources.

Quadrant 2: High dependency, low friction. These are enablers that unlock others. Sequence them before they are needed, or carve out templates to reduce their dependency effects.

Quadrant 3: Low dependency, high friction. These look risky but do not block others. Treat them as isolated experiments with strong rollback, so they do not contaminate the main flow.

Quadrant 4: High dependency, high friction. These are the true aisle-blockers. They must be identified early, decomposed into smaller moves, and scheduled first or buffered so that their delays do not cascade.

Using this matrix forces leaders to stop prioritizing by intuition or politics, and instead sequence by systemic impact. It turns vague to-do lists into a choreography plan.

Three concrete patterns for choreographed integration

Leaders can use tactical patterns to implement this framework. Here are three reliable ones.

Pattern: Outside in sequencing for customer journeys

Start integration with elements closest to the customer that will reduce customer pain or prevent churn. This is the boarding equivalent of allowing window seats to board before middles and aisles so fewer people block the aisle when storing luggage. For businesses, the goal is to stabilize revenue and preserve trust. For example, migrate customer-facing platforms, billing, and care pathways in a way that minimizes visible disruption, even if it delays internal harmonization.

Pattern: Buffering and temporary interfaces

When two systems must integrate but one is fragile or high friction, build a buffer. In airplane terms, think of temporary overhead luggage storage areas that keep aisles free while passengers settle. In corporate integration, the buffer can be a lightweight API, an interim vendor, or a short-term funding vehicle that prevents work from blocking downstream tasks.

Pattern: Choreographed micro-migrations

Break large migrations into micro-migrations that have predictable, reversible outcomes. Instead of moving an entire customer base in one go, migrate cohorts by geography, product type, or contract vintage. Design each micro-migration as a mini experiment with clear metrics so the organization learns and adapts without stalling the whole program.

These patterns are tools for leaders who want to treat integration as low-friction choreography rather than a brute force push.

Why choreography wins where brute force fails

There are three structural reasons choreography outperforms traditional approaches.

First, it respects human and operational reality. People do not behave like modules that can be swapped without interaction. They push back, they react to uncertainty, and they create delays. Sequencing that anticipates these reactions reduces wasted cycles and morale damage.

Second, choreography leverages information. Early, small moves reveal the true shape of the problem. A micro-migration that encounters unexpected contract issues is valuable: it forces renegotiation, clarifies assumptions, and redirects the broader plan. Brute force tends to bury learning until the cost of correction is high.

Third, choreography reduces the cost of failure. By isolating high-risk moves and making them reversible, leaders limit downside and preserve optionality. A failed micro-migration is a lesson, not a catastrophe.

A short playbook for leaders who want to choreograph

Below are practical steps to apply these ideas to any M and A, divestiture, or large-scale integration.

1. Map dependencies visually. Draw the end state and work backward, identifying which systems, contracts, and people block others. Treat this map as the boarding chart.

2. Score each workstream by dependency intensity and friction cost. Place them in the Sequencing Matrix and choose a play for each quadrant.

3. Design micro-migrations with clear success criteria and rollback paths. Treat the early waves as experiments that must teach.

4. Create buffers for unavoidable friction. Temporary interfaces, parallel vendor runs, and short-term funding can prevent blocking.

5. Communicate the choreography, not the destination. Make every stakeholder understand the sequence, the reason for it, and their role in the flow. People tolerate change much better when they know whose turn comes next.

Choreography is not a bureaucratic plan. It is a social contract: a shared sequence that reduces surprise, interference, and wasted effort.

Key Takeaways

1. Map blocking dependencies first: identify the true aisle-blockers before you schedule broad integration work.

2. Prioritize high-dependency, high-friction items early or decompose them into reversible parts.

3. Parallelize low-dependency workstreams to build momentum and free capacity for difficult moves.

4. Use buffers and temporary interfaces to prevent fragile systems from halting the whole program.

5. Treat early waves as experiments with explicit metrics and rollback plans.

Closing: rethink where the work actually happens

Too often we confuse boldness with speed. Buying assets and then pushing them together quickly is bold; choreographing stepwise moves that reduce friction and accelerate learning is smart. The first produces messy integration, the second creates durable value.

Imagine your next deal as a flight that must be boarded without chaos. What changes if you stop asking how to cram everyone on fast, and instead ask how to get them seated without blocking the aisle? The answer will change your priorities, your governance, and perhaps the very way you measure success.

Strategy, in this view, becomes choreography. The best leaders are not those who move fastest, but those who sequence best.