Start typing to search the site
Teams postpone runbooks because documentation feels secondary during calm periods. Then an incident lands on the wrong person at the wrong time and institutional memory turns out to be a very weak system.
Shared responsibility can improve collaboration. It can also become the sentence teams use when accountability is too blurry to survive an incident cleanly.
The incident pattern your team keeps normalizing is usually a design signal. On-call pain is one of the clearest ways a system reveals where its architecture is actually weak.
Repeating a failing action can be useful. It can also multiply load, duplicate side effects, and hide the fact that the system was never designed to fail safely.
Teams love pushing work into the background because the request gets faster. They forget the complexity did not disappear. It just moved somewhere less visible.
Schema changes look safe in tiny local databases. Production is where table size, lock time, and rollout order turn an ordinary migration into a real incident.