# Debrief the work, not the person

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

---

## Debrief the work, not the person

ID: MHC-D-RESEARCH-9109 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/debrief-the-work-not-the-person

A useful debrief reconstructs decisions, conditions and actions.

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

### Use when

- When a result was poor and the team needs to learn without turning review into blame.

### Avoid when

- Team-learning practices consume time. Use them where there is a real performance or coordination question, and do not substitute process rituals for domain expertise.

### Explanation

Review what was expected, what happened, what information was available, what helped or hindered and what should change next time. Personal accountability can remain explicit without replacing system learning.

### Steps

1. Restate expected outcome.
2. Reconstruct what actually happened.
3. Identify decision and coordination gaps.
4. Choose one or two changes for the next cycle.

### Example

After a failed cutover rehearsal, the team traces missing ownership and late validation rather than opening with 'who caused this?'

### Check

The review produces a change to the next cycle and can still name accountable actions.

### Limits

- Team-learning practices consume time. Use them where there is a real performance or coordination question, and do not substitute process rituals for domain expertise.

### Evidence and sources

- supports: A meta-analysis of 46 samples found structured debriefs improved effectiveness on average and identified alignment, facilitation and structure as potentially important design features. — RS-99DE99332F99B58B. Average effects across training and work settings do not imply that every retrospective meeting is useful or that longer debriefs are better. (Abstract)
- RS-99DE99332F99B58B: Do Team and Individual Debriefs Enhance Performance? A Meta-Analysis — https://doi.org/10.1177/0018720812448394

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/start-debriefs-from-expected-versus-actual
