# Turn mistakes and outcomes into changes you can verify

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

Add a compact learning loop for debriefing, root-cause exploration, prospective failure analysis and stronger corrective actions without collapsing every failure into individual blame.
Collection kind: collection
Source: https://vedokrok.com/collections/turn-mistakes-and-outcomes-into-changes-you-can-verify
Version: 0.1.0

---

## Compare expected and actual before explaining the gap

ID: MHC-D-RESEARCH-0726 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/compare-expected-and-actual-before-explaining-the-gap

Start the review with two columns, not a culprit.

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

### Use when

- A project, decision, incident or experiment has ended and the group is already telling a story about why it went well or badly.

### Avoid when

- A timeline can still be incomplete. Missing logs or observations should be marked as unknown, not filled with a plausible story.

### Explanation

Write what was expected to happen and what actually happened using observable outcomes, dates, thresholds or artifacts. Mark the first meaningful divergence. Only then discuss explanations. This separates reconstruction from hindsight and gives the review a shared object to inspect.

### Steps

1. Another person can point to the same first divergence without needing your interpretation of motive.

### Example

Expected 98% of records to validate before import. Actual 81% validated; the first divergence appeared after mapping rule 4 changed.

### Check

Another person can point to the same first divergence without needing your interpretation of motive.

### Limits

- A timeline can still be incomplete. Missing logs or observations should be marked as unknown, not filled with a plausible story.

### Evidence and sources

- supports: Structured debriefs or after-action reviews have been studied as a way to support learning from experience, with meta-analytic evidence of improved performance on average across varied settings. — RS-6A2E6BA2CE371BB3. Average effects across studies do not predict the benefit of a particular review; facilitation, task and implementation matter. (Abstract: objective, method, results and application)
- supports: After-action review effectiveness varies with design features; alignment to the person or team and objective review media were among the recurring contributors in a later meta-analysis. — RS-6A2B05A2CE34388A. The analysis covers training-evaluation outcomes and interacting moderators; it does not establish one best debrief format for every setting. (PubMed abstract)
- RS-6A2E6BA2CE371BB3: Do Team and Individual Debriefs Enhance Performance? A Meta-Analysis — https://journals.sagepub.com/doi/10.1177/0018720812448394
- RS-6A2B05A2CE34388A: A meta-analysis of the effectiveness of the after-action review (or debrief) and factors that influence its effectiveness — https://pubmed.ncbi.nlm.nih.gov/32852990/

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/bring-objective-traces-into-the-debrief

---

## Bring objective traces into the debrief

ID: MHC-D-RESEARCH-0727 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/bring-objective-traces-into-the-debrief

Memory is useful input; it should not be the only log.

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

### Use when

- A review depends mainly on memory, impressions or the loudest participant's account.

### Avoid when

- Logs can be incomplete or misleading. Treat them as evidence with provenance, not automatic truth.

### Explanation

Before the discussion, collect the smallest set of objective traces that can challenge recollection: timestamps, versions, test results, messages, metrics, screenshots, transaction IDs or recordings. Put them beside the narrative rather than using them as decoration after the conclusion.

### Checklist

- What trace fixes the timing?
- What artifact shows the state before and after?
- What evidence could contradict the current story?
- Which important interval has no trace?

### Example

Instead of debating when a configuration changed, compare transport timestamps, activation logs and the first failing test.

### Check

The review contains at least one artifact capable of falsifying a participant's remembered sequence.

### Limits

- Logs can be incomplete or misleading. Treat them as evidence with provenance, not automatic truth.

### Evidence and sources

- supports: After-action review effectiveness varies with design features; alignment to the person or team and objective review media were among the recurring contributors in a later meta-analysis. — RS-6A2B05A2CE34388A. The analysis covers training-evaluation outcomes and interacting moderators; it does not establish one best debrief format for every setting. (PubMed abstract)
- RS-6A2B05A2CE34388A: A meta-analysis of the effectiveness of the after-action review (or debrief) and factors that influence its effectiveness — https://pubmed.ncbi.nlm.nih.gov/32852990/

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/ask-what-helped-what-hindered-and-what-changes-next

