A founder feels the company on the line in their body. Cash is tight, a make-or-break deal is live, a launch has to land, and it sits in their chest at three in the morning. Then they look at the team, and the team is working a normal week, and the gap is infuriating. Why can they not see that this is the moment. Why is nobody else running.
The instinct is to blame the team, to decide they do not care enough or hustle enough. That instinct is almost always wrong, and acting on it makes everything worse. If your team does not know when it is time to push, the most likely reason is not that they are lazy. It is that nobody ever made the moment legible to them, and you cannot expect people to respond to a signal they were never given. The gap is real and it is dangerous. It is also mostly yours to close.
The stakes are not automatically legible
The founder feels the stakes because it is their company, their name, their risk, and their upside. That feeling is not transferable by default. Your team did not sign up for the same bet, does not have the same information, and does not lie awake with the same fear, and none of that makes them uncommitted. It makes them employees, which is what you hired.
So the surge you are silently hoping for does not come, because from where they sit nothing looks different from any other week. They are not in the deal calls. They do not see the cash position. They hear a general sense that things are busy, which is how it always feels, and they have no way to know that this week is the one that actually matters. You are reading a situation they cannot see, and then resenting them for not reacting to it.
The fix starts with making the stakes real and specific instead of assuming they are felt. Say the actual thing. Here is what is happening, here is what is at risk, here is why this one is different, here is what we have to do and by when. People will step up for real, named stakes they understand far more often than founders expect. What they cannot do is rise to a crisis you kept to yourself.
If everything is urgent, nothing is
There is a second reason the team does not react, and this one is entirely self-inflicted. If you run the company at red alert all the time, you have taught everyone that red alert means nothing.
A leader who treats every week as do-or-die, every deadline as existential, and every request as an emergency spends the alarm until it is worthless. The team learns, correctly, that the urgency is just your normal volume, and they tune it out to survive, because nobody can sprint continuously. Then a week arrives when the company genuinely is on the line, you sound the alarm, and it lands exactly like all the false ones did. You cannot understand why they are not responding. They are not responding because you trained them not to.
Urgency is a signal, and a signal only works if it is rare. The leaders whose teams surge when it counts are almost always the ones who do not manufacture urgency the rest of the time. They keep a calm, sustainable baseline precisely so that when they say this one is real, the words still carry weight. Protecting the alarm is a discipline, and you protect it by not pulling it for things that are not fires.
A real call to push is named, bounded, and shared
When the moment is genuine, there is a way to ask for the surge that works, and it has three parts, none of which are just working people harder.
You name it. You say plainly that this is real, what is at stake, and why this is different from a normal stretch, so people are responding to information and not to your mood. You bound it. A surge has a defined shape and a defined end: this is what we need, and it lasts until this milestone, not forever, because open-ended hustle is not a surge, it is just a worse permanent baseline that people will refuse or break under. And you share it. You are visibly in it with them, taking the hardest parts, present rather than issuing the push from a distance. Nothing kills a call to hustle faster than a leader demanding a sprint they are not running themselves.
Do those three things and most teams will show up in a way that surprises you. People will give a great deal for something real, finite, and led from the front. What they will not give, and should not, is indefinite grind for a crisis they cannot see, called by someone who is not in it with them.
This is not grind culture, and the difference matters
None of this contradicts the truth that a team run at maximum forever burns out and breaks. It depends on it. The ability to surge is a resource, and you bank that resource by not spending it in normal times. A team already running on empty has no sprint left in them when you finally need it, so the sustainable baseline is not the opposite of being able to hustle. It is what makes hustle possible.
The distinction is between the rare, real, bounded surge and the permanent expectation of overwork, and teams can tell the two apart even when leaders pretend they are the same. A genuine all-hands moment, named honestly and ended cleanly, can even bring a team closer, because they went through something real together and came out the other side. The same hours demanded as a constant, with no end and no shared stakes, just corrodes people until the good ones leave. If you want a team that can push when the company is on the line, the most important work happens in all the weeks when it is not, by protecting them enough that they have something left to give.
When they still do not step up
Suppose you have done all of it. You made the stakes legible, you did not cry wolf, you named and bounded the surge, and you led from the front. And someone still will not engage when the company genuinely needs it. That is real information, and now you can trust it, because you have ruled out the reasons that would have been yours.
Handle it the way you handle any performance signal: honestly and specifically, in a real conversation, not by broadcasting resentment at the whole team for one or two people. Sometimes it is a misunderstanding that survived even your clarity, and a direct conversation fixes it. Sometimes it is a values or fit mismatch that a moment of real stakes has simply revealed, and that is worth knowing, because who shows up when it counts is data you cannot get any other way. But you only earn the right to that conclusion after you have genuinely closed the gap from your side. A leader who skips straight to blaming the team has learned nothing and will have the same problem with the next team, because the constant in that equation is not the people.
Where to start
Ready to find out whether your team cannot rise when it counts or has simply never been shown when it counts, and what it would take to close that gap before the moment that decides everything? The Forge Assessment is the 30-day diagnostic that maps how urgency, stakes, and commitment actually move through your organization. $6,500. A ranked 90-day roadmap at the end. Book a discovery call →
Jason Bonito is the founder of Crucible76, a fractional operating partner practice helping scaling businesses find and remove the self-inflicted friction before someone else does. DATA · DECISIONS · GROWTH.
