The session that moved me most this week was the 2×2 quadrant — engagement on one axis, capability on the other. Not because the model was unfamiliar, but because it formalised something I’ve been doing every week since I took this EM role: a quiet, running read of where each person on my team is sitting at any given moment.
I want to be specific about that practice, because the gift of the quadrant for me wasn’t a new behaviour. It was a way to think more clearly about a behaviour I’d already been building, and — more importantly — a way to hand the same lens to my engineers.
The map
| Zone | Engagement | Capability | What the person needs |
|---|---|---|---|
| Embarking | High | Low | Coaching, guidance, time to grow |
| Flourishing | High | High | Trust, autonomy, room to run |
| Dissatisfied | Low | High | Honest conversation about why |
| Disengaged | Low | Low | Courageous, compassionate truth-telling |
The map isn’t the point. The point is that each quadrant asks for a different conversation, and reading the wrong quadrant means giving someone the wrong conversation. That’s where the cost lives.
The four conversations, the way I’ve come to hold them
Embarking is where I spend a lot of my coaching attention, and where I love being a manager. These are people who want to be excellent at something they’re not yet excellent at. The move that works isn’t to step in and do it for them — it’s to scaffold the next hard thing, walk through the first messy attempt with them, and then step back early enough that they get to feel the win. I do a lot of this. I learned to do it watching a manager I worked under as an engineer who built people that way, and I’ve been deliberately copying the move.
Flourishing is where I’m careful not to confuse autonomy for absence. Flourishing people don’t need direction; they need room plus a leader who is still paying attention so that the room doesn’t drift into isolation. My one-on-ones with people in this zone are shorter and less frequent than the rest, but they’re not skipped, and they’re not transactional. The conversation tends to be about strategy, growth, where the next stretch is. The signal I’m watching for is the quiet shift from flourishing into dissatisfied, which is easy to miss if you’re not close.
Dissatisfied is the quadrant the close-attention practice was built for. Capability stays intact; output stays fine; the body language stays calm. The shift is internal. The conversation that works is the one I aim to have before someone has fully built the resignation case in their head — what’s the work meaning to you right now? what’s drained out of it? what would put it back in? Because I’m in the team’s rhythm — in their channels, at their stand-ups, in walk-and-talks — I tend to catch the drift earlier than the work shows it. That’s the part of being close that pays off most concretely.
Disengaged is the quadrant where care and honesty have to coexist with the most intention. Capability and engagement have both slipped, and the temptation in either direction — over-helping or writing the person off — is high. The conversation that helps is the one a lot of managers avoid: a clear, compassionate naming of where things are, what I can and can’t do to help, and what the next step looks like. I have these. They’re hard. I’d rather have them than let the team carry an unspoken weight.
What the quadrant added to my practice
I want to be honest about what the framework gave me beyond a label.
A teachable shape. I’d been holding a rolling read of my team in my head — names, recent state, what I think the next conversation needs to be. The quadrant is the version of that I can write down without it feeling like surveillance. More importantly, it’s a version I can teach. When my senior engineers ask me how I think about people on the team, I now have four words to give them instead of a long story.
A check on my own reads. A formal model invites the question am I seeing this right? I’ve started using the quadrant as a self-check: for each person I think is flourishing, what would dissatisfied look like in them specifically, and have I seen any of it? That second pass catches the few cases where I’d been generous with my read.
Sharper language for one-on-ones. “I’m reading you as embarking on this and I want to make sure I’m not crowding the embarking with too much hand-holding — what would help?” is a different conversation than the version I’d have had a month ago. The vocabulary doesn’t replace the relationship; it just gives the relationship a more useful surface to talk about itself on.
Mapping isn’t a label, it’s a moving picture
The single most important thing about the quadrant — and the thing the training was careful to underline — is that it’s a map, not a taxonomy. Real people don’t stay in quadrants. They move. They move because the work changes. They move because their life outside work changes. They move because I’ve been a better or worse leader for them in the last few weeks.
The mapping has to be a habit. Not an annual exercise, not a stage-of-promotion exercise — a quiet running check, every week or two, of where each person actually is. That’s what I’d been doing anyway. The framework just makes the check explicit.
Why this is an effectiveness lever, not an HR exercise
The team-effectiveness case for the quadrant is the case I keep returning to in this series, because it’s the case that matters.
A team in which every person is in the right conversation moves at the right speed for what they’re carrying. The embarking person isn’t being asked to lead a project that will break them. The flourishing person isn’t being micromanaged out of their own judgement. The dissatisfied person isn’t being assumed-fine until they’re gone. The disengaged person isn’t being silently carried because no one has named what’s happening.
Every one of those mismatches is a tax on team throughput. A subtle, accumulating tax that doesn’t show up on any dashboard and shows up everywhere in the work. The quadrant doesn’t make people more capable or more engaged on its own; it makes sure my care is going to the right place, which is most of the work of leading well.
What I’m doing now that’s a little different
I’ve started writing the read down. Not as a performance tool — as a one-page private journal entry I update every couple of weeks. Names, current quadrant, what I think the next conversation is. A few of the managers I worked under as an engineer kept lists like this; I assumed they were doing it for HR. Now I think they were doing it for the same reason I’m doing it now: it keeps the read honest, and it makes sure my attention is going where it’s needed, not where it’s easiest.
That, more than any framework in the training, is what responsive leadership keeps coming down to for me: knowing where each person is right now, so the next conversation we have is the one they actually need.