---

## Ask what helped, what hindered and what changes next

ID: MHC-D-RESEARCH-0728 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/ask-what-helped-what-hindered-and-what-changes-next

A useful review connects observation to a specific next change.

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

### Use when

- A retrospective is drifting into a list of complaints or generic lessons.

### Avoid when

- This is a reflection scaffold, not a causal proof. A promising explanation may still need a test.

### Explanation

Run three passes: what supported the result, what obstructed it, and what should change next time. Keep statements close to behaviors, interfaces, conditions and decisions. Preserve successful controls as deliberately as you fix failures.

### Steps

1. Every proposed change points back to an observed condition rather than a generic slogan.

### Example

Helped: a dry-run file. Hindered: validation happened only after the full batch. Next change: validate the first 20 records automatically. Keep: dry-run checklist.

### Check

Every proposed change points back to an observed condition rather than a generic slogan.

### Limits

- This is a reflection scaffold, not a causal proof. A promising explanation may still need a test.

### Evidence and sources

- supports: Structured debriefs or after-action reviews have been studied as a way to support learning from experience, with meta-analytic evidence of improved performance on average across varied settings. — RS-6A2E6BA2CE371BB3. Average effects across studies do not predict the benefit of a particular review; facilitation, task and implementation matter. (Abstract: objective, method, results and application)
- RS-6A2E6BA2CE371BB3: Do Team and Individual Debriefs Enhance Performance? A Meta-Analysis — https://journals.sagepub.com/doi/10.1177/0018720812448394

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/give-the-lesson-a-verifiable-finish

---

## Give the lesson a verifiable finish

ID: MHC-D-RESEARCH-0729 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/give-the-lesson-a-verifiable-finish

A corrective action needs a finish line that can be inspected.

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

### Use when

- A review has produced actions but they can remain open forever or be declared done after a document edit.

### Avoid when

- Verification does not prove the original root cause was correct; monitor recurrence and side effects.

### Explanation

For each action, write an owner, a change, a due condition and a verification signal. Prefer a signal that tests the workflow, not only the existence of a new policy or slide. If the change cannot be verified, it is still an intention.

### Template

Owner: [person/role]. Change: [system or behavior change]. Done when: [observable condition]. Verify by: [test, metric or audit].

### Example

Owner: release lead. Change: add pre-import schema validation. Done when: pipeline blocks malformed files. Verify by: a known-bad fixture fails before import.

### Check

Someone outside the review can tell whether the action worked without asking the action owner.

### Limits

- Verification does not prove the original root cause was correct; monitor recurrence and side effects.

### Evidence and sources

- supports: Modern RCA guidance emphasizes system-level contributing factors and sustainable corrective actions rather than stopping at individual blame or documentation. — RS-C63447C9710D56FD. AHRQ discusses healthcare safety. The corpus transfers the system-design logic cautiously to ordinary work. (Introduction; RCA2; action hierarchy discussion)
- RS-C63447C9710D56FD: The Evolution of Root Cause Analysis — https://psnet.ahrq.gov/perspective/evolution-root-cause-analysis

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/prefer-a-system-strengthening-action-over-another-reminder

---

## Follow the why-chain until the cause becomes changeable

ID: MHC-D-RESEARCH-0730 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/follow-the-why-chain-until-the-cause-becomes-changeable

Do not stop at a label that merely renames the event.

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

### Use when

- The immediate explanation is a label such as human error, missed step, bad data or process deviation.

### Avoid when

- Five Whys is a prompt for inquiry, not a guarantee of one root cause. Complex failures commonly have interacting causes.

### Explanation

Ask why the observed event was possible, then ask why about the answer while the chain remains evidence-based. Stop when you reach a factor the system can change, when the chain branches, or when evidence runs out. Record branches instead of forcing one linear root cause.

### Steps

1. Is this answer more than a label?
2. What evidence supports the next link?
3. Did the chain split into multiple contributors?
4. Is the current factor changeable?
5. Are we now guessing?

