Escalation as Resolution

Chapter 18

Escalation is a narrowing function.

That is its design. A decision elevated to higher authority should enter a smaller circle, where scope is clarified, trade-offs are accepted, and ownership concentrates. The decision binds. Ambiguity terminates.

In most organisations, the opposite occurs.

This is not a failure of nerve. It is a failure of architecture.

For escalation to resolve rather than circulate, three properties must exist.

Scope must compress. The elevated authority addresses a defined trade-off, not the entire problem space. The question arriving at altitude should be smaller than the one that left the ground.

Ownership must intensify. The number of accountable parties must decrease, not increase. Authority concentrates as a decision rises. Exposure does not distribute.

A terminal condition must exist. There must be a defined point at which the decision binds and does not re-enter circulation unless explicit revisitation criteria are met.

Remove any of these properties and escalation cannot converge. It can only move.

Without scope compression, escalation becomes re-litigation. The decision arrives at a higher level carrying its original ambiguity plus whatever framing was added in transit. Authority inherits expansion, not clarity.

Without ownership intensification, escalation distributes exposure rather than concentrating it. Additional stakeholders are included to ensure representation. Risk is restated in broader terms. The coalition grows. Accountability thins.

Without a terminal condition, escalation has no endpoint. A decision that binds at one level can be re-elevated at another. Revisitation is implied rather than governed. The decision does not stop when it reaches authority. It continues until someone absorbs sufficient cost to hold it, or until time resolves it by default.

These absences share a single effect. Escalation transforms from convergence mechanism into circulation mechanism.

The decision moves upward. Visibility increases. Symbolic weight accumulates. The cost of being wrong rises. At each level, the safest move becomes deferral — masked as further analysis, broader consultation, or pending information.

Each step is individually justified. Given the impact, we should involve. This crosses domains; it requires alignment. Before committing, we need more data.

The language is reasonable.

The cumulative effect is latency.

Over time, the structure shapes behaviour. Engineers stop resolving ambiguity locally because local resolution will be escalated regardless. Middle management avoids binding decisions because escalation provides insulation without concentrated accountability. Senior leaders receive questions that feel operational but are structurally unresolvable — because the pathway that delivered them was never designed to terminate.

The organisation appears highly governed.

It is structurally indecisive.

These are not in tension. One produces the other.

Escalation, properly designed, accelerates convergence. It shortens decision windows, concentrates authority, and closes ambiguity at altitude. Improperly designed — which is to say, designed without termination — it extends latency, diffuses consequence, and expands participation until the decision belongs to no level in particular.

The difference is not cultural. It is not a question of intent.

It is whether the escalation pathway enforces closure.

Motion is not resolution.

Visibility is not convergence.

Without termination, escalation becomes organised avoidance with institutional legitimacy.