# Let a colleague rehearse the runbook without your missing context

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Let a colleague rehearse the runbook without your missing context

ID: MHC-D-RESEARCH-1014 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/let-a-colleague-rehearse-the-runbook-without-your-missing-context

The missing step is usually obvious to the person who forgot to write it.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A procedure looks complete to its author but must work for another qualified operator.

### Avoid when

- Never create uncontrolled production failures to test documentation. A runbook cannot replace prerequisite training, access or judgment.

### Explanation

Give a colleague a safe practice scenario and the documented starting conditions. Observe where they need information that exists only in your head. Use the rehearsal to repair the procedure, including expected results and escalation points, rather than grading the colleague for not reading your mind.

### Steps

1. Choose an isolated or simulated case with a safe reset and clear stop conditions.
2. Let the colleague follow the documented route; record needed prompts and ambiguous steps.
3. Revise the runbook and repeat the affected part with the agreed support level.

### Example

A new support engineer rehearses a failed import. The exercise reveals that the runbook never identifies which log belongs to the processing attempt.

### Check

The colleague can reach the expected result or correctly escalate using the stated prerequisites and support.

### Limits

- Never create uncontrolled production failures to test documentation. A runbook cannot replace prerequisite training, access or judgment.

### Evidence and sources

- supports: The SRE on-call account uses practical exercises and incident role-play alongside documented playbooks, including semi-independent onboarding exercises. — RS-2B5F7E58BBC9FD5B. Testing a runbook with a colleague is an editorial extension; the source does not isolate its causal effect on incident outcomes. (Training roadmap; Afterword; Maintaining Playbooks)
- RS-2B5F7E58BBC9FD5B: Being On-Call — https://sre.google/workbook/on-call/

No review details supplied.