### Example

Wrong field mapped → template used an old label → template had no version check → add a version gate at upload.

### Check

The final factor suggests a concrete control and each causal link has evidence or is marked as a hypothesis.

### Limits

- Five Whys is a prompt for inquiry, not a guarantee of one root cause. Complex failures commonly have interacting causes.

### Evidence and sources

- supports: Modern RCA guidance emphasizes system-level contributing factors and sustainable corrective actions rather than stopping at individual blame or documentation. — RS-C63447C9710D56FD. AHRQ discusses healthcare safety. The corpus transfers the system-design logic cautiously to ordinary work. (Introduction; RCA2; action hierarchy discussion)
- supports: Five Whys is used in RCA2 to extend a causal chain beyond an immediate event description. — RS-C63447C9710D56FD. Repeated 'why' questions can oversimplify branching causes; answers still need evidence. (Discussion of event mapping and Five Whys)
- RS-C63447C9710D56FD: The Evolution of Root Cause Analysis — https://psnet.ahrq.gov/perspective/evolution-root-cause-analysis

No review details supplied.
Related (alternative): https://vedokrok.com/knowledge/fan-possible-causes-out-before-narrowing-them

---

## Fan possible causes out before narrowing them

ID: MHC-D-RESEARCH-0731 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/fan-possible-causes-out-before-narrowing-them

Widen the causal search before selecting the story.

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

### Use when

- A team has one plausible explanation too early or the problem spans people, process, tools and environment.

### Avoid when

- Fishbone diagrams organize hypotheses. They do not establish causal strength or exhaust all possible causes.

### Explanation

Put the observed effect at the head of a cause-and-effect diagram. Add a few context-appropriate branches such as process, information, tools, environment, interfaces and workload. Generate candidate causes under each branch, then mark which candidates have evidence, which need tests and which are already contradicted.

### Steps

1. The diagram contains competing candidate causes and an evidence status, not just a decorative list.

### Example

Repeated upload failures branch into file format, mapping rules, permissions, runtime capacity and operator sequence before testing each candidate.

### Check

The diagram contains competing candidate causes and an evidence status, not just a decorative list.

### Limits

- Fishbone diagrams organize hypotheses. They do not establish causal strength or exhaust all possible causes.

### Evidence and sources

- supports: A cause-and-effect or fishbone diagram is a structured way to lay out suspected causes across categories before deeper analysis. — RS-C6EF83B5DEEEBAC3. The diagram generates hypotheses about causes; it does not verify them. (Description, uses and steps)
- RS-C6EF83B5DEEEBAC3: Cause-and-Effect Diagram — https://digital.ahrq.gov/health-it-tools-and-resources/evaluation-resources/workflow-assessment-health-it-toolkit/all-workflow-tools/cause-and-effect-diagram

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/follow-the-why-chain-until-the-cause-becomes-changeable

---

## Run failure-mode analysis before the consequential change

ID: MHC-D-RESEARCH-0732 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/run-failure-mode-analysis-before-the-consequential-change

Ask how the process can fail before production teaches you.

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

### Use when

- You are about to change a process, migration, automation or workflow where one missed failure mode could have a large blast radius.

### Avoid when

- FMEA prioritization numbers are not calibrated probabilities. Use them to structure attention, not simulate certainty.

### Explanation

Walk each important step and list plausible failure modes, their effects, existing controls and detectability. Use rough severity/likelihood/detectability ratings only to prioritize attention. Spend the review on weak controls and hard-to-detect high-impact modes, not on debating a precise risk score.

### Steps

1. At least one high-impact or hard-to-detect failure mode has a stronger prevention, detection or recovery control.

### Example

Bulk update: wrong selection filter → thousands of unintended records → current control: manual review → detection: after activation → safeguard: pre-run count and sampled IDs.

### Check

At least one high-impact or hard-to-detect failure mode has a stronger prevention, detection or recovery control.

### Limits

- FMEA prioritization numbers are not calibrated probabilities. Use them to structure attention, not simulate certainty.

### Evidence and sources

