Volume Doubled. Someone Quit. SOP Broke.: Three operational triggers, each with a structured response to run in the first forty-eight hours.

The book is the third companion to Operational Efficiency Frameworks (Operator Playbooks 06). It does not build on the weekly or quarterly instruments. It runs in parallel to them, available when a specific event fires.

A six-question diagnostic intake identifies which trigger has fired and routes directly to the relevant framework.

What this companion does NOT replace: the spot-check, process-time tracker, and throughput gauge in Where the Queue Forms (op-06 weekly rhythm), or the value-stream remap, OEE deep-dive, and process-cost reconstruction in The Map Has Drifted (op-06 quarterly review). Those cover ongoing rhythm and structural recalibration. This covers the three scenarios they cannot reach.

Volume Doubles Overnight Response. Run when order volume spikes 100 percent or more without warning. The framework computes the maximum sustainable throughput against the spike duration and produces a structured commit-or-reject decision before any customer commitment is made. Two worked examples: a Central Java food distributor handling a high-volume commodity surge with uniform SKU composition, and a Yogyakarta batik export workshop facing a low-volume high-mix surge from a single Korean buyer where the throughput ceiling is not volume but setup-change capacity.

Key Operator Quits Without Warning. Run within ninety minutes of receiving the resignation. The framework maps the knowledge held by the departing operator, schedules a day-one knowledge session, and produces a cross-coverage plan before the notice period ends. Two worked examples: a delivery company dispatcher whose coordination knowledge is distributed across informal routing decisions, and a Bandung garment accessories manufacturer whose machine setup operator holds technical process knowledge that has never been documented.

SOP Errors Up Diagnosis. Run when a new standard operating procedure has been rolled out and error rates have climbed. A 48-hour structured observation window precedes the root-cause analysis. Two worked examples: a B2B distribution order confirmation SOP where errors cluster at a single step, and a Surabaya cold-chain pharmaceutical and food logistics provider where a temperature-controlled physical inspection SOP introduces unintended delays that the rollout team did not model.

Each framework carries a self-scoring rubric, a quick decision tree, and tier adaptations. The response plan at the back sequences all three across the first 48 hours, the first week, and the first month after a trigger fires.

Written from the seat of an Indonesian operator. The context is specific; the trigger patterns are not.

Who This Is For

Operators facing one of these three triggers right now.

Owners with concentrated knowledge in one or two key operators.

Mid-tier directors who want documented pre-decision procedures before the next unplanned event.

Topics and Keywords

operational crisis response, volume spike management, key operator departure, SOP rollout failure, scenario-triggered operations, capacity decisions, SME operations under pressure