When Ops Heroes Burn Out: Tackling Personal Heroism in Operations

What Is Personal Heroism?

According to Interactive Encyclopedia, personal heroism emphasizes individual effort over the masses to accomplish social tasks, contrasting with revolutionary heroism. It places personal influence above collective wisdom.

In the context of operations, personal heroism can be defined as relying on individual effort to keep a problematic system appearing normal, often at personal cost.

The system may consist of services, teams, processes, software, or any combination of these.

Manifestations of Personal Heroism in Operations

Operations define SLAs or other metrics for system health. When systems fail to meet these targets, a "hero" works overtime, including weekends, to meet the expectations.

Working late every day

Using weekends

Specific Examples

Ticket Queue

A team promises a 24‑hour ticket‑resolution SLA. Rapid business growth generates many tickets, overwhelming the 8‑hour shift. Heroes extend workdays to 10, 12, even 16 hours to meet the SLA.

Service SLA

A production service aims for "four nines" availability, but architectural, release, and monitoring issues prevent it. Heroes manually monitor, roll back problematic releases, anticipate resource alerts, and restart faulty programs to maintain the SLA.

Is Personal Heroism Good?

Evaluation depends on perspective.

Company view: Short‑term benefit of stable systems, but long‑term harm as hidden problems surface and hero burnout leads to turnover.

Team members view: Short‑term relief, but creates false confidence, discourages systemic improvements, and influences newcomers to accept the status quo.

Hero’s view: Limited personal gain; effort is often invisible, repetitive, and does not lead to promotion, eventually causing fatigue and possible departure.

System view: Apparent smooth operation masks deep issues; reliance on a single person creates a single point of failure.

How to Avoid Personal Heroism

While heroic actions can help during incidents, sustainable operations require eliminating dependence on individuals.

Why It Happens

Quick fixes are easy and provide immediate results.

Immediate impact gives a sense of achievement.

Perceived importance of the work despite lacking a holistic view.

Prevention Strategies

1. Communicate the Issue

Regularly share the drawbacks of personal heroism, encourage problem reporting, and promote upward feedback.

2. Work Allocation

Use feedback to plan improvements, reducing reliance on single individuals and focusing on long‑term value projects.

3. Set Realistic Expectations

Acknowledge when SLAs cannot be met and prioritize system improvements over temporary patches.

4. Eliminate Single Points

Document component architecture, automate repetitive tasks, provide checklists, share knowledge, and ensure backup personnel.

Conclusion

Personal heroism resembles a fire‑fighter who constantly extinguishes flames without addressing the cause; reducing it means building autonomous systems that achieve high SLA without extra human effort.

Leaders must identify and remove reliance on heroic individuals, while practitioners should avoid becoming the sole hero.

Don't sacrifice your social life for professional life and later regret it.