Emotional Acuity: The Leadership Capability Most VPs Never Learned

Published August 5, 2026

Touch a hot stove and your hand moves before you've decided anything. Pain is a signal, and your body reads it instantly, no permission needed. Emotional acuity is what happens when a leader learns to treat their own feelings the same way — information arriving in real time, worth reading before you react to it. Most leaders never make that switch. They feel the heat and either push through it or lash out, and either way the signal gets thrown away instead of used.

That's a private cost when you're leading a team of five. At the VP level, it stops being private. You're carrying blindspots you can't fully see from where you sit — patterns in how you communicate that are quietly working on the people around you, maybe on your life outside work too. And the job itself has already changed by the time you reach that seat: it's optimizing the humans running the systems.

This is where the stakes get real for a VP specifically. You're removed from the day-to-day work by design, which means you depend on directors and managers to tell you what's actually happening underneath the numbers. A status report can say green and still be hiding something. Reading between those lines is what emotional acuity gives a VP. It functions as a risk-mitigation tool as much as a people-skill: miss it, and dysfunction gets room to sit underneath a green status report until it costs you something you can't get back.

The same read runs in the other direction too. In my experience, a leader's emotional state sets the weather for everyone below them, and at VP altitude that's an org of a hundred-plus people breathing whatever you're putting out. A single dismissive comment, thrown off without realizing its weight, can shut down cross-functional collaboration for far longer than the moment it took to say it. The leaders who catch it in themselves before it lands are doing culture work in the moment it matters most.

At VP scale, psychological safety shows up as specific engineering symptoms: design-review gridlock, or an edge-case warning that never gets raised because nobody felt safe raising it. The same dynamic decides who wants to work for you: the engineers worth keeping have options, and they gravitate toward leaders who make them feel seen and safe to do good work — a pull that works on its own, without having to win purely on salary.

That same read extends into planning. A leader who can sense how motivated a team actually is, and how much they're already carrying, walks into a planning meeting with something closer to the truth than a guess. Commitments built on a false read of capacity are hopes wearing a deadline.

I know the failure mode this creates because I've lived it. I've had stretches where I could feel an emotion working on me without understanding where it was coming from or what was actually bothering me. That kind of unclarity is frustrating on its own, and it makes it hard to let anything go. When you can't trace an effect back to its source, you can't do much with it except carry it around.

That same imprecision shows up at the vocabulary level, and it's worth fixing regardless of altitude. Most of us stop at two words for what we're feeling: mad or sad. That's not enough resolution for a VP trying to read a room, let alone a director trying to read themselves. Annoyed and frustrated are different signals asking for different responses, and a leader who can't tell them apart is flying on one instrument. Brené Brown's Atlas of the Heart is where I point people who want to build that vocabulary — it names the emotion behind the emotion, which is most of the work.

It also extends outward, to the people reporting to you. Leaders with real emotional acuity read past their own intent: they notice tone and what's left unsaid, and they take responsibility for how something actually landed when it doesn't match what they meant. The leader who defends their intent misses the signal. The one who checks the impact gets the information needed to repair it.

I've watched this play out from the coaching seat more than once, always some version of the same story. Someone is frustrated in a role. The leader never picks up that something is off. Then the resignation lands, and it catches the leader completely off guard. The surprise is the tell — the signal was almost always there before the resignation showed up, the leader just wasn't reading for it.

Building this runs through a practice ladder, and it starts wherever you're weakest. If your vocabulary is thin, start there: Atlas of the Heart is a good first stop, because you can't name a signal you don't have a word for yet. From there it's reflection or meditation, anything that creates a beat of space between feeling something and reacting to it; a structured mental-fitness practice can do the same work if journaling alone isn't enough scaffolding. Then it moves into live practice: naming the emotion out loud as it happens, closing the gap between the feeling and your response a little more each time. A practice partner helps: someone you trust enough to ask how something landed, and believe the answer. And when a pattern is genuinely hard to shift alone, a therapist or a coach can walk you through it directly, replaying a past example and rehearsing a specific trigger you know is coming until the response changes before the trigger does.

Maybe a resignation caught you by surprise when you looked back at the signs, or you've sensed a project was in worse shape than anyone was saying out loud. If either one sounds familiar, I'd like to hear what it looks like from where you sit: https://clients.agile-ideation.com/public/fit-conversation

Back to Field Notes