🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
Learning/Post-Mortem Database
Purpose: Capture learnings from incidents, projects, or experiences.
Schema
| Property | Type | Options | Purpose |
|---|---|---|---|
| Title | title | - | Event or project name |
| Date | date | - | When it happened |
| Type | select | Incident, Project, Experiment, Retrospective | Learning type |
| Severity | select | Critical, Major, Minor | Impact level (for incidents) |
| Team | people | - | Who was involved |
| Key Learnings | number | - | Count of learnings |
| Action Items | relation | Links to tasks | Follow-up actions |
Content Template
Each learning page should include:
- What Happened: Situation description
- What Went Well: Success factors
- What Didn't Go Well: Problems encountered
- Root Causes: Why things happened
- Learnings: Key takeaways
- Action Items: Improvements to implement
Best Practices
- Blameless approach: Focus on systems and processes, not individuals
- Document quickly: Capture while memory is fresh
- Identify root causes: Go beyond surface-level problems
- Create action items: Turn learnings into improvements
- Follow up: Track that action items are completed
- Share widely: Make learnings accessible to entire team