

Overcoming Normalisation of Deviance
Jan 2, 2019
Celebrate a year of insights with a discussion on the perils of normalisation of deviance in tech. Flickering tests lead to deeper issues that can mirror historical disasters. The conversation emphasizes the necessity of psychological safety, encouraging team members to voice concerns about risks. Pair programming is revealed as a powerful tool for enhancing team alignment and communication. Discover innovative strategies for fostering safety in high-risk environments like oil rigs, spotlighting the need for open dialogues and support.
AI Snips
Chapters
Transcript
Episode notes
Deployment Override Caused Outage
- A manual deployment override was done despite broken upstream builds due to mistrusting a flickering test.
- This action caused a partial site outage but was quickly reverted once the issue was discovered.
Normalization of Deviance Explained
- Normalization of deviance means deviations from protocol become accepted as normal.
- This concept explains how repeated ignoring of warnings can lead to disastrous outcomes.
Groups in Deviance Normalization
- People who observe problems may downplay or ignore them, or fail to speak up due to fear.
- Some junior team members assume silence means no problem, reinforcing deviance normalization.