Selling your Company on Chaos Engineering
summary
Practical playbook for getting budget and rollout approval: treat fault injection as a feature of high‑priority projects (cloud migration, DR, observability) rather than a standalone “chaos” initiative, meet vendors in person and insist they document attendees and mutual next steps, identify and win over mobilizers (go‑getters, teachers, skeptics), produce an implementation plan listing apps, metrics, resources and incentive changes, use conservative savings (example used $55,000 per downtime hour) and negotiate per‑service pricing or limited entitlements.
AI-written summary · about
chapters (12)
- 0:00intro
- 0:22preamble
- 0:55goals for our session
- 2:03sales rep owners manual
- 5:21selling to internal stakeholders
- 12:08hogh roi project alignment
- 14:42migrate to the cloud with less downtime
- 15:45observability vs monitoring
- 16:54other potential ideas
- 18:10building your business case
- 19:06write an implementation plan
- 20:07key takeways
related talks
27mChaos Engineering: The Path to Reliability
18mChaos Engineering: Break It On Purpose
36mChaos Engineering in 2021
23mHow to tame chaos effectively?
48mChaos Engineering: The Path to Reliability
31mPlanning for Failure using Chaos Engineering
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure
26mImprove application resilience with chaos engineering