- supports: FMEA is a prospective method for identifying possible failure modes and considering their effects before or during process improvement. — RS-D8547C3B32436378. Priority scores are heuristics; they should not be mistaken for calibrated failure probabilities. (Description and uses)
- RS-D8547C3B32436378: Failure Mode and Effects Analysis — https://digital.ahrq.gov/health-it-tools-and-resources/evaluation-resources/workflow-assessment-health-it-toolkit/all-workflow-tools/fmea-analysis

### Vedokrok editorial review

Follow failure-mode analysis through to checked actions

Finding a risk is useful; improving one safeguard does not settle all the other risks. Keep each priority failure mode connected to an owner, an action and a follow-up check.

#### Describe the failure before scoring it

For a bounded process, involve people who understand its important steps. Record how each step could fail, its effects, likely causes and the controls already in place. Consider severity, likelihood and how early the failure would be noticed. Ratings help order the discussion; they are not calibrated probabilities or a substitute for judgment.

#### Track what the review changes

For each mode selected for action, name the change, owner, due point and evidence to collect. Record the result when the action is completed, then reconsider the risk. For a bulk import, one check might reject a wrong account filter before writes begin; separately track a possible duplicate write. Do not close both risks because only the filter check improved.

**Editorial takeaway:** Before calling the review complete, inspect the actions and unresolved risks across its stated scope. FMEA requires informed judgment and can miss or misrank risks; this compact aid is not a replacement for a qualified safety review.

#### Editorial evidence

- supports: The AHRQ FMEA procedure defines the scope, examines failure modes and controls, assigns action owners and deadlines, then records completion results and revises ratings. — RS-D8547C3B32436378. Selected official procedure inspected on 2026-10-04. The import example and per-mode follow-up wording are editorial adaptations of the action and result steps. (How do I use this tool?, steps 1–14, especially 13–14)
- limits: The guidance expects some training or experience and warns that the method is not foolproof in identifying highest risk or action priority. — RS-D8547C3B32436378. Ordinal ratings organize attention; no numerical score is presented as measured risk or evidence that all failure modes were found. (Expertise Required; Disadvantages)
- RS-D8547C3B32436378: Failure Mode and Effects Analysis — https://digital.ahrq.gov/health-it-tools-and-resources/evaluation-resources/workflow-assessment-health-it-toolkit/all-workflow-tools/fmea-analysis

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

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/prefer-a-system-strengthening-action-over-another-reminder

---

## Prefer a system-strengthening action over another reminder

ID: MHC-D-RESEARCH-0733 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/prefer-a-system-strengthening-action-over-another-reminder

If the same slip can recur unchanged, the action probably did not reach the system.

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

### Use when

- The proposed fix is training, a policy reminder, a warning email or 'be more careful' after a repeatable failure.

### Avoid when

- Not every problem can be engineered away. Accountability, skill and judgment still matter; the point is not to misclassify a system defect as a memory problem.

### Explanation

Compare the proposed action with stronger options: remove the hazardous step, constrain invalid input, change the default, automate a check, improve visibility, reduce ambiguity or add recovery. Training can still be useful, especially for knowledge gaps, but do not use it as the automatic answer to a design defect.

### Example

Instead of reminding analysts to check a file version, reject uploads whose schema version does not match the target.

### Check

The selected action changes the conditions under which the error occurs, or explicitly explains why that is not feasible.

### Limits

- Not every problem can be engineered away. Accountability, skill and judgment still matter; the point is not to misclassify a system defect as a memory problem.

### Evidence and sources

- supports: Modern RCA guidance emphasizes system-level contributing factors and sustainable corrective actions rather than stopping at individual blame or documentation. — RS-C63447C9710D56FD. AHRQ discusses healthcare safety. The corpus transfers the system-design logic cautiously to ordinary work. (Introduction; RCA2; action hierarchy discussion)
- RS-C63447C9710D56FD: The Evolution of Root Cause Analysis — https://psnet.ahrq.gov/perspective/evolution-root-cause-analysis

No review details supplied.
