Skip to content

New Service Tier

Standing service structure — instantiates Response Repertoire Expansion

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.

A New Service Tier is a new standing level — a premium desk, an escalation unit, a step-down ward, an express lane — created because a class of cases needs a level of response the current tiers simply are not built to give. Its distinctive move is to organize a response into a durable, resourced structure with its own staffing and scope, rather than to author a procedure or train a person. It is the institutional mechanism of the archetype: the response becomes a place cases can be sent, with the authority and time to actually resolve them.

Example

A bank finds that complex account-takeover cases overwhelm frontline phone agents — they lack the authority and the time, so cases bounce between departments and customers churn. The bank stands up a dedicated fraud-response desk: a small team with elevated authority to freeze and reverse, longer handle times, and specialist training. Before launch, a readiness check confirms staffing, system access, and authority are actually in place; a risk review sets the limits on the desk's powers and the audit trail its actions leave; and after launch, adoption monitoring watches whether frontline agents actually route the right cases there and whether the desk is over- or under-loaded. A case class that used to have no adequate home now has a resourced pathway built for it.

How it works

The mechanism is capacity structured as a new level, not more of the same queue. It defines the tier's scope and authority, resources it, then monitors uptake and load so the tier is neither starved nor turned into a dumping ground. The response is embodied in an organizational unit — which is what makes it the most durable and the most expensive form of repertoire expansion.

Tuning parameters

  • Scope width — how broad a case class the tier owns. Wider scope justifies the fixed cost but blurs the tier's purpose; narrower is crisp but risks under-utilization.
  • Authority and resource level — how much power and staffing the tier gets. More lets it truly resolve hard cases; too little makes it just another bounce point.
  • Entry criteria strictness — how selectively cases are admitted. Loose entry floods the tier; tight entry strands cases that just miss the bar.
  • Standing vs. surge — a permanent tier versus one spun up only under load.

When it helps, and when it misleads

Its strength is giving a genuinely under-served case class a home with the authority and time to resolve it, and making that capacity schedulable and accountable. Its failure modes follow from its cost: a tier is expensive fixed structure, so an under-used one is pure overhead, and a badly-scoped one becomes the queue where hard cases go to die. Worse, adding a tier can merely relabel the same overloaded queue while adding no real new response. The classic misuse is announcing a new tier for optics without the authority or staffing that would let it do anything different. The discipline is to resource it to a real new capability, gate entry deliberately, and monitor adoption and load so it is right-sized — or retired.

How it implements the components

  • resource_readiness_check — confirms the tier's staffing, access, and authority are genuinely in place before it opens.
  • risk_review — bounds the tier's elevated powers and sets the controls and audit trail they operate under.
  • adoption_monitoring — watches whether cases are actually routed to the tier and whether it is over- or under-loaded.

It does not classify and route incoming cases into the tier — that is Triage Protocol Update — and it does not author the procedures the tier runs; those are Exception Handling Playbook and the runbooks.

Notes

A tier is the most expensive form of repertoire expansion. When the real gap is "no procedure" or "no trained person," a playbook or a cross-training program solves it far more cheaply than a standing org unit. Reaching for a new tier first — before the cheaper mechanisms are ruled out — is a common and costly reflex.