The distinction that hit me hardest in the session this week was between transformational and responsive leadership. Not because either one was new — I’ve watched managers run on both ends of that spectrum for eighteen years of engineering before I took my own EM role — but because the contrast finally gave me language for the shape I’ve been holding for the last twenty-two months.
The way I lead is built on being close to the team. Not in a checking-up way; in a present way. Close enough that I know what each person is sitting with this week. Close enough that the team brings concerns to me early, often before they fully know what the concern is. Close enough that when I give counsel, it lands, because I already have most of the context. And careful enough — this is the part that takes work — to keep that closeness from sliding into the wrong kind of control.
That’s responsive leadership, more or less. I’d been practising it. The training gave me the name.
What the two ends actually do
Transformational leadership is the leader who lifts a team toward a future state. Vision, narrative, the speech that makes people believe the next quarter matters. It’s the part of leadership that’s easiest to see from the engineering side; the managers I worked under who did this well are the ones I most remember.
Responsive leadership is the leader who senses the present accurately and adapts in real time. Less rallying speech, more careful listening. Less “let me tell you where we’re going”, more “tell me what you’re seeing — what’s harder than it looks?”. It’s quieter work, and you don’t notice it being done well until you compare a team that has it with one that doesn’t.
| Transformational | Responsive |
|---|---|
| Inspires with vision | Leads with presence |
| Drives change | Senses and adapts to change |
| Charisma and storytelling | Active listening and contextual trust |
The framing the training pushed — and the part I want to underline — is that these are complementary, not ranked. A team that only gets transformational is unmoored when the work doesn’t match the narrative. A team that only gets responsive drifts because no one is naming where it’s going. The leader’s craft is reading which one the moment is asking for, and being able to do both.
What I’ve been doing without quite calling it that
I want to be specific about what responsive leadership looks like in my practice, because the abstract version is too easy to nod at.
I stay close on purpose. I’m in the team’s channels, in their work, in the rhythm of their week. Not constantly — that’s the line I work to hold — but reliably. People who want to talk to me don’t have to schedule a meeting; they catch me in a thread, or in a quick walk-and-talk, or at the end of a stand-up. The signal I’m sending, deliberately, is I’m available. That signal is what most of the trust in my team is built on.
I read first, react after. When someone brings me a problem, I want to know what they’re actually carrying before I want to know what to do about it. The first question I ask is usually some version of what’s been going on for you with this? The shape of the answer — long, short, anxious, energised, vague — tells me as much as the content. By the time I’m offering anything, I’ve already adjusted what I’m going to say to what they actually need.
I lead through four things working together. Transparency: I share more context than feels comfortable, including what I haven’t decided. Collaboration: decisions get built with the team, not announced to it. Empathy: I meet each person where they actually are, not where the org chart says they should be. Ownership: I make sure each person feels the work is theirs, and I stand behind them when it is. All four serve the same goal — a team that can carry the work, sustainably, together.
I keep the goal in view: team effectiveness. I want to be very clear about this, because it’s the part too many leaders get wrong. Care isn’t an alternative to results. Care is how you get results, sustainably, from real people doing hard things. A close, well-tended team ships better than a managed-at-arms-length one, and they keep doing it across years rather than quarters. Every move I’ve described above pays off in throughput, not just in morale.
What the training added
Three things, all useful.
A name for the practice. “Responsive leadership” gives me something to point at when I’m trying to explain to my team — or to a peer leader — what I’m trying to do and why. The first time I used the phrase in a one-on-one back at my desk, the person across from me said “yes, that’s the thing you do”. That’s the gift of a good label.
The complementary frame. I’d been quietly suspicious of leaders who pushed transformational as the real leadership. I’m not anymore — I just see them as having chosen the wrong default for most teams most of the time. The framework let me hold both as legitimate, and to notice the moments my team actually needs the transformational version from me (the vision check-in at the start of a quarter, the speech before a hard launch). I do those too, and now I do them deliberately rather than by feel.
Confidence in the model. I’ve been doing this work for less than two years and I’d been quietly checking my approach against every leadership book I could get through. The training was the first time I sat in a room of frameworks designed to teach this and recognised most of what I’d been practising in the names being used. That recognition matters; it’s how I know what to keep building on rather than what to reconsider.
What I’m taking back to my desk
The lens for the rest of this series is going to be honest about how much of each session was new to me versus how much was language for what I already do. Some of it landed as confirmation. Some of it landed as a sharper version of a move I’d been making roughly. A few pieces — the engagement-vs-capability quadrant, the SBID format, the GROW stages — gave me explicit tools I’ll be using on Monday.
The point I want to keep returning to: the team I lead lets me lead them this way because they trust the closeness is genuine. That trust isn’t something the training taught me; it’s the foundation I came in with. What the training did was hand me clearer language to keep building on it.
That’s most of what a good training does. It’s what this one did.