Recovery, uncertainty, and handoff

A spare umbrella helps only if it is where you are when rain begins. Buying another one at home does little if you are already at the station. Recovery plans have the same timing problem. An extra supply order may be useful, late, or blocked by the next stage. A good plan names the event that makes the option useful and keeps uncertain arrivals separate from confirmed stock.

Return to the common Northstar requirement of twenty nine good bottles. Supplier, manufacturing, and shipping ceilings are twenty four, thirty two, and thirty. Buying five additional on-time supplier equivalents for ten currency units each closes the nominal gap and costs fifty. Buying eight equivalents costs eighty but permits only thirty shipments because shipping becomes limiting. Against the twenty nine requirement, the extra three units beyond the needed five do not improve current due service. They might have later value, but that is a separate decision.

Now consider a downside case in which shipping falls to twenty seven. With the five-unit supplier recovery, completed flow is min(29,32,27), or twenty seven, leaving two late. A backup carrier can add three shipping slots for a fixed fee of eighteen, restoring the needed flow to twenty nine. An action should be checked against all downstream gates and should be charged according to its actual cost rule. Fixed fees differ from per-unit costs. Do not multiply a fixed pickup fee by the number of bottles.

Without probabilities, compare scenarios without claiming an expected cost. If a decision maker supplies explicit probabilities, a weighted result can be calculated, but that does not guarantee a particular outcome. For teaching, use a sixty percent nominal case and forty percent shipping-downside case, and treat these probabilities as assumptions. Supplier recovery alone yields weighted shortfall of point eight bottle, although actual shortfall is either zero or two. Paying for contingent backup only in the downside has expected added fee seven point two, assuming activation is reliably available.

A relay runner cannot help by shouting that the team is fast enough. The next runner needs a clear handover point and must know when to start. Planning has its own handover. Procurement, production, inspection, and transport need the same approved quantity and time, plus a rule for what to do when an assumption fails. A detailed table without that agreement can still create conflicting actions on the day.

A decision record should separate known facts, assumptions, choices, and triggers. For Northstar the requirement is twenty nine good bottles. The current supplier ceiling is twenty four. A proposed five-unit recovery is not confirmed until procurement verifies availability and arrival before the production release gate. Manufacturing has a ceiling of thirty two and transport thirty in this simplified good-unit model. Record the version and time of each confirmation. A later change in a hard constraint should reopen the decision rather than silently replace a cell.

Use concrete checkpoints. Procurement must confirm the five extra equivalents by Monday at ten. If confirmation fails, the planner reduces the firm new-flow promise to twenty four and records five unfilled units. If confirmation succeeds but the carrier later confirms only twenty seven slots, transport activates a pre-reserved three-slot backup by Tuesday noon. These actions are fictional operating rules for this case. They require named roles, stated deadlines, and authority; a vague instruction to expedite does not tell a colleague what to do.

The final handoff contains the quantities to start, quantities expected good, quantities approved to ship, and the checks that connect them. Do not mix the good-unit capacity example with a separate yield-based start calculation without translating the units. In a physical run with a ninety seven percent expected yield, thirty starts support an expectation of twenty nine point one good bottles, not a firm guarantee of twenty nine. Inspection should release actual good stock, and customer service should update the promise if the released amount misses the committed quantity.

In your lab, write a release note for each path through the case. Name the quantity, the owner, the next gate, and the proof still needed. Keep the old version so the team can see why the promise changed. A late message is new evidence, not a reason to hide a missed gate. Close the review by asking whether each planned action is still available at the time it must be used.

1. Define the case

   Original card shows the two lesson titles, fictional business, and planning goal.

   • Northstar case
   • Explicit scope
   • Check the units
2. Read the inputs

   Original table highlights the first lesson’s supplied quantities with unit and timing labels.

   • Given quantities
   • Usable dates
   • Stated limits
3. Trace the first check

   Original arithmetic flow follows the first lesson’s worked calculation to its checked answer.

   • Calculate load
   • Find the gap
   • State the result
4. Add the second view

   Original paired cards show how the second lesson adds a new constraint or decision policy.

   • New condition
   • Same discipline
   • No hidden assumptions
5. Compare scenarios

   Original three-column table uses the lesson lab baseline, stress case, and response.

   • Baseline
   • Stress case
   • Feasible response
6. Release the decision

   Original decision card links result, uncertainty, owner, and next verification gate.

   • Explain tradeoffs
   • Name the owner
   • Verify before release