Chaos engineering has a credibility problem. Half the teams that adopt it are doing it because it's fashionable, not because it makes their systems more reliable. The result is a lot of chaos tools getting installed, a lot of demo videos getting recorded, and not much actually improving.
If you don't have these three things in place, your chaos engineering practice is theater. Skip it and fix the prerequisites first.
1. You actually fix what chaos finds
The biggest chaos engineering failure mode I've seen: a team runs experiments, documents the issues they uncover, and then never fixes them. The findings pile up in a Jira backlog labeled "future-work" and rot.
If your team isn't going to immediately allocate engineering time to fix what chaos finds, don't run chaos. You're just generating discovery debt.
