Ruby Video
Talks
Speakers
Events
Topics
Leaderboard
Sign in
Talks
Speakers
Events
Topics
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
RubyConf 2018 - Retrospectives for Humans by Courtney Eckhardt Seattle has two of the longest floating bridges in the world, and in 1990, one of them sank while it was being repurposed. This accident was a classic complex systems failure with a massive PR problem and great documentation. That combination is an excellent frame for talking about incident retrospectives- the good, the bad, the vaguely confusing and unsatisfying. Come for the interesting disaster story, stay to learn about the language of blame and how to ask warm, thoughtful engineering questions.
Date
Summary
Markdown supported
In the talk "Retrospectives for Humans" presented by Courtney Eckhardt at RubyConf 2018, the speaker explores the concept of incident retrospectives and their importance within teams. The discussion begins with an acknowledgment of the challenging times, setting a compassionate tone before diving into the main topic of retrospectives, particularly in agile environments. Eckhardt uses the 1990 sinking of the Merle Bridge in Seattle as a case study to illustrate the complexities involved in understanding failures. The bridge, one of the longest floating structures in the world, sank while undergoing maintenance due to several contributing factors that the official investigation outlined. Key points from this example include: - **Complex Systems Failures**: The investigation identified five necessary factors that led to the bridge's failure, emphasizing how multiple elements can converge to cause significant incidents. - **Communication and Misunderstanding**: Despite thorough documentation, the investigation lacked clarity on social dynamics, exposing a gap in understanding how decisions were made and processes were adhered to during the crisis. - **The Role of Facilitators in Retrospectives**: Eckhardt highlights the importance of creating a blame-free environment during retrospectives. Facilitators should focus on constructive dialogue, guiding questions to uncover underlying issues, and ensuring everyone's voice is heard. Throughout the talk, Eckhardt stresses the importance of thoughtful questioning: - Avoid blame-filled language by steering clear of "you" and “why” questions. - Use reflective prompts like "What could have been done differently?" to foster a collaborative atmosphere. The speaker also addresses common fallacies in retrospectives, such as the assumption that recognizing a mistake equates to preventing it from happening in the future. Instead, Eckhardt emphasizes the need for understanding systemic issues and human variability. Eckhardt concludes with strategies for effective retrospectives, including: - Preparing an agenda to keep discussions focused. - Being attentive to group dynamics and encouraging participation from all members. - Handling humor with sensitivity, ensuring respect and positivity remain at the forefront of discussions. Ultimately, the session stresses that retrospectives are key to organizational growth, inviting teams to learn from their experiences and to foster a culture that encourages responsible risk-taking and collective learning. The importance of maintaining a blameless environment and constructive dialogue is reiterated throughout the presentation, providing attendees with actionable insights for improving their retrospective practices.
Suggest modifications
Cancel