Skip to content

Response Repertoire Expansion

Add new response options when existing responses cannot handle recurring conditions or disturbances.

The Diagnostic Story

Symptom: The same class of situation keeps arriving and the system has no authorized way to handle it. Frontline actors improvise private workarounds or escalate cases that shouldn't need escalation because the official repertoire simply doesn't cover what they face. Reviews and postmortems keep noting 'we had no playbook for this,' but the pattern is predictable enough that calling it an edge case has stopped being defensible.

Pivot: Identify recurring response gaps — the case classes that consistently exceed available options — then design viable response options for them, enable those options with resources and authority, define when each is activated, and maintain or retire them based on performance feedback.

Resolution: Recurring unhandled cases receive viable responses instead of improvisation or refusal. Avoidable escalations decrease because actors gain appropriate response options rather than needing to push cases upward. Each repeated gap now produces a designed option rather than just a lesson learned, and the boundary between routine handling and genuine escalation becomes clearer.

Reach for this when you hear…

[customer support operations] “We escalate about forty tickets a week for the same partial-refund scenario because nobody ever gave us an authorized response for it — it's not an edge case anymore.”

[emergency medicine] “The protocol covered the common presentations, but when patients arrived with the atypical variant the nurses had to improvise every time because there was no recognized pathway.”

[incident response] “We had a runbook for the database going down and one for the network dropping, but the scenario where both happened at once left the team arguing about which playbook applied.”

Mechanisms / Implementations

  • After-Action Repertoire Review: A blame-free retrospective that asks, after each handled or mishandled event, whether the system had the right response available — turning recurring gaps into candidate new options and judging whether past additions actually worked.
  • Competency Matrix Update: Maintains the standing record of which people can perform which responses, and to what proven level, so coverage gaps are visible before an event exposes them.
  • Controlled Pilot: Exposes a newly-added response to a bounded slice of real conditions before wide reliance, so its readiness, risks, and actual effectiveness are proven on small stakes.
  • Cross-Training Program: Builds a second set of people who can perform an existing response, so the option survives the absence, overload, or departure of the one person who used to hold it.
  • Decision Tree Update: Encodes, as an explicit branch structure, which response a case should select from its features — including the branch that says 'none of these fits, escalate.'
  • Exception Handling Playbook: Turns a recurring class of exceptions into named, written procedures, so staff select a known response instead of improvising each disturbance from scratch.
  • Job Aid Checklist: A stripped-down, point-of-use card for a single response, so it can be performed correctly under pressure by whoever is present — not only by the expert who knows it cold.
  • New Service Tier: Stands up a new, resourced service level or pathway to handle a class of cases the existing tiers structurally cannot, organizing a response into a standing offering rather than a one-off.
  • Runbook Library Update: Keeps the growing collection of operational runbooks healthy — each one owned, current, findable, and retired or merged when stale — so the repertoire doesn't rot into a graveyard of half-true procedures.
  • Scenario Drill: Rehearses a response under simulated conditions before it's needed, so people can actually execute it under pressure — and so the gaps show up in practice instead of during the real event.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 10 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Exception Response Expansion · subtype · recognized

Add response options for recurring exceptions that existing ordinary procedures cannot handle.

Skill Repertoire Expansion · implementation variant · recognized

Add or distribute skills so recurring disturbance classes can be handled without fragile specialist bottlenecks.

Tool Repertoire Expansion · mechanism family variant · recognized

Add tools, interfaces, templates, or technical capabilities that make a previously unavailable response executable.

Service Tier Addition · scale variant · recognized

Add a new tier of response intensity or specialization for cases that ordinary service and escalation do not fit.

Authority Response Expansion · governance variant · recognized

Add a response option by granting authority to act in cases that previously required delay, escalation, or unofficial workaround.