At 5:29 on a Monday morning, while I was off the grid, one of my leads sent the most significant email of his career. Not to me. To a peer who’d behaved unprofessionally during a feature demo. Formal. Written. Documented. Clear. He named the behaviour, explained the standard, and asked for a written follow-up.

I didn’t see it until Tuesday. By then, two other leads had independently done the most mature leadership work I’d seen from any of them all quarter. None of them had needed me. The only thing that connected those three moments was that I wasn’t there.

I’ve been sitting with that for two weeks now, and I think it changes how I understand my job.

The Monday I didn’t show up

The day off wasn’t strategic. I just needed a break. Declined every meeting, closed Slack, went fully dark. I’d been telling myself for months that my teams could run without me. I was about to find out whether I believed it.

The lead who sent the 5:29am email had, three weeks earlier, been on the edge of quitting. He’d vented to me at six one morning about a team that wouldn’t listen, frustrations and exhaustion in equal measure. The work I’d been doing with him for months was very obviously developmental: how to have hard conversations, how to escalate without burning bridges, how to write things down rather than carry them in his head.

On the Monday I wasn’t there, he crossed a line I’d been waiting months to see him cross. Not management (knowing what’s broken). Leadership (saying it out loud and committing publicly to fix it).

Meanwhile, on a completely different team, one of my engineers, not even a lead, posted a customer discovery write-up that did the kind of work I’d usually expect from a principal. He’d structured the customer feedback by priority, mapped requirements to retention risk, and proposed an early-versus-later scope split. He did this while handling a family emergency. No direction from me. No prompt. No template. He just saw work that needed doing and did it at a level nobody had asked for.

A few days later, a third lead, the one who manages QA across one of my teams, sent a formal email to her reports. She opened with: “I want to be direct: I’m responsible for part of this.” A team lead, in writing, publicly naming her own contribution to the problems before asking her team to change. Not “we need to do better.” Not “I’ve noticed some patterns.” She said “I’m responsible” first.

Three leads. Three teams. Three independent moments of leadership maturity. Same week. The only thing they had in common was that I wasn’t in the room.

Something was going on.

The uncomfortable hypothesis

When I’m in the room (or in the Slack channel, or on the calendar), my leads know there’s a backstop. If the conversation goes sideways, I’ll help. If the decision is wrong, I’ll course-correct. The safety is real, and I spent months building it.

But safety has a side effect. When the backstop is always there, people lean on it. Not consciously. Not lazily. Just naturally, the same way you drive differently when the road has guardrails.

My absence removed the guardrails. And instead of driving off the cliff, my leads drove more carefully — the consequences were suddenly theirs. The most mature leadership email of one lead’s career was sent at 5:29am on a day he knew I wouldn’t see it until later. The QA lead’s accountability email was CC’d to me but not written for me. The engineer’s product write-up was posted in a channel I wasn’t monitoring.

My presence gives safety. My absence gives permission.

The counterexample that proves it

If the story ended there, it would be too clean. A neat parable about letting go. The kind of thing that fits on a LinkedIn post.

The same week, the same team whose lead sent that powerful 5:29am email was dealing with an attendance crisis. People not showing up to the office. A team that can run its technical governance without its director still can’t self-organise on basic attendance norms. Autonomy without reliability is one dimension of maturity, not maturity itself.

And on another team, an intern said something in a retro that stopped the room. “I look at us and I don’t feel like we’re a team. Everyone works on different things. People feel like strangers.”

That took real courage. The team that hasn’t passed the absence test yet produced the most honest self-assessment of all three. Sometimes the team that names its own failure is further along than the team that doesn’t notice.

The pattern underneath the pattern

I’ve been coaching my leads for months on the same principle: constraints, not methods. Define the end state, shut up about the path. But I’d been applying it inconsistently. I defined the end state for the work. I was still showing up to manage the path for the people.

Every weekly 1:1 where I coached a lead through a difficult conversation was also a weekly signal that they needed coaching to have difficult conversations. Every time I modelled the right response to a tricky stakeholder was a demonstration that the right response needed modelling.

The method that finally worked was not coaching harder. It was disappearing for a Monday.

What I’ve changed

What follows is the LinkedIn-shaped part I gestured at earlier. Three concrete changes. Forgive me; they’re the part I actually have evidence for.

One: I’ve started declining meetings I used to attend “just in case.” In the last three weeks I’ve declined eleven of them. Nine were genuinely fine without me. Two surfaced gaps I now know about, things I’d been quietly papering over by being in the room. Both are now on a list to actually fix, instead of permanently absorbed by my calendar.

Two: I’ve stretched the gap between 1:1s with my most senior lead from weekly to fortnightly. The accountability bar went up, not down. We agreed in advance what would be different at the next session. Two cycles in, the conversation has more in it. Less status update, more genuine reflection. The space between sessions is where the independent decisions happen.

Three: I’m watching what happens during my absences more carefully than what happens during my presence. The signals that matter aren’t in the meetings I attend. They’re in the Slack messages sent at 5:29am when nobody’s watching.

The thing I still can’t quite accept

I’ve been managing people for years. My stated goal this quarter is to help my teams stand on their own feet. Every post I’ve written this year circles back to some version of: let go, step back, trust the system.

And yet. Every instinct I have still says be there. Be available. Be the backstop. The gap between knowing you should step back and actually doing it turns out to be approximately the width of a Monday.

I’m not going to pretend I’ve cracked this. I still jump into Slack threads I should ignore. I still schedule coaching sessions for people who are past the point of needing them. I still have an involuntary physical reaction when I see a team decision I would have made differently.

But that Monday keeps replaying. Three leads, three independent acts of leadership courage, and the only common thread was my absence.

Your presence gives safety. Your absence gives permission. The answer, I suspect, is more permission than you’re comfortable with.