The Difference Between Knowing What to Do and Being Able to Do It

I knew exactly what I should have said.

I knew it in the moment — the calm, clear, grounded response that was sitting right there, fully formed, somewhere behind the flood of everything I was feeling. I could see it. I could almost reach it.

And then I said something else entirely.

That gap — between knowing and being able — is one I've lived in personally and witnessed professionally more times than I can count. And I've come to believe it is one of the most important and least discussed realities in leadership development.

We are extraordinarily good at teaching people what to do in conflict. The frameworks. The scripts. The communication models with their tidy steps and their color-coded quadrants. And those things have value. I'm not dismissing them.

But here's what I know to be true: knowledge doesn't hold under pressure.

When the stakes feel high, when your character is being questioned, when someone you trusted says something that lands like a betrayal — the thinking brain steps back and something older, faster, and far less articulate takes over. The body responds before the mind decides. And all the frameworks in the world live in the part of you that has just gone temporarily offline.

I remember working with a senior leader — experienced, emotionally intelligent, deeply committed to her team — who had done significant personal development work. She could articulate the principles of nonviolent communication. She understood her own triggers. She had done the reading, the workshops, the coaching.

And then her most trusted team member challenged her vision in front of the executive team. Publicly. With force.

She shut down. Not dramatically. Not obviously. But something closed. Her answers became shorter. Her presence became managed rather than real. She moved through the rest of the meeting like someone navigating a room with the lights slightly dimmed.

Afterward, she said something I've never forgotten.

"I knew what I needed to do. I just couldn't get to it."

That is not a knowledge problem. That is a capacity problem.

Capacity is different from knowledge in a fundamental way. Knowledge is cognitive — it lives in the mind and can be recalled when conditions are safe and calm. Capacity is embodied — it lives in the nervous system, and it is built not through learning but through practice, repetition, and the slow, patient work of rewiring old patterns.

Building capacity means learning to recognize your own signals before they become your responses. The tightening in your chest. The moment your thinking narrows. The subtle shift where you stop being curious and start being defended. It means developing enough self-awareness to catch yourself mid-pattern — not always, not perfectly, but more often than before.

It means being willing to be a beginner again, long after you thought you'd graduated from that.

The leaders who move most powerfully through conflict are not the ones who know the most. They are the ones who have done the interior work of bringing their knowledge and their nervous system into alignment. Who have practiced being present under pressure — not in a workshop simulation, but in the actual messy, high-stakes, relationship-on-the-line moments that leadership really holds.

That alignment is not a destination. It is a practice.

And it begins with the humility to acknowledge that knowing what to do has never been the hard part.

Being able to do it — when it matters most, with the most at stake — that is where the real work lives