The session on responsive vs reactive zones was the one I came in most curious about, because the practice it points at — noticing how you show up before the team has to absorb the version that walked into the room — is one I’ve been deliberate about since day one of this role.
The frame is simple: under pressure, leaders default to a reactive pattern. There are a few common ones, and the leader’s craft is noticing the early signal — the moment before you slide — and choosing differently. I’ve been doing that work, mostly because eighteen years on the engineering side gave me a long memory of what it feels like when a manager doesn’t.
What the session added wasn’t the awareness. It was a sharper map of the three defaults and a more honest vocabulary for the early signals.
The map
| Reactive default | What it looks like in a leader | The responsive shift |
|---|---|---|
| Anxious → micromanage | Asking for status more often, rewriting things “to help”, small-decisioning into the work | Pause. Say the anxiety out loud. Trust the next checkpoint. |
| Overloaded → withdraw | Slow reply times, vague messages, postponing the one-on-one that needs to happen | Pause. Send the half-formed message. Pick the conversation back up explicitly. |
| Defensive → dismiss | Hearing a critique and immediately explaining why it isn’t really a problem | Pause. Repeat back what I heard before responding. Sit with it for ten minutes before deciding it’s wrong. |
I’ve worked under managers who lived in each of these defaults, and I remember exactly how each one felt from the team side. The micromanage default makes you smaller. The withdraw default makes you stranded. The dismiss default makes you stop bringing things. I built my own practice around avoiding all three, and the session gave me a way to talk about why.
What I watch for in myself
The honest part is that avoiding a reactive default isn’t the same as being immune to it. The defaults are pulls. Every leader feels them. The work is noticing the pull early enough that you have a choice about what happens next.
Anxious-into-micromanage has a specific opening signal in me: a low background hum of “I don’t know what’s happening here”. When I haven’t seen the progress, haven’t reviewed a recent design, am not sure whether the risk I flagged last week was actually picked up — that’s the moment. The reactive version would be to start asking for status on smaller and smaller pieces. The responsive shift, the one I’ve been practising, is to admit the hum: I haven’t been close to this work in a week and I need a re-ground. That’s a five-minute conversation and the rest of the week stays calm. I do this most weeks. It’s not glamorous. It works.
Overloaded-into-withdraw is the one I’m most vigilant about, because the cost of getting it wrong is the part of my practice I most value: being available. The opening signal is when I start triaging time-of-day; if I’m choosing what to do based on how much energy it takes rather than what it matters to, I’m at the edge of withdrawing. The responsive shift is brutal but it works: send the half-formed message that says I’m underwater and I owe you an answer by Thursday — and write it down so I don’t miss it. The signal I’m sending to the team in that move is the one I most want them to keep: you have access to me, even when I’m overloaded.
Defensive-into-dismiss is the most painful to write about, because the people who care most about truth are the ones primed to defend their version of it. The opening signal is internal — a tightness in the chest, a faster reply forming, a “yes, but” — and by the time it’s on my face it’s already in the room. The responsive shift, the one I practise hardest, is to delay the response. Say back what I think I heard. Sit with it for a beat. Even the act of repeating it back changes whether I’m hearing it as an attack or as data. I’ve had this practice for a long time, and I still need it.
What it costs the team when a leader misses
I want to spell out the team cost, because the personal cost is easy to talk about and the team cost is what matters.
Micromanaging shrinks the autonomy of the people the team most needs to be autonomous. Even a brief stretch of it leaves a residue — a small reduction in willingness to push for things without asking. That residue compounds across people and weeks, and by the time anyone notices the team’s velocity has dropped, the root cause is six conversations ago. I’ve watched this from the engineering side under a manager who didn’t know he was doing it, and the team I was on shrank slowly for a year before he was moved.
Withdrawal under load is worse, because it looks like nothing. From the team’s perspective, the leader just got quieter. The work that depends on the leader’s decision doesn’t move. The person who needed the one-on-one wonders if they’re in trouble. The peer the leader is supposed to be aligning with starts making decisions without them, and now there’s a misalignment to clean up later. None of that is in any post-mortem; all of it is in the quiet inefficiency of the next quarter.
Dismissing critique, even unintentionally, teaches the team to stop bringing critique. That is the single most expensive thing a leader can teach. Once it’s been taught, the early signals stop appearing and the leader loses the ability to lead responsively, because responsiveness requires information and the information stops flowing.
The practice I run
The practice — the thing I’ve been doing for the better part of two years now, that the session sharpened — is to know my defaults well enough to feel them before they fire. The small interventions:
A walking five minutes between back-to-back meetings, especially the ones I’m dreading.
A note at the top of my journal listing the three defaults and a single one-word check next to each, updated weekly.
A standing question at the end of every one-on-one: is there anything you wanted to say this week that you didn’t? That last one is humbling to ask and it’s the only way I get the data that tells me which default cost something this week. My team has answered honestly every time, which is itself a sign that the practice is working.
What the session added to all this
Three things, all genuinely useful.
The reactive-zones names. I had been thinking of these defaults as patterns to avoid; now I have shorter labels for them. Shorter labels make for faster catches.
Permission to talk about this with my team. I’d been doing this work quietly. The session made me realise it might be useful to name my defaults to the people who work with me — to tell them: when I start asking for status more often than usual, that’s anxiety, and the right read is to push back, not comply. That conversation is on my list for next week.
A reminder that this never stops being work. The pull doesn’t go away with practice. I’m two years into vigilance about this and the pulls are still there, in the same shape. The session named that, plainly, in a way that made me feel less self-critical about the work being constant. The work is constant. That’s not a failure of leadership. It’s the substance of it.
The team-effectiveness piece
A team led by a leader who notices their reactive pulls early stays expansive. The autonomy stays intact. The information keeps flowing. The hard conversations get had. Everyone on the team can feel a leader who shows up the same way most of the time, even under pressure — and that consistency itself is a form of trust the team builds on.
The closer the version of me that walks into the room is to the version of me I want to be, the better my team works. That’s not a metaphor. It’s the throughput equation. I’m not going to be perfect at it. I’m going to be better at it than I would have been without the practice — and the session made the practice sharper.
That’s the test of a good training, I think. It made me better at a thing I was already trying to do.