We know we've built reliable systems when we survive the surge of shoppers on Black Friday or maintain uptime during a massive migration. But reliability isn't about a single moment. It's built over time with every single deployment, resulting in a relationship of trust with your users and customers. Reliability requires practice. 

We'll kick off Chaos Conf by hearing from speakers who have deployed reliability practices and built organizations that delivered for their customers during critical moments. Tune in to hear technical reliability tactics and lessons.

Examples:

• More than a title: establishing an SRE practice in your organization
• Documenting your reliability practices with runbooks
• Setting and achieving milestones in your reliability journey

DevOps is supposed to tear down the silos separating developers and operations engineers. But too often, it creates a one-way flow from developers to ops with no feedback from ops to help developers build more operable and reliable applications. Chaos Engineering provides a way to complete the loop and prioritize quality across all teams. 

Day two of Chaos Conf will cover how to help your organizations meet reliability goals by including Chaos Engineering in the software lifecycle. 

Examples:

• Setting Service Level Objectives (SLO's) and Validating Indicators (SLI's) with Chaos Engineering
• Moving from manual Gamedays to automated Chaos Experiments
• Chaos Engineering in your CI/CD Pipeline
• Code isn't done when you deploy it - Building reliability and operability into software
• Holistic systems: bringing Developers and Operations Engineers together with Chaos Engineering 

Cultural change on the organizational level requires data to back it up. To grow an internal culture of chaos experimenation, you must democratize what you're learning. But how do we capture and share the most important lessons? How do you influence building a culture of reliability? 

Day three will cover what to measure, and how to use that data to tell stories that influence change across your organization. 

Examples:

• Using your monitoring data to guide chaos testing and verify test success
• Reliability vs Features: Using Chaos Engineering to prioritize work
• Celebrating wins - Case studies featuring how Chaos Engineering led to reduced incidents, lower MTTR, and other desired business outcomes.