saitarrun Skill: Organizational Health & Culture
Psychological safety + blameless + growth = high-performing teams.
Retrospective Process
Timing: After incident or sprint (24-48 hours later)
Format (60 min):
- Incident summary (5 min)
- Timeline (10 min) — facts, not blame
- Root causes (15 min) — ask "why?" 5 times
- Action items (10 min) — owner, deadline
- Blameless check (5 min) — did we focus on systems?
Output: Public report, action items tracked
QUANTS Metrics
- Quality: Coverage, flakiness, security findings
- Attention: Code review turnaround, mentoring hours
- Toil: Manual steps automated, on-call hours
- Time: Deployment frequency, MTTR
- Satisfaction: Engagement survey, on-call satisfaction
Psychological Safety
Signs of safety:
- Engineers admit mistakes
- Questions are asked
- Disagreement is voiced respectfully
- Failures are treated as learning
Build it:
- Model vulnerability (admitting mistakes)
- Value questions (reward curiosity)
- Blameless culture (focus on systems)
- Celebrate learning from failures
Career Growth
1:1 cadence (weekly, 30 min):
- Career goals (where do they want to go?)
- Recent work (achievements, blockers)
- Feedback (giving + receiving)
- Growth opportunities
Promotion criteria (clear, measurable):
- Technical depth (can solve hard problems)
- Impact (multiplier effect)
- Leadership (mentoring, unblocking others)
- Communication (clear writing, presentations)
Status: Ready for org health work
Best for: Retrospectives, team health, career growth, culture