Incident and Defect Learning
Template Library
Incident and Defect Learning
Convert incidents and defects into learning, patterns, root-cause themes, preventive actions, owners, and routes.
ES-114
Incidents/Defects
Failure Learning
Template purpose
Use this template to convert incidents and defects into learning, patterns, actions, and routed follow-up.
Project
<Project name>
Document control
| Field |
Value |
| Artifact owner |
<owner> |
| Primary reviewers |
<reviewers> |
| Status |
<draft / in review / accepted / revised> |
| Last updated |
<YYYY-MM-DD> |
| Related Engineering Stage |
ES-114 — Post-Release Learning and Stewardship |
| Project workspace target |
docs/project-workspace/stewardship/incident_and_defect_learning.md |
Incident / defect learning register
| ID |
Incident / Defect |
Evidence |
Learning |
Action |
Owner |
Route |
Status |
| IDL-001 |
<incident/defect> |
<evidence> |
<learning> |
<action> |
<owner> |
<ES-### / backlog / governance> |
<open / closed> |
Recurring patterns
| Pattern |
Evidence |
Implication |
Action |
<pattern> |
<evidence> |
<implication> |
<action> |
Root cause themes
| Theme |
Evidence |
Engineering Implication |
<theme> |
<evidence> |
<implication> |
No-incident learning
<If no incidents occurred, describe what the absence of incidents does and does not prove.>
Preventive actions
| Action |
Owner |
Route |
Priority |
<action> |
<owner> |
<route> |
<priority> |
Review checklist
- [ ] Incidents and defects trace to evidence.
- [ ] Learning is separated from raw event description.
- [ ] Recurring patterns are identified.
- [ ] No-incident learning is included when applicable.
- [ ] Preventive actions have owners and routes.