TL;DR
Active listening is not enough. This episode argues that the most damaging leadership failure in organizations today has nothing to do with strategy, vision, or even communication. It is the gap between what a leader hears and what a leader actually does. When numbers are good, that gap stays invisible. When numbers turn, everything hidden inside them is exposed at once — and the organization’s default response makes everything worse. This episode is for the leader who wants to go beyond the dashboard and for the one who has the courage to treat a team’s silence not as compliance but as data.
I want to start today with a question, and I want you to sit with it before you answer.
When was the last time your numbers were really good, and someone above you pushed back on how you were leading?
Take a second. Think about it.
If you’re like most leaders I know, the honest answer is: never. When the numbers are good, nobody looks underneath them. The quarterly review is a celebration. The one-on-ones are shorter. The emails from leadership are warmer. Everyone is happy, and you get left alone to keep doing whatever you’ve been doing.
And that, right there, is the most dangerous place a leader can be.
ACT ONE: The Gap That Hides in Plain Sight
We’ve talked on this show before about active listening. And I want to be clear about something before we go any further today, because I know some of you have been with me since the early episodes.
Active listening is real. It matters. The ability to be fully present, to hear beyond the words, to understand the emotions and context underneath what someone is actually saying — that is a genuine leadership skill. I believe that. I’ve built episodes around it. I stand by every word.
But here’s what I haven’t said yet.
Active listening is an input skill. And inputs without outputs are just performance.
You can be the most engaged, present, empathetic listener in your organization. You can nod. You can take notes. You can repeat back what you heard with genuine warmth and make every person on your team feel completely seen in the moment. And if you walk out of that conversation and do absolutely nothing with what you just heard, you have not led anyone. You have performed leadership. And there is a meaningful difference between the two.
That gap, the space between what a leader hears and what a leader actually executes on, is what I’m calling the execution gap. And I want to make the case today that it is one of the most widespread, most costly, and most invisible failures in organizational leadership. Invisible, specifically, because of one thing.
The numbers.
ACT TWO: What Strong Numbers Actually Hide
I want to tell you about a leader I worked for. I’m going to call him John, and I want to be clear up front: I respect this person. Genuinely. What he was great at, he was extraordinary at.
John had a gift for making a team feel like a team. Not in a manufactured way. Not with forced fun or mandatory team building exercises. He just had this quality where you felt, when you were around him, that everyone in the room mattered and that you were all rowing in the same direction. That is rare. That is actually a form of leadership that most people never develop.
And the numbers reflected it. Our numbers were strong. Consistently strong. And when the numbers are consistently strong, a particular thing happens inside an organization. Leadership above you stops looking closely. They stop asking hard questions. They leave you alone. Because why would you mess with something that’s working?
Here’s what was also true at the same time. Operational gaps were accumulating. Technology that needed updating wasn’t getting updated. Process failures that team members had flagged in conversations — real conversations, real feedback — were being heard, nodded at, appreciated, and then nothing happened. Not out of malice. Not out of indifference. But because when everything looks fine on the scoreboard, there is very little urgency to fix what’s underneath it. Nobody’s complaining loudly. Numbers are good. Let’s not jinx it.
And then a reorganization happened. John was moved out of the leadership seat. And what became apparent almost immediately was that the team cohesion that had felt so organic, so genuinely built, had been doing a second job nobody realized. It was covering the operational gaps. When the cohesion went, so did the cover. And everything that had been accumulating underneath was suddenly visible.
I am not telling this story to diminish John. I’m telling it because I have watched this exact pattern play out more than once in my career. The details change. The industry changes. The leader changes. The pattern does not.
Strong numbers are the most effective camouflage an organization has ever invented. And most of us don’t realize we’re hiding behind them until the camouflage disappears.
ACT THREE: The Default Response and Why It Fails
So the numbers turn. Maybe it’s the market. Maybe it’s a client loss. Maybe it’s just a run of bad timing, the kind of thing that has nothing at all to do with the leader’s competency or effort. Doesn’t matter. The moment the numbers go south, something happens above the leader that is as predictable as sunrise.
The metrics come out.
I experienced this firsthand in 2005. I had made the transition from practicing law in New Jersey to what I thought would be the business side of the legal world. We had moved to Charlotte. I had a brief stint at a legal recruiting firm, and I had a manager there whose entire leadership philosophy, as best I could tell, could be summarized in three sentences.
Believe in the numbers.
If you’re not making me money, I’m not talking to you.
If it’s not in the CRM, it never happened.
That was it. That was the playbook. And when things were going well, those sentences were background noise. But the moment a week went sideways, out came the tracking. How many calls did you make? How many presentations did you have? How many meetings did you schedule? How many opportunities are on the board?
I still think about that manager. A former colleague and I still occasionally laugh about him, because it was genuinely that absurd. And yet, 21 years later, I can tell you with complete confidence that this approach has not gone anywhere. I have seen versions of it in law firms, in technology companies, in professional services organizations, in every sector I have worked in or consulted for. When the numbers go bad, we default to the assembly line.
How many tickets did you open? How many did you close? What is your efficiency rate?
We treat human beings like robots. And then we are surprised when morale goes further south. And when morale goes further south, we lose people. And when we start losing people, the numbers get worse. And when the numbers get worse, the surveillance tightens. And the cycle continues until there is nothing left to lose.
Here’s the question I keep coming back to.
When a server goes offline, when software fails, when a system breaks down, we do not respond by counting how many times the server was turned on and off. We do a root cause analysis. We trace the failure back to its origin. We ask what actually went wrong, not how many things happened. We treat the problem as something worth understanding before we try to fix it.
Why don’t we do that with people?
Why, when a team’s performance dips, do we not ask the same question we would ask about any other system we care about? What is the root cause? What was already present before the numbers turned that we simply weren’t paying attention to because we didn’t have to?
The answer, most of the time, is sitting in a conversation that already happened. Something a team member said six months ago that got heard, acknowledged, and never acted on. Something that went into the execution gap and stayed there.
ACT FOUR: Make Room for the Leader Who Goes Deeper
I want to talk about a different kind of leader for a minute. Because they exist. I have met them. I have tried to be one, with varying degrees of success depending on the season I was in.
This is the leader who, when the numbers turn, does not reach for the activity report. This is the leader who goes another level deeper. Who asks the line manager to actually sit with the individual contributor. Not to audit them. To understand them.
Is there something personal going on that we can create some flexibility around? Is there a technical gap we haven’t identified that we have the ability to close? Is there a skill that needs development that has somehow been masked by team performance or good fortune? Is the sales rep uncomfortable with a part of the pitch we haven’t looked at in two years? Is the associate attorney not getting to the right questions with prospective clients because nobody has coached them on how to handle objections in a legal technology conversation?
These are not soft questions. They are diagnostic questions. And the leader who asks them is doing exactly what a good engineer does when a system fails. They are tracing the problem back to its origin before they start applying fixes.
This kind of leader makes a lot of organizations uncomfortable, by the way. Because this approach requires patience. It requires sitting with uncertainty for a little longer than the dashboard allows. It requires the belief that the human beings on your team are worth the same kind of rigorous, careful analysis we give to our technology and our financial models.
I have been in rooms where that belief was not shared. Where the message, spoken or unspoken, was: the numbers tell us what we need to know, and everything else is noise. I understand why organizations end up there. The metrics are clean. The metrics are comparable. The metrics don’t require you to sit in an uncomfortable conversation with a person who is struggling.
But the metrics also do not tell you why. And why is the only question that actually fixes anything.
THE CLOSE
Here is what I want you to take away from today.
Active listening matters. Keep doing it. Keep developing it. Keep teaching it to the people around you. But do not confuse listening with leading. Listening is the input. Execution is the output. And the gap between them is where trust either grows or dies.
When your numbers are good, that is exactly the moment to look underneath them. Not because something is wrong, but because that is when you have the clarity and the space to see clearly. That is when the hard conversations are still manageable. That is when the operational gaps are still fixable. Do not wait for the camouflage to disappear before you start asking the real questions.
And when things turn, resist the default. Resist the assembly line response. Before you pull out the activity report, ask the root cause question. Treat your team with the same intellectual rigor you would apply to any system you actually want to understand.
Make room for the leader who thinks differently. And if you are that leader, stay in the room. The organizations that survive the next decade will be the ones that figured out the difference between counting activity and understanding people.
KEY TAKEAWAYS
Active listening is an input skill. Without execution on the other end, it is theater. The measure of whether a leader actually heard something is not the quality of the conversation. It is what happened in the 24 hours after it.
Strong numbers are the most effective camouflage in any organization. They protect the leader from scrutiny, mask accumulating operational failures, and create a false signal that everything is working. The execution gap grows fastest when the scoreboard looks best.
The default response to declining performance almost always makes things worse. Activity metrics, increased reporting, and tighter surveillance treat the symptom and ignore the disease. They also accelerate attrition among the people most capable of leaving.
Root cause analysis is not just for systems. When a team’s performance drops, the instinct to count outputs is the wrong instinct. The right instinct is to trace the failure back to its origin. The answer is almost always in a conversation that already happened and a follow-through that never did.
Make room for the leader who goes deeper. The diagnostic leader, the one who asks why before asking how many, is the one who builds teams that are durable rather than just temporarily productive. That kind of leadership is uncomfortable for organizations trained on dashboards. Do it anyway.
