Every behavioral health organization has heroes.
The supervisor who covers three caseloads during a vacancy. The program manager who knows which client needs a call on Friday afternoon because she has done it for six years. The billing lead who catches the authorization that was about to lapse because she checks a spreadsheet nobody else knows exists.
We celebrate these people, and we should. But after more than thirty years in community behavioral health, I have come to see heroics differently. Heroics are usually a symptom. They tell you where the system stopped doing its job and a person started doing it instead.
Heroics hide the real design
When a hero is holding something together, the organization looks fine from the outside. Visits happen. Notes get signed. Referral sources get a callback. The dashboard is green.
What you cannot see is the cost:
- The work depends on one person’s memory, not a documented process.
- The workload is invisible, so it never shows up in staffing decisions.
- When that person leaves, burns out, or takes a week off, performance drops and no one can explain why.
In other words, heroics keep a weak system from being exposed. That feels like a win in the short term. Over time it becomes the reason good people leave.
Caring is not the problem
Behavioral health is full of people who care deeply. I have never worked with a team that did not want to do right by the people they serve.
When results are inconsistent, the instinct is to ask people to care more, try harder, or stay later. That rarely works, because effort was never the missing ingredient. What is usually missing is the structure that turns good intentions into reliable delivery:
- A schedule that is built and protected, not improvised each morning.
- Clear expectations for how quickly documentation is completed.
- A defined process for what happens when a client misses a visit.
- A weekly rhythm where leaders look at the same few numbers and act on them.
None of that is glamorous. All of it reduces the need for heroes.
Where to look first
If you lead an organization and want to find where heroics are covering for the system, start with three questions:
- What would break if one specific person were out for two weeks? That answer points to a process that lives in someone’s head.
- Where do staff routinely stay late or work from home at night? That is usually work the schedule does not account for.
- Which problems get solved by the same person every time? Recurring rescues are a design signal, not a performance story.
Then pick one and build the system around it. Write the steps down. Assign ownership. Put it on a calendar. Measure whether it happens.
The goal is boring reliability
The best compliment an operating system can get is that nothing dramatic happens. Clients are seen consistently. Staff know what is expected. Referral partners get the same experience on a Tuesday in March that they get on a Friday in December.
That does not mean the heroes go away. It means their talent gets spent on the hard, human parts of the work instead of patching gaps the organization should have closed.
That is what I mean by systems over heroics. It is also the idea behind this site, my newsletter, and the book I am writing. If it resonates, I would like to hear where you see heroics carrying the load in your organization.
