A just culture is one where organizations and their people value resilience and improvement. It is one where leadership and their people can admit mistakes, accept failure, and jointly feel accountable to learning and improving. This track will provide practices and processes that demonstrate how both psychological safety and safety engineering can lead to higher quality software and happier teams. It will talk about moving beyond just blameless postmortems and retrospectives to building a culture where folks are rewarded for being the messenger. Topics will include incident management techniques, risk management practices, and learning practices.
From this track
Generous, High Fidelity Communication Is the Key to a Safe, Effective Team
Monday Dec 5 / 09:00AM PST
A team's ability to communicate effectively and disagree productively is directly related to its resilience towards incidents and interruptions.
Engineering Manager and Rubyist
Recipes for Blameless Accountability
Monday Dec 5 / 10:10AM PST
Engineering Manager SRE @Google
How Did It Make Sense at the Time? Understanding Incidents As They Occurred, Not as They Are Remembered
Monday Dec 5 / 11:20AM PST
When we encounter undesirable outcomes, there is a natural instinct to look back, find something that went wrong, and fix it.
Staff Software Engineer @stripe
Reckoning with the Harm We Do: In Search of Restorative Just Culture in Software and Web Operations
Monday Dec 5 / 12:30PM PST
“Psychological Safety” and “Blameless” postmortems are not enough. We’ve heard that we need a “Just Culture” but does that matter if your people are “stressed, exhausted, depleted, spent, drained”?
Sr. Software Engineering Manager - SRE @Microsoft