# Practice the backup before you need the backup

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: MHC-RPUB-20261011-9e4b62c5
Snapshot SHA-256: b97dfd5520e2cf31744978d7e824b94e55bd12d9a2bdef759b5bc69a963375e5
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Practice the backup before you need the backup

ID: MHC-D-RESEARCH-9226 · Version: 0.2.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/practice-the-backup-before-you-need-the-backup

A backup on a map is not a backup until the handoff has survived a realistic attempt.

### Use when

- Your expertise map names a backup, but nobody knows whether that person can actually carry a recurring critical task when the primary is unavailable.

### Avoid when

- Do not rehearse on live high-risk systems without safeguards. Licensed, regulated or safety-critical work may require formal authorization and supervised training. Cross-training depth produced inconsistent findings in the experimental literature, and much of the evidence is simulation-based; demonstrated backup readiness does not make people interchangeable experts.

### Explanation

Choose one recurring, consequential workflow with a single point of failure. Let the backup perform a realistic case while the primary observes only at agreed stop points. Capture missing decision cues, access, artifacts and escalation conditions, fix those gaps, then repeat with the primary unavailable. Cross-training studies support shared interaction models and coordination, but much of the evidence comes from simulations and does not imply that every role should be duplicated.

### Steps

1. Pick one task where primary-person absence would materially delay or endanger the work. Define success, stop conditions and the escalation route.
2. Give the backup the current artifact and a minimal walkthrough, then let them execute a realistic case rather than merely watch the primary.
3. Record each failure as a concrete gap: missing context, permission, tool, decision cue, artifact or escalation rule. Repair the smallest useful gap.
4. Retest after the repair or a meaningful system change with the primary unavailable. Keep the formal owner and escalation path explicit.

### Example

An integration team lists a second engineer as backup for payment-retry incidents. During rehearsal, the backup discovers a hidden dashboard permission and an undocumented rollback threshold. The team fixes the access and records the threshold; on the next drill, the backup can complete the case without the primary.

### Check

With the primary unavailable, the backup can either complete the defined case safely or stop at the right boundary and escalate using current artifacts and permissions.

### Limits

- Do not rehearse on live high-risk systems without safeguards. Licensed, regulated or safety-critical work may require formal authorization and supervised training. Cross-training depth produced inconsistent findings in the experimental literature, and much of the evidence is simulation-based; demonstrated backup readiness does not make people interchangeable experts.

### Evidence and sources

- supports: Across two computer-simulation experiments with 45 and 49 teams, cross-training enhanced shared team-interaction mental models; coordination mediated the relationship between those shared models and team performance. — RS-85FBF9764660FB3E9E89. The tasks were simulations, and the authors reported inconsistent findings about the depth of cross-training needed to improve shared mental models. (Abstract)
- limits: A 2007 meta-analysis found a small-to-moderate tendency for team training to improve team performance, while its analyses suggested that coordination and adaptation training contributed more strongly than cross-training alone. — RS-F8EB6521EF7C07182E49. The evidence base was small; the main analysis treated multiple tests from some studies as independent, although a supplemental seven-study analysis showed the same broad pattern. This does not identify one universally optimal training mix. (Abstract and supplemental independence analysis)
- contextualizes: A 2024 scoping review of 213 cross-disciplinary sources on team adaptation recommends realistic training with actual teams and highlights shared mental models, contingency planning, roles and responsibilities as relevant learning objectives. — RS-4B65D6D807889A08CCF5. The review synthesizes heterogeneous experimental, observational and conceptual work. Its training recommendations are not a causal test of the rehearsal protocol in this card. (Training implications and discussion)
- RS-85FBF9764660FB3E9E89: The impact of cross-training on team effectiveness — https://doi.org/10.1037/0021-9010.87.1.3
- RS-F8EB6521EF7C07182E49: Testing Three Team Training Strategies in Intact Teams: A Meta-Analysis — https://doi.org/10.1177/1046496407304332
- RS-4B65D6D807889A08CCF5: Team adaptive capacity and adaptation in dynamic environments: A scoping review of the literature — https://doi.org/10.1016/j.hfh.2024.100089

No review details supplied.
Published: 2026-10-01T14:27:00Z