Principle
Review a risky success, not only a visible failure
Success can be a bad process wearing a good outcome.
Before you use it
- Use when
- The result was good, but the path included an unsafe shortcut, surprising recovery, fragile assumption or unusual rescue.
Keep this limit in mind
- Do not manufacture problems from every successful task. Use this when the path contains credible risk, surprise or recovery worth understanding.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Debrief the process when the outcome was better than the path deserved. Ask what had to go right, which adaptations rescued the work, what nearly failed and whether the same process would be acceptable if repeated. Preserve useful resilience as well as weaknesses. This prevents a lucky result from silently certifying a fragile method.
An example
A deployment succeeds only because one engineer manually spots an undocumented configuration mismatch. The release is successful, but the mismatch and rescue still deserve review.
Check your result
At least one process lesson is recorded independently of whether the final outcome was good or bad.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingReview a risky success, not only a visible failure
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaPast success does not make a deviation safe
Evidence and sources
AHRQ recommends using briefings and debriefings as learning opportunities after routine work and after exceptionally poor or good outcomes.
A debrief can surface hypotheses and adaptations but does not establish causality by itself.
Engineering Safe Practices Affinity Group · Strategy 5: Incorporate Learning Opportunities into Routine Processes
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.