When an idea fails or a production incident occurs, an engineering manager can look for someone to blame—or help the team learn what happened. A blameless culture makes it safe for people to share what they know about failures without being personally punished for speaking up. It does not mean ignoring errors: the team still investigates causes and makes corrections. section 1.1.3 section 12.2.6
Put the norm into practice in two settings:
- During innovation, invite feedback and new ideas. Treat ideas that do not reach production as learning opportunities, and make room for healthy mistakes. section 1.1.3
- After a major incident, invite team members’ perspectives, analyze root causes, identify improvements, and implement corrective actions. section 12.2.6
- Carry the learning forward by updating troubleshooting guides and improving on-call practices. section 12.2.6
After an incident
Suppose a production incident exposes a gap in a troubleshooting guide. In the postmortem, team members can describe what they encountered without the discussion becoming a search for someone to blame. The team can then investigate the root cause, agree on corrective actions, and update the guide. The aim is better support next time, not a consequence-free review. section 1.1.3 section 12.2.6
For the next failed experiment or major incident, ask: What information might people hesitate to share, and what can the team change after hearing it? section 1.1.3 section 12.2.6
