PLAYBOOK

How to Convince Your Organization to Adopt Chaos Engineering

Win over and convince your coworkers and management to explore and adopt Chaos Engineering and Site Reliability Engineering (SRE).

The playbook provides ideas and techniques that can be used to articulate the need and benefits to internal stakeholders in your organization. It also guides the initial implementation in a way that will lead to success and growth across the organization.

Get the playbook

Thanks for requesting How to Convince Your Organization to Adopt Chaos Engineering! View the guide here. (A copy has also been sent to your email.)


About the Authors

Jordan Pritchard

Director of Infrastructure & Site Reliability Engineering

Michael Kehoe

Architect of reliable, scalable infrastructure

Rodney Lester

Technical Lead, Reliability Pillar of Well Architected Program

Tammy Butow

Principal SRE

Jay Holler

Manager, Site Reliability Engineering

Ramin Keene

Founder

Implementing something new like Chaos Engineering successfully is a good way to get promoted and help the organization succeed, and this guide is here to help you.

In this guide we tell you:

  • Why Chaos Engineering matters
  • How to identify a use case within your organization
  • How to sell the discipline of Chaos Engineering
  • How to build the business case
  • What the procurement process looks like
  • How to build for the long term

  • Incident classification: SEV descriptions and levels, and SEV and time-to-detection (TTD) timelines

  • Organization-wide critical service monitoring, including key dashboards and KPI metrics emails

  • Service ownership and metrics for organizations maintaining a microservices architecture

  • Effective on-call principles for site reliability engineers, including rotation structure, alert threshold maintenance, and escalation practices

  • Chaos Engineering practices to identify random and unpredictable behavior in your system

  • Monitoring and metrics to detect incidents caused by self-healing systems

  • Creating a high-reliability culture by listening to people in your organization

While this guide focuses on Chaos Engineering, many of the principles and concepts presented in this playbook will be applicable for anyone looking to make organizational or cultural change, or to bring on a new software tool to your organization.

Over a decade of collective experience unleashing chaos at companies like

Get the playbook

Avoid downtime. Use Gremlin to turn failure into resilience.

Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.

Product Hero ImageShape