STRATEGYMonths to result

Seven Steps for Breaking Through Organizational Gridlock

Map linked quick-fix loops to escape cross-functional paralysis

Problem it solves

loops to escape cross-functional paralysis

Best for

Cross-functional teams stuck in recurring turf wars, organizations where delayering has increased interdependence but walls persist, and leaders watching teams optimize locally at the expense of the whole.

Not ideal for

Problems genuinely within a single function, or situations where gridlock is caused by a single individual rather than structural dynamics.

Overview

Why this framework exists

The Seven Steps framework provides a structured method for diagnosing and resolving organizational gridlock using the Shifting the Burden systems archetype. Gridlock occurs when individual actors continue behaving as if they were independent of everyone else, each pulling in different directions, even though organizational delayering has made them more interdependent.

The framework maps interlocking quick-fix loops that keep teams locked into patterned responses. In a typical gridlock situation, each team applies solutions that seem reasonable from their own perspective but create problems for other teams, who respond with their own quick fixes. This creates linked Shifting the Burden structures feeding each other in a vicious spiral.

The breakthrough comes from getting a bird's-eye view of the entire system. When teams see how their individual solutions collectively create the gridlock, finger-pointing stops and genuine cross-functional collaboration becomes possible.

Core principles

4 total
  1. Organizational gridlock is caused by interlocking structural dynamics where each team's rational solution creates problems for others.
  2. The persistence of gridlock signals reinforcing processes locking players into patterned responses, not that people are unreasonable.
  3. The process of mapping gridlock is itself a high-leverage action because it stops finger-pointing and creates a shared view.
  4. Fundamental solutions to gridlock almost always involve improving cross-team communication quality and frequency.

Steps

7 steps
  1. Identify the Original Problem Symptom
    Look back over time and identify recurring symptom classes: missed specifications, wrong part numbers, incompatible outputs, coordination failures. Group symptoms under a general heading that captures the pattern.
    Pro tipRecurrence is the hallmark of a structural problem. Focus on symptoms that keep returning despite being addressed.
  2. Map All Quick Fixes
    Map all fixes used to tackle the problem. Identify balancing loops that appear to keep problems under control. Each quick fix represents symptom management without addressing underlying causes.
    Pro tipInclude fixes from all involved teams, not just your own.
  3. Identify Undesirable Impacts on Others
    Trace how each team's fix creates problems for other teams. Actions by one group almost always affect others. The persistence of gridlock suggests a reinforcing process locking players into patterned responses.
    Pro tipAsk each team what problems other teams create for them, then cross-reference.
    WarningThis step can generate defensive reactions. Frame it as mapping system dynamics, not assigning blame.
  4. Identify the Fundamental Solution
    Find a solution that fundamentally addresses the problems by looking at the situation from everyone's perspective simultaneously. The fundamental solution typically involves improving cross-team communication and collaboration.
    Pro tipThe fundamental solution is almost always something everyone knows is needed but nobody has implemented.
  5. Map Addictive Side Effects of Quick Fixes
    In Shifting the Burden structures, quick-fix side effects steadily undermine the fundamental solution. Each round of fixes may increase focus on own targets while decreasing cross-team investment, creating dependency spirals.
    Pro tipLook for how each cycle increases resentment. Resentment is the emotional fuel of gridlock addiction.
  6. Find Interconnections Between Addiction Loops
    Find links between interaction effects and the fundamental solution. Two linked Shifting the Burden structures create spiraling resentment and increasing unwillingness to communicate. The us-versus-them mentality becomes another addictive force.
    Pro tipDraw the full diagram on a large whiteboard with all teams present. The visual impact often produces an immediate perspective shift.
  7. Identify High-Leverage Actions
    With the bird's-eye view, identify points where small interventions produce disproportionate effects. The mapping process itself is often the highest-leverage action because shared understanding changes the dynamic even before formal intervention.
    Pro tipThe highest leverage often lies in making the gridlock structure visible to all parties simultaneously.

Checklist

Saved in your browser

Examples

2 cases
NVH and Chassis Teams

In an automobile program, the NVH team fixed noise by adding chassis reinforcements (adding weight). Chassis compensated by increasing tire pressure (worsening harshness), creating new NVH problems. Each round increased focus on own targets and decreased cross-team communication.

OutcomeMapping all seven steps on a shared diagram stopped the blame game and created conditions for the fundamental solution: improved cross-team communication.
Delayering Paradox

Organizations removing hierarchy in the 1990s found gridlock actually increased. Removing coordination layers made functions more interdependent without providing alternative coordination tools.

OutcomeThe Seven Steps revealed that delayering without building cross-functional communication created linked Shifting the Burden structures.

Common mistakes

3 traps
Mapping Only Your Own Perspective
If you map only your team's fixes, you will see others as the problem rather than seeing the structural dynamic that traps all parties.
Treating Gridlock as a People Problem
Replacing individuals does not resolve gridlock because the structural dynamics remain. The same positions will produce the same patterns regardless of who occupies them.
Implementing Fundamental Solutions Without Addressing Addiction
Even when identified, the addictive dynamics of quick fixes may be too strong. Teams may need to gradually wean off quick fixes while building fundamental solution capacity.

Origin story

How this framework came to be

Daniel Kim of Pegasus Communications and MIT developed the Seven Steps as a practical application of systems archetypes to organizational gridlock. First published in The Systems Thinker newsletter in February 1993, the framework addressed the paradox that delayering, intended to make organizations more agile, often increased gridlock by making functions more interdependent without providing coordination tools.

Kim observed that removing hierarchy without building cross-functional communication capabilities created linked Shifting the Burden structures where each function's independent optimization undermined the others.

Source

Traced to primary
Source · BOOK
The Fifth Discipline Fieldbook
Peter Senge · 1994
Open source →

Related frameworks

Browse all Strategy →