The commits started coming in at 2:14 AM.

At first, Marcus, a lead backend engineer, looked like he was simply in the zone. He was closing tickets at a record pace, pushing massive refactors, and carrying a critical database migration almost entirely on his shoulders. The corporate dashboard showed green across the board. But his manager, noticed something else entirely. Marcus had stopped arguing.

For two years, Marcus had been the team’s most vocal advocate for clean architecture. He pushed back on bad deadlines, challenged product managers, and debated system designs with a fierce, joyful energy. But suddenly, his pull requests were dead silent. When executives threw impossible, last-minute requirements into the sprint, he didn’t push back or suggest alternatives. He just typed, “On it.”

The manager recognized the signal. It was not the sound of a highly optimized employee; it was the sound of a battery running completely dry. The friction of caring had become too heavy, so Marcus had simply stopped caring in order to survive the workload.

The next morning, he pulled him into an unscheduled one-on-one. He didn’t ask about the migration timeline. He didn’t mention the sprint velocity. He just looked at him and said, “I can see something is going on. How do you feel?”

Marcus immediately panicked. He instinctively started listing the dependencies, the cross-team bottlenecks, and the angry executives expecting a Friday delivery.

The manager just shook his head. “I do not care about the deployment right now. I care about you.”

That single moment of interception fundamentally changed their working dynamic. In a business culture that routinely rewards the dangerous habit of heroic overwork, telling your top performer to stop is a radical act of leadership. The manager didn’t offer a generic wellness seminar or a corporate gift card. He offered the ultimate form of psychological safety: he used his authority to build a shield and a safe space so his engineer could actually open up.

When Marcus returned the following week, the exhaustion wasn’t gone. The silence wasn’t gone, either. You do not undo months of deep corporate burnout with a single long weekend. But a fundamental shift had occurred. Instead of sprinting blindly into the next impossible ticket, Marcus started pacing himself. He stopped working nights. He started talking more to the manager during their check-ins – not just about deployment blockers, but about his actual mental capacity. One afternoon, he even turned on his camera and shared the names of his cats who kept walking across his keyboard.

The trust established in that tiny window – the absolute realization that his manager viewed him as a human being first and a resource second – didn’t instantly fix the heavy workload. But it created a foundation of safety and quiet joy that no salary bump or equity grant could ever buy. True leadership is not about squeezing the last drop of productivity out of your team, and it isn’t about magical Hollywood endings. It is knowing exactly when to tell them to stop, and being there to help them find a sustainable pace when they return.

The situation has improved in 6 months and Marcus was back. But it was a Marcus 2.0. Very effective, but never again overworking.

The choice on what type of a manager you want to be is as per usual – yours.

*The story is based on my own experience, but names and facts were changed.