# Start debriefs from expected versus actual

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
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Start debriefs from expected versus actual

ID: MHC-D-RESEARCH-9110 · Version: 0.1.0 · Kind: question
Source: https://vedokrok.com/knowledge/start-debriefs-from-expected-versus-actual

Comparison gives reflection an anchor.

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

### Use when

- When retrospectives drift into general impressions and recent anecdotes.

### 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

Write the expected result or process first, then place actual evidence next to it. Investigate the largest meaningful gap instead of collecting every complaint.

### Question

What did we expect? · What actually happened? · Which gap matters most? · What explains that gap well enough to change the next attempt?

### Example

The team expected all 500 records to reconcile in 20 minutes; actual result was 420 in 55 minutes with one queue bottleneck.

### Check

The debrief centers on an observable gap rather than a mood survey.

### 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

### Vedokrok editorial review

Compare the result with the expectation recorded beforehand

A debrief needs an expected result, but hindsight can quietly rewrite it. Start with the plan or criterion that existed before the work, not a target invented after the outcome.

#### Put the prior plan beside the actual evidence

Bring the task brief, acceptance criterion or dated forecast and compare it with logs, outputs and observations from the same activity. Note relevant constraints and any changes made during execution. In a hypothetical rehearsal, a ticket expected 500 records to reconcile in 20 minutes; the run produced 420 in 55 minutes. Inspect the gap without silently replacing the original target or assuming that the delay has a single cause.

#### Label reconstruction when a prior record is missing

A remembered expectation can still help the discussion, but call it a reconstruction and record disagreements. Separate “what we expected then” from “what we now think would have been sensible.” Set a clearer expectation for the next cycle rather than presenting a retrospective standard as an agreed one. NASA’s guide supplies the planned-versus-actual structure; the timestamp distinction adapts open-science transparency guidance to an ordinary work debrief.

**Editorial takeaway:** Keep the original expectation, the observed result and any later reinterpretation distinct. This supports learning from the work; it does not establish causation, prove the plan was sound or replace formal accountability processes.

#### Editorial evidence

- supports: NASA’s after-action-review guide compares intended activities and plans with actual events, then records lessons and next actions. — EA-NASA-AAR-PAUSE-LEARN. Selected official guidance inspected on 2026-10-05. It describes a learning process, not a controlled test of this work-debrief example. Its separate immediate-timing suggestion is not adopted as a universal rule. (Steps 4–8, PDF p.1; Important Tips, p.2)
- challenges: Recording a plan makes all later interpretations confirmatory or guarantees a sound conclusion. — RS-8AFFAB6BB9BA52C9. Selected methodological guidance inspected on 2026-10-05. Prior planning is insufficient by itself, and departures should remain visible. A dated work brief is not being presented as formal preregistration. (Transparent Changes; FAQ on planned/unplanned analyses, selective interpretation and changing a preregistration)
- EA-NASA-AAR-PAUSE-LEARN: After Action Review (Pause and Learn) — https://www.nasa.gov/wp-content/uploads/2025/09/after-action-review-v3.pdf
- RS-8AFFAB6BB9BA52C9: Preregistration — Center for Open Science — https://www.cos.io/initiatives/prereg

Editorial version: 1.0.0 · evidence checked 2026-10-05 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/end-debriefs-with-one-changed-behavior
