Heroics Are Expensive

Every organization has one.

The person who knows where everything is. The person who can calm the angry customer, repair the broken report, find the missing invoice, restart the system, and translate what the owner meant. When something catches fire, everyone knows whom to call.

That person is valuable. The dependence is not.

Leaders often confuse heroics with high performance because the rescue is visible. The prevented crisis is quiet. Nobody gets applause for the fire that didn’t start. The person who fights it at midnight receives the thank-you email, while the person asking for a maintenance schedule looks unnecessarily cautious.

Strategy is what you fund when nothing is on fire.

This creates a dangerous incentive: organizations reward recovery more visibly than prevention. Eventually, the company starts depending on the drama it claims to dislike.

Heroics are expensive in at least three ways.

First, they conceal the real cost of a weak system. The issue looks resolved because the team saved the customer or shipped the order. But leaders rarely assign the overtime, interruption, rework, and diverted attention to the failure that caused them. The business sees the recovered revenue and misses the margin that disappeared during the rescue.

Second, heroics create single points of failure. The more often one person saves the day, the more work naturally routes toward that person. Their knowledge grows while everyone else’s opportunity to learn shrinks. Eventually, the organization can’t promote them, replace them, or allow them to take a genuine vacation.

Third, heroics exhaust the people we claim to value most. A dependable employee becomes the answer to every exception. The organization rewards reliability with more interruptions. Over time, it burns out the very person holding everything together.

The answer isn’t to discourage initiative. When someone steps up in a crisis, thank them. Then make the rescue teach the system.

Ask which signal the team missed. Ask which decision lacked an owner. Ask whether the team had a procedure, understood it, could access it, and followed it. Ask what would’ve prevented the event or reduced its impact. Assign the corrective action to a named owner and review whether it worked.

Don’t stop at, “We handled it.” That’s a description of survival, not improvement.

A mature organization converts individual wisdom into organizational capability. The technician’s fix becomes a documented procedure. The manager’s judgment becomes an escalation rule. The founder’s instinct becomes a decision standard. People remain important—deeply important—but the business no longer requires a particular person to perform a miracle on demand.

You can test your own organization with a simple exercise. List the five people who receive the most “quick questions.” Then list the decisions or problems behind those interruptions. Patterns will appear. Those patterns are showing you where the system is borrowing stability from an individual.

Build the system before you celebrate the next rescue. Gratitude is appropriate. Dependence is not.