Purpose: Manage assumptions that could not be tested pre-launch. Every load-bearing residual must have a named owner, an observable signpost, a trigger threshold, and a hedging action. Load-bearing residuals without named owners are program launch risks that must be escalated.
ABP Classification:Load-bearing — program needs major redesign if false; active monitoring + named owner required. Vulnerable — plausible to fail; response plan needed; passive monitoring acceptable. Background — unlikely to fail or low impact; document only.
Residual Assumption Monitor Updated after each monitoring cycle
Assump. #
Assumption (short)
ABP Class
Owner
Observable Signpost — specific data point that signals this is failing
Trigger Threshold
Monitoring Frequency
Hedging Action — what happens if assumption fails
Monitoring Log Updated at each monitoring cycle; one entry per cycle per assumption