Don't Overfit On Past Problems
Your team is just coming off a major incident. In the postmortem you all come up with a number of ways to avoid having that problem happen ever again.
Good. Now take a second look at that list and make sure that you're not just setting up guards to prevent the exact same problem. It's important to make sure you don't make the same mistake twice but you want to make sure that your solutions are pragmatic.
You want to avoid solutions that are too narrow; they only address the very specific problem you just encountered and solutions that are overly restrictive; they overreact to the problem by making to hard to do anything.
Very specific solutions are often "cover your ass" work. They end up introducing complexity without being as effective as understanding the root cause of the problem and coming up with general solutions.
Overly restrictive solutions can end up producing process debt. It's tempting to lock things down with stuff goes wrong, but rather than putting up roadblocks to prevent problems, take the time to really understand where the gaps in your process are that can allow mistakes to get shipped. Make smart tradeoffs between safety and speed.
Things going wrong are an opportunity to make improvements. Just make sure you're making the right ones.