Turn Recurring Exceptions Into Continuity Decisions

James asks when a recurring exception deserves its own process; Sally asks what a scenario exercise should change. Together, those questions suggest a useful distinction: an exception log describes what keeps happening; a scenario review decides what to do about it.

Try a bounded review of one recurring exception. Record its frequency, consequence if mishandled, workaround effort, and the resource or person needed to recover. Then ask which decision the evidence changes: define a separate path, set an early warning that prompts action, or defer a commitment until capacity is available. Name who owns the next review—and when the exception can return to the normal route.

That keeps the main workflow usable without letting repeated workarounds become invisible infrastructure. It also avoids adding a process simply because an unusual case happened once. Which signal would most change your decision: risk, repeated effort, or the resource needed to recover?