Measuring chaos: Chaos engineering and team health

Description

Chaos engineering is exploding in popularity. Once restricted to companies like Netflix, it’s becoming a common practice in organizations of all sizes. A number of great talks have delivered techniques for introducing your organization to chaos engineering, but without effective methods for measuring impact, organizations can fall victim to resiliency theater. The results of this are predictable: adoption struggles, teams feel burned out, and chaos engineering feels like a chore.

Paul Osman details how Under Armour measures the impact of chaos engineering. He walks you through a service maturity model the company created and how it uses game days to evaluate services against it. You’ll see how Under Armour uses this data to create an overall view of team health, blamelessly identifying teams that are overburdened and need additional help from its infrastructure and SRE teams to get back on track. He also walks you through how the company uses health report cards to create visibility and shared accountability for team health and psychological safety.

Under Armour’s reliability engineering team is taking the lead on moving its culture from one of fire fighting (reactive) to building inspection (proactive). He explains how Under Armour tracks incidents through five stages (ending with continuous chaos experiments) and uses incident data to prioritize proactive reliability work.