Front Rescope Playbook¶

Contingency playbook (protocol) — instantiates Sustainment-Reach Alignment

A pre-decided repertoire of ways to shrink an overextended front — pull back, narrow, hand off, or make it self-sustaining — chosen before the line breaks, not during the panic.

When net support falls below what the current reach demands, the front has to get smaller — but how it gets smaller is a decision most organizations make badly, late, and under duress. Front Rescope Playbook is the pre-authored menu of reduction moves and the rules for choosing among them: pull the front back to a shorter, defensible line; narrow it by dropping the least-supportable segments; hand a segment to a partner; or cut the tail loose by chartering the forward element to run autonomously on local means. Its distinguishing contribution is that it treats giving ground as a designed act with options, decided while there is still slack, rather than as an improvised admission of failure after the line has already snapped. The playbook exists precisely because retraction is the move an overextended front is least willing to make voluntarily.

Example¶

A B2B software company has, over two years, expanded to 14 country-markets and 30 third-party integrations. Now the seams show: localization lags, compliance filings slip, on-call engineers can't hold the support SLA across so many surfaces, and every new incident robs attention from the core. Net delivered support has fallen below the footprint. Instead of firefighting market by market, the team runs its rescope playbook, whose plays and triggers are pre-defined: sunset the five lowest-usage locales (below an agreed active-account floor); consolidate the integration surface to a supported tier and deprecate the long tail; hand off two strategic-but-costly markets to a regional reseller under a support agreement; and charter the strongest regional team to operate semi-autonomously with its own on-call and localized roadmap. Leadership selects the "narrow-and-consolidate" combination, executes to a defensible footprint of core markets, and — crucially — communicates it as a planned contraction with clear criteria, not a retreat. The remaining footprint now sits back inside what support can actually sustain.

How it works¶

Reduction plays are pre-written. Retract, narrow, hand off, and charter-autonomous each have defined preconditions, sequencing, and reversibility, so choosing one is selection, not invention.
Triggers are agreed in advance. Each play names the signal that arms it (a support-margin breach, a service-floor violation), so the decision to shrink isn't hostage to sunk-cost pride.
It ends on a defensible line. The target of any play is a footprint whose support requirement sits back inside net delivered support — with margin — not merely "less than before."

Tuning parameters¶

Play selection — retract vs. narrow vs. hand off vs. charter; each trades differently among cost saved, capability kept, and reversibility.
Trigger threshold — how deep the support shortfall must be before a play arms; tight triggers rescope early and cheaply but risk over-reacting to noise.
Depth of pull-back — how far to shorten; a deeper cut buys more margin but forfeits more of the advance and is harder to reverse.
Reversibility — whether a rescope is designed to be re-expanded later (a temporary contraction) or is a permanent exit; this shapes how you dismantle.
Handoff terms — for hand-off and charter plays, how much authority and support transfers with the segment.

When it helps, and when it misleads¶

Its strength is that it makes the hardest move — voluntary contraction — available, fast, and dignified, by deciding the options before the crisis and attaching them to triggers rather than to willpower. Shortening the line to a length the support can hold is a classic recovery: a shorter front is denser, cheaper to sustain, and more defensible than an overextended one.^[1] The playbook is also what lets a team pull back without the paralysis of treating retreat as defeat.

Its failure mode is using it too readily or too timidly. Rescope every time a signal blips and you thrash, never consolidating anything; wait until collapse and the "playbook" is just a post-mortem. The classic misuse is running it backwards — reaching for the reversible "temporary narrowing" play to avoid admitting a permanent overreach, so the front never actually gets small enough to sustain and the shortfall recurs. The discipline is honest triggers and a target defined as a sustainable footprint, checked against the support model rather than against how much anyone wants to keep.

How it implements the components¶

Front Rescope Playbook fills the archetype's reduce-the-front components — the rules and authorities for making reach smaller:

retraction_or_rescope_rule — it is that rule set: the pre-defined plays (retract, narrow, hand off) and the triggers that arm them.
front_autonomy_charter — the charter-autonomous play, cutting a forward element loose to sustain itself on local means, is both one of its reduction options and the authority document that enacts it.

It does not detect the live shortfall that triggers a rescope (line_health_monitor — Net-Supply Ratio Dashboard), compute where the sustainable line lies (net_delivery_metric, reach_cost_model — Line-of-Support Capacity Model), or ration scarce support across a held front (support_priority_policy — Priority Supply Ladder); it acts on the front's extent once those say it must shrink.

Instantiates: Sustainment-Reach Alignment — the repertoire for pulling reach back inside sustainable support.
Consumes: Line-of-Support Capacity Model and Net-Supply Ratio Dashboard to know when the front must shrink and to what line.
Sibling mechanisms: Advance Pause and Consolidation Window · Reach-Limit Gate · Priority Supply Ladder · Line-of-Support Capacity Model · Local Sourcing or Repair Protocol · Forward Staging Cache · Lead-Time Stress Simulation · Net-Supply Ratio Dashboard · Relay-Hub Network · Support Burn-Rate Review · Support-Line Postmortem

Notes¶

Rescoping is the last resort on the archetype's ladder — cheaper responses (pause, buffer, localize, reprioritize) come first, and a rescope is warranted when they cannot bring reach and support back into line. Its close cousin is Advance Pause and Consolidation Window: a pause holds ground expecting to resume; a rescope concedes ground because the reach itself was wrong. Naming which one you are doing is half the decision.

References¶

[1] "Shortening the line" is a standard defensive manoeuvre — voluntarily withdrawing from an overextended frontage to a shorter, more concentrated line the available force can actually hold. The reduction in frontage, not any gain of ground, is the point. ↩