The new approval route is written. Can someone use it?

The revised procedure now names an alternate approver. The sentence is clear, the role is spelled correctly, and the document looks finished. Then someone new takes the incident lead’s seat. Can they find that person and bring a decision the alternate is actually allowed to make?

That is the question in this fictional Dispatch rehearsal. A storage repair previously waited because the primary approver was unavailable and nobody knew a backup route. The proposed improvement adds an alternate and a limited procedure. Replaying that same moment tells us more than checking that the new paragraph exists.

What should the next lead be able to do?

The change is meant to let a replacement responder reach an authorized decision without inventing permission along the way. They should be able to find the alternate, supply the required evidence, obtain an explicit decision and record its limits.

That is a useful promise on its own. It does not promise a quicker storage repair, an end to outages or permission for everyone to make every change. Keeping the promise specific makes it possible to notice whether the edit helped.

The alternate needs more than a message saying “storage is broken”

Give participants fictional role cards: the storage duty owner is the primary approver, the storage incident delegate is the alternate, and the incident executive handles escalation. The facilitator plays those contacts and reports whether each is available.

For a proposed regional configuration repair, the responder needs a packet containing the affected region, observed timeout evidence, exact configuration difference, compatibility check, rollback plan and checks of new and queued exports after the change. An alternate who receives only “storage is broken, please approve” has to reconstruct all of that before deciding. A contact name removes one obstacle; a usable request removes another.

The exercise grants the approver authority over only that region and change. Destructive recovery or unknown data compatibility must be escalated. Contact the duty owner first, then the delegate with the same packet if the owner is unavailable. If neither is available, or the action exceeds their authority, escalate to the incident executive while keeping the last approved mitigation active. Record the decision and limits before simulated execution. These are fictional exercise rules, not permissions in a real organization.

Now let the participant use the procedure. If the facilitator supplies a missing step, record the help. A hint can be good teaching, but it changes what the run demonstrates. The pause may reveal something the author knows so well that they forgot to put it on the page.

Rehearse the decision while the approver is unavailable

The new packet says storage writes are timing out, the primary approver is unavailable, the repair concerns one region and rollback compatibility remains uncertain. Hand over the revised procedure without explaining the route through it.

Watch where the responder looks, whom they contact in the simulation, what evidence they assemble and what they decide. Use simulated contacts unless real participants have agreed to take part. Nobody on production duty should discover this is a rehearsal only after receiving an unexpected page.

Finding the delegate may be only half the improvement

Suppose the participant finds the alternate but cannot identify the compatibility evidence. The new route helped; the decision is still incomplete. Record both. If the procedure ends with “use judgment,” it may have moved the original ambiguity rather than removed it.

A comparison of speed needs comparable timestamps from both runs. Two impressions of how long things took cannot support “50% faster.” There is nothing weak about a precise qualitative result: “The participant found and followed the previously missing approval route without a hint.” That describes something observed, not something the edit was hoped to achieve.

This time, the alternate is unavailable too

Change the role card. Can the responder now find the escalation route and keep managing impact while waiting? Success with an available delegate has not tested this second path.

Keep the procedure proportionate to the decision. A small, familiar incident may need one concise authority entry; higher consequences or uncertainty call for more detail. Edit the missed step and replay it. Another participant can show whether the wording works beyond its author. A solo walkthrough can still help, provided it stays labeled as one.

Save the point where the next edit belongs

Keep the original gap, revised procedure and actual replay together. “Found the delegate alone; the request came back for a missing rollback condition” tells the next editor where to work. “Tabletop completed” tells them only that the meeting ended.

If you worked alone, report a desk walkthrough with no independent responder test; a facilitated rehearsal remains a next step. The useful result is not a polished procedure standing by itself. It is the moment another person could take the next step with it, alongside the precise place they still needed help.

Sources

Postmortem culture and incident response provide background. The authority scenario is synthetic teaching material.