The operational debt your expertise is hiding

Experienced engineers often develop a tolerance for operational friction that becomes invisible to them but overwhelming for newer teammates. This piece examines how operational debt manifests through blurred on-call/support boundaries, undeclared incidents, noisy alerts, and high-urgency/low-autonomy situations. Staff engineers and tech leads are urged to stop being operational heroes and instead fix the underlying systems: separate on-call from support, declare incidents consistently, tune alerts to match actual risk, and prioritize paying down operational debt even at the cost of feature work. The core message is to design systems for average competent engineers, not for experts who know where all the landmines are.