Last month, the leadership team in a manufacturing business I help run pulled off a rescue.

A pile of rush orders had stacked up. Three managers dropped what they were doing, chased down parts, pulled people onto the work, and pushed the orders out the door. It worked. The orders shipped.

This week, in our quarterly review, one manager put words to the cost: going in every day at 150% is not sustainable.

He was right. And if you run an established business, you have probably felt the same thing from the other side of the table.

Why heroics feel like leadership

Heroic effort is rewarding. It's visible. It produces a clear win and a good story. When you, or one of your best people, swoop in and save the week, it feels like proof the business is in good hands.

But look at what a rescue actually tells you. The normal way of doing the work didn't get it done. Something in the process, the priorities, or the handoffs broke, and a person had to absorb the gap with extra hours and extra stress.

One rescue is fine. A business that needs a rescue every month has made heroics its operating model. And the people doing the rescuing are usually the ones you can least afford to burn out. Often, that includes you.

Ask for the number

In that same review, we ran a simple check. Each leader rated their stress on a scale of 0 to 10. Zero is calm. Ten is "get me out of here."

The answers ranged from about three and a half to eight.

Then we asked the people at the top of the range a follow-up question: what would need to be true to bring your number down a couple of points?

Nobody said "work less." The answers were specific. Get one stubborn quality problem under control. Get a key process into a steady flow instead of keeping it alive by force. Carry fewer than thirty open items instead of what I'm carrying now.

That's the value of asking for the number. It turns a vague feeling of overload into a short list of problems you can actually solve. And the leaders who give you the highest numbers usually aren't the weakest. They're the ones carrying the most unfixed problems.

If you've never asked your leadership team this question, ask it this week. Then listen to what comes after the number.

What a little more every day looks like

The alternative to heroics isn't coasting. It's steady, visible progress that doesn't depend on anyone running at 150%. In that review, it looked like a few unglamorous habits.

Put the numbers on the wall every day. The team runs a daily scorecard. In the review, we noticed blanks in it. The fix wasn't a new tool. It was filling it in every day, so the trend is visible as it happens instead of reconstructed after something goes wrong.

Give every open item a date. The team's implementation list started with about 40 items. As problems surfaced, it grew to 105. They have closed more than 70. What's left is the harder 20 percent, the work that takes longer and needs more thought. In the review, every remaining item got a due date. A list without dates is a wish list. A list with dates is a plan you can inspect.

Find the dominoes. Once everything had a date, a pattern showed up. Several items couldn't move until one other decision landed. A single software decision was holding up training, pay plans, and a quality system. Instead of pushing on all of them at once, the team agreed to land the first domino and let the rest wait on purpose. Pushing on everything feels productive. Pushing on the thing that releases the rest actually is.

Make one change at a time, then wait. The team has been fighting a stubborn quality problem. They made a change about a week earlier, and the data will take 60 to 90 days to show whether it worked. The temptation was to stack another fix on top. One leader even caught himself and called his own theory "all feeling and no fact." The team chose to hold steady and watch the data. If you change three things at once and the problem improves, you don't know what worked. If it gets worse, you don't know what to undo.

Separate real urgency from inherited urgency. At one point the team had about 60 orders marked as rush. Someone did the math out loud: that's roughly ten per manager in the room. When everything is urgent, the label stops meaning anything. The proposal was to give each aging rush order one named owner who sees it through. Before doing that, the team decided to first make it visible which rush orders had a customer actually waiting and which were restocking. Urgency is a budget. Spend it on everything and you've spent it on nothing.

None of these habits is impressive on its own. That's the point. Together, they replace the rescue with a rhythm.

Plan for seasons, not a permanent sprint

There will still be times when the business needs more from everyone. A big launch. A busy season. A customer you can't afford to disappoint.

The leadership team didn't pretend otherwise. The way we described it in the room: live at a four. Ramp up to a seven for a season when the work demands it. Then come back down to a four on purpose, so it stays sustainable and nobody is living on heroics.

They went a step further. Even with strong demand ahead, they decided to slow growth next year on purpose, so operations can catch up and hold steady. That isn't a lack of ambition. It's recognizing that growth built on exhausted people is borrowed against the future.

A surge with an end date is a strategy. A surge with no end date is just your culture.

What this asks of you

If you're the owner, you set the standard for what gets celebrated. When the rescue gets the applause and the steady scorecard gets ignored, your team learns which one you actually value.

So try this:

The goal isn't a business that never works hard. It's a business that doesn't need anyone, including you, at 150% to keep its promises.

Build the business. Keep your life.

If your business still runs on rescues, yours or your team's, share what feels stuck. We'll explore the right level of support for your business.