One of my team leads told me, mid-sentence in a coaching call, that they’d almost phoned me on Saturday morning to quit.

It wasn’t delivered as a dramatic reveal. More like an afterthought. Wedged between complaints about team attendance and frustration about back-end code quality. “I was so close to calling you Saturday morning to say I’m done.” Then they kept talking about something else.

This was a Monday. At 9:23 AM that same Monday, before we’d even spoken, they’d already sent a firm, clear attendance policy email to their entire team. No escalation. No draft review from me. No permission slip. They’d identified the problem, set expectations, and pressed send.

The person closest to walking out the door was the same person showing the most ownership I’d seen from them all quarter.

The people closest to quitting

The people closest to quitting are rarely the disengaged ones. They’re the ones who care too deeply about work that feels impossible.

My lead wasn’t frustrated because the job was hard. They were frustrated because they’d tried everything they could think of (coaching, direct conversation, leading by example) and the team still wasn’t listening. “They don’t listen when I talk to them,” they told me. “So they’ll have to learn to read.”

The Monday email wasn’t rage. It was the culmination of months of being ignored and deciding to put it in writing because spoken words weren’t landing.

But the same drive that produced the email is what produced the Saturday morning crisis. The ownership that makes someone draft a policy before 9 AM is the same ownership that keeps them up at 3 AM wondering why nobody else seems to care as much. You can’t have one without the other. And if you’re their manager, you can’t celebrate the Monday without reckoning with the Saturday.

Meanwhile, on another team

The same week (because apparently the universe likes themes), I was in a coaching call with a different lead. Different team, different challenges, same syndrome.

This one was drowning. Not in bad work, in too much of it. Every QA gap caught personally. Every priority deviation corrected in real-time. Every miscommunication between team members mediated, explained, re-explained.

“I feel very tired,” they said. “Too many things in my head and nobody can do the job properly.”

I asked them why they were personally reviewing every piece of work from a particular engineer instead of distributing reviews across the team. They said I’d told them to. I hadn’t. Somewhere between a suggestion and a recollection, they’d constructed an instruction nobody gave and built their entire workweek around it.

I said something I’d been trying to say for months: “You choose to engage with behaviours. That’s your comfort zone. The fact that it makes you miserable doesn’t mean it isn’t comfortable. You keep choosing it.”

They didn’t love hearing that. I wouldn’t have either.

But the pattern was the same. A highly capable lead, investing everything in their team, absorbing every failure as a personal responsibility, and slowly running out of fuel. Not because the job was too big, but because they’d taken on a version of the job that no single person could sustain.

Two leads, one mistake. Mine.

I’d been coaching both these people for months. Teaching them to delegate, to step back, to set constraints instead of methods, to define end states and let their teams find their own path. Standard leadership development stuff. The kind of coaching that looks great in a quarterly review.

And it was working. The first lead had grown more in six months than in the previous two years. They were making decisions independently, pushing back on product pressure, handling difficult conversations with composure. The second lead had built testing practices from nothing, established accountability structures, created real quality culture. Both were objectively better leaders than when we’d started.

So why was one almost quitting and the other burning out?

Because I was only doing half the job.

I was developing their capability without protecting the conditions for it to survive. Building muscle while the gym was on fire.

Development without protection isn’t development. It’s exploitation with a coaching wrapper. You teach someone to take ownership, but you don’t shield them from the organisational dysfunction that punishes ownership. You teach someone to delegate, but you don’t address the culture that makes delegation feel unsafe. You grow their skills while the system around them consumes those skills faster than they can replenish them.

What the other half looks like

A few days before that Monday email, I’d done two things in the same day.

The first was a conversation with the CTO. One of my engineers had been on the receiving end of a behaviour pattern from a senior stakeholder, dismissive feedback in public forums, requests routed around her, credit for her work landing on someone else’s slide. None of it individually firing-line stuff. All of it adding up to the kind of climate where her growing leadership would quietly suffocate.

I walked into that conversation knowing I might lose it. I named the pattern, attributed the specific incidents, and asked for a change in how the stakeholder engaged with her team. There was no agreement. There was a “let’s keep an eye on it.” I left the room not knowing if anything would change, and three weeks later I’m still not sure. That’s the texture of protective work. Nobody applauds. The graph nobody draws goes flat for a quarter and you call that a win.

The second thing, that same afternoon, was enrolling that same engineer in a management training programme. Sent the message to HR, outlined the goals, set the timeline. Constructive. Tangible. The kind of action with a visible artifact.

One felt like a fight. The other felt like progress. The second only works if you keep doing the first.

Within forty-eight hours of being formally given the team lead role, this engineer had completed a plan of attack, run her first daily standup, announced execution to the team, and independently started exploring how the team would use AI tooling in its workflow. Zero direction from me. Months of quiet investment compounding into self-sufficiency.

The difference between her and my two struggling leads wasn’t talent or motivation. All three had those in abundance. The difference was that for her, I’d been doing both halves: developing the capability and protecting the space for it to grow. Hard conversations upward, coaching conversations downward.

For the other two, I’d been mostly teaching.

Getting out of the way only works if the way is clear

I’ve been writing about leadership philosophy for a few weeks now. Constraints, not methods. Define the end state. Get out of the way. Let teams stand on their own feet.

All true. And none of it sufficient.

The lead who almost quit on Saturday had perfectly internalised every piece of coaching I’d given them. Set clear expectations. Document rather than verbalise. Hold people accountable through evidence, not emotion. They’d done all of it. And the result was that they absorbed all the accountability while the system around them continued to produce the problems they were accountable for solving.

I told them: “Focus your energy on the people who listen. Stop trying to squeeze blood from a stone.”

Good advice. Also a confession: I hadn’t done enough to fix the environment that was making blood-from-stone the default mode.

The protective work is less satisfying than the developmental work. Coaching someone through a difficult conversation is rewarding. You see growth in real-time. But having a hard conversation with your own boss to shield a team lead from political pressure? That’s just Tuesday. Nobody notices. The lead doesn’t know the conversation happened. The outcome is the absence of a problem rather than the presence of a win.

Turns out the absence of problems is exactly what leadership development runs on. You can’t grow someone in soil that keeps getting salted.

I’m paying more attention to the soil now. When I coach a lead on delegation, I’m also asking: what in their environment makes delegation feel risky? When I tell someone to step back, I’m asking: have I cleared enough space for stepping back to be safe? And when someone almost quits, I’m not treating it as a crisis to manage. I’m treating it as a signal about which half of my job I’ve been neglecting.

The Saturday morning phone call never came. The Monday morning email did. I’d like to take credit for the email. The honest version is that I nearly caused the phone call. Same act. Same job. Miss either half and you get a resignation written by someone who would have been your best leader.