Escalation Review¶
Procedure — instantiates Task Interdependence Mapping
A defined procedure for moving a dependency conflict that cannot be solved at the local task level up to the authority and information that can resolve it, before local blockage becomes system failure.
An Escalation Review is the exception procedure of the archetype: the pre-defined path a blocked dependency takes when the people at the coupling cannot resolve it themselves. Its defining move is vertical routing under a trigger — it does not run on a calendar or a shared picture; it fires when a specific condition is met (a dependency blocked past a threshold, a conflict two teams cannot settle, a risk score crossing a line) and moves the problem, with the authority to decide, to the level that can act. What makes it THIS mechanism and not a standing meeting is that it is invoked by exception, not by rhythm: most dependencies never touch it, and the ones that do get a fast, bounded review that ends in a decision — reallocate, re-sequence, accept the slip, or override — rather than another conversation.
Example¶
An automotive plant runs a just-in-time line, and a tier-2 supplier of wiring harnesses has just told the logistics coordinator that a shipment will miss by four days — long enough to idle the assembly line, which costs far more than the part. The line-side team has already exhausted its local options: no buffer stock, no alternate supplier qualified. This is exactly the condition the Escalation Review procedure exists for. The blocked dependency's risk score — line-stopping, no slack, single-source — trips the escalation threshold, and the coordinator invokes the path: within two hours the review convenes the plant manager, purchasing, and the supplier-quality lead, the three roles with the authority to spend money and bend the plan.
The review is short and decisive: purchasing authorizes premium air freight for the critical subset of harnesses, engineering approves building the affected cars short and completing them off-line, and the supplier-quality lead opens a second-source qualification so this coupling stops being a single point of failure. None of those moves were available to the line-side team; the procedure's job was to get the problem, fast, to the people for whom they were. The line keeps running, and the decision trail is logged so the recurring weakness is fixed, not just survived.
How it works¶
The procedure is a triggered routing rule, not a forum:
- Define the trigger. State the conditions that fire an escalation — blocked past a time threshold, an unresolvable cross-team conflict, or a dependency risk score above a set line — so escalation is a rule, not a judgment call made under pressure.
- Route by tier. Specify who receives the escalation at each level and what authority they hold, so the problem lands at the lowest level that can actually decide, not automatically at the top.
- Name the owner who carries it. Each escalated dependency has a contact responsible for raising it and shepherding it to resolution, so nothing stalls in the gap between "someone should escalate" and no one doing so.
- Close with a decision and a record. The review ends in an explicit call — reallocate, re-sequence, accept, or override — logged so recurring escalations expose a design flaw to fix rather than a fire to keep re-fighting.
Its ancestor on a factory floor is the andon cord: any worker can pull it to stop the line and pull the problem, immediately, to the team leader.[n1]
Tuning parameters¶
- Trigger threshold — how blocked, how risky, or how long-stalled before escalation fires. A low threshold catches problems early but floods the upper tiers; a high one risks escalating only after damage is done.
- Tier depth — how many levels the path passes through and how much authority sits at each. Shallow paths decide fast but can over-escalate; deep ones protect senior attention but slow resolution.
- Response time-box — the clock the review must beat once invoked. A tight SLA keeps escalation credible; a loose one lets urgent blockers rot in a queue.
- Risk-score gating — how heavily the dependency's risk score weights the trigger versus raw elapsed block-time. Score-gating focuses escalation on couplings whose failure matters, not merely on whatever is loudest.
When it helps, and when it misleads¶
Its strength is that it keeps a local blockage from becoming a system failure: a stuck dependency reaches the authority and information to unstick it before the cost compounds, and the logged decisions turn repeat escalations into a to-do list for redesign. It is the safety valve that lets the rest of the coordination machinery run lightweight.
Its failure mode is the archetype's ownership-without-authority trap: naming an escalation owner who has a route but no real influence, so the path exists on paper and dead-ends in practice. A classic misuse is an escalation channel that becomes a blame conduit — problems are "escalated" to assign fault rather than to decide — which teaches everyone downstream to hide blockers instead of surfacing them. The guarding discipline is to make sure every tier on the path holds genuine decision authority and to treat escalation as structural evidence (this coupling keeps breaking) rather than personal failing (someone keeps dropping it).
How it implements the components¶
escalation_path— it is the defined route: the tiers, triggers, and authorities that move an unresolved dependency conflict to the level that can settle it.dependency_owner_or_contact_path— it names the contact responsible for raising each escalated dependency and carrying it to a decision, closing the "someone should have escalated" gap.dependency_risk_score— it uses each dependency's risk score to gate the trigger, so escalation fires for couplings whose failure would matter rather than for whatever is merely noisy.
It does not run the standing rhythm the routine couplings live on (communication_cadence) — that is Coordination Meeting Cadence; and it does not continuously monitor and display dependency state (dependency_health_signal) — that is Shared Workflow Board, whose signal is often what trips this procedure's trigger.
Related¶
- Instantiates: Task Interdependence Mapping — this procedure is the archetype's exception path, catching the couplings the routine mechanisms cannot resolve.
- Consumes: Shared Workflow Board — supplies the blocked-time and health signal whose breach trips the escalation trigger.
- Sibling mechanisms: Coordination Meeting Cadence · Shared Workflow Board · Critical Path Analysis · Dependency Mapping Session · Cross-Functional Workflow Mapping · Workflow Diagram
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Escalation Review operates as a repeatable ordered procedure or handoff sequence that coordinates action because it a defined procedure for moving a dependency conflict that cannot be solved at the local task level up to the authority and information that can resolve it, before local blockage becomes system failure.
Independent corroboration: The frozen evidence defines Escalation Review as 'A defined procedure for moving a dependency conflict that cannot be solved at the local task level up to the authority and information that can resolve it, before local blockage becomes system failure', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Cross-team dependency management cohered exception review that routes unresolved coupling conflicts to an authority able to reallocate, resequence, or override.
Related originating lineages:
- Operations Research — Scheduling and resource-allocation analysis supplies the dependency and bottleneck decisions made at the review.
Review resolution: The current reviewers agree that organizational_management is primary. For the reported differences (alternate_origin_disagreement, origin_mode_disagreement, encyclopedia_synthesis_disagreement), the evidence supports single_lineage, multi_domain, and operations_research; these choices preserve materially formative origins without conflating later domain reach.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The andon cord in the Toyota Production System is a line-stop-and-signal device: any worker who spots a problem pulls it, which halts the line and immediately summons the team leader. It is the archetypal escalation trigger — a low-threshold, authority-summoning path that treats a stuck dependency as a system event to resolve at once, not a local nuisance to work around. ↩