Why Confusing Kindness With Safety Makes Them Hate You

Derek and the Meeting That Ended at 4:47

Picture a man — call him Derek — sitting in a conference room on a Thursday afternoon. The meeting ends at 4:47. Ninety minutes of discussion, wrapped up on schedule, everyone filing out with their laptops under their arms. Within the hour, three of Derek’s seven direct reports are texting each other. Not about the project they just spent an hour and a half discussing. About Derek.

“Same thing, different week.” “He asked me for my opinion then talked over me the moment I started answering.” “I am actively looking. I cannot do another year of this.”

Derek has no idea any of that is happening. In his version of that same meeting, he was decisive. He was engaged. He was clear. He ran a tight ship, and he walked out of that room thinking his team respected him for it. Three of them were updating their LinkedIn profiles before they got home from the office.

Here’s what I want you to sit with before we go any further. Derek is not a villain. He’s not a bully. He has never raised his voice in a meeting in his life. He has never publicly humiliated anyone who works for him, and he genuinely believes in his team’s potential — he tells them so, regularly, and he means it. But there are five specific things Derek does. Five patterns, each one subtle, each one documented in the research, that make the people around him feel chronically unsafe, undervalued, and unheard. And because those people are intelligent adults with options, they are quietly leaving, or quietly checking out while giving Derek exactly enough engagement to keep him comfortably unaware of what’s actually happening around him.

This episode is about those five mistakes. Not the dramatic leadership failures you already know about — the screaming boss, the manager who steals credit, the executive who manipulates people for political advantage. Those failures are obvious, and the people committing them usually know it. What you’re about to hear are the mistakes that good, smart, well-intentioned men make, because they’ve never examined their own patterns with enough honesty to actually see them. If you lead people, some version of this is almost certainly true of you too, and the gap between what you intend and what you actually produce is where your talent quietly walks out the door. It’s where problems stay invisible until they’re catastrophic. It’s where your best ideas never get built, because the people who have them don’t believe it’s safe to bring them to you.

I’m going to give you a framework for closing that gap. I call it the Leadership Audit Protocol, and I want to be honest with you up front: it is not comfortable, and it is not designed to make you feel good about yourself. It’s designed to make you more effective, and the price of that effectiveness is an honest accounting of where your impact diverges from your intent. That divergence is almost always bigger than you think it is. Every leader who has actually done this audit has found gaps they didn’t know existed. And every leader who acted on what the audit revealed has seen it show up in the numbers that matter to you. Your retention improves. The quality of the work improves. Real problems start getting surfaced instead of buried until they explode in your face.

You are going to hear five mistakes in the next few minutes. You will not make all five. Almost nobody does. But you will recognize at least one of them as unmistakably yours, and when you do, I want you to resist the urge to explain it away or soften it into something more comfortable. Let it land. That’s the only way any of what follows actually does you any good. You didn’t come here for reassurance. You came here to see something you’ve been missing about yourself, and that’s exactly what you’re about to get.

Confusing Psychological Safety With Being Nice

Real disagreement only shows up in hallway conversations, never in the meeting itself.
Bad news arrives late, after someone already has a fix ready to hand you.
People ask you fewer clarifying questions than they used to, not more.
Your best ideas increasingly come from you, not from the room.

Let’s start with the first mistake, because it’s the one underneath most of the others. Amy Edmondson is a professor at Harvard Business School, and she has spent decades studying why some teams perform dramatically better than others. Her most important finding overturns the thing you probably assume, which is that high-performing teams are built mainly through talent, incentives, or strategy. What she found — consistently, across industries, across company sizes, across cultures — is that the single variable most predictive of team performance is psychological safety. That’s the shared belief, inside a team, that it’s a safe place to take an interpersonal risk.

Now, psychological safety is not about being comfortable. It’s not about avoiding conflict, and it’s not about having a pleasant workplace culture. It’s about whether the people around you believe they can raise a concern, challenge an assumption, admit a mistake, or float a counterintuitive idea without being penalized for it, formally or informally. And here’s the part that matters most for you: the penalty doesn’t need to be explicit. It doesn’t need to be a firing or a written reprimand. A flash of visible irritation from you when someone delivers bad news is a penalty. A subtle shift in your tone when someone disagrees with you is a penalty. Assigning blame the moment a risk you took turns out badly is a penalty. Small, subtle, often unintentional penalties like these accumulate into one very clear belief across your team: raising an uncomfortable truth with you costs something. And once people believe that, they stop paying the cost. They stop telling you things.

The mistake most leaders make — and you may be making it right now without knowing it — is treating psychological safety as the same thing as niceness. You’re friendly. You praise people in public. You avoid harsh criticism. And you genuinely cannot understand why, despite all that warmth, people still don’t speak up in meetings. Why the real opinions come out in the hallway conversation after the meeting, not in the room. Why problems get discovered late, when the information about them existed in someone’s head for weeks before it ever reached you. You see a warm climate and you assume it’s a safe one. Those two things are not the same. Safety is the tested belief that raising an uncomfortable truth won’t get you punished, socially or professionally. Warmth is just a general emotional temperature, and it can exist with or without real safety underneath it. Plenty of warm leaders run deeply unsafe teams. The warmth actually makes the problem harder to see, because the surface looks friendly while the real dynamics underneath are quietly shutting down honest communication.

Edmondson’s research on medical teams makes this uncomfortably precise. She found that the best-performing teams reported higher rates of error — more mistakes per patient, more near-misses written up, more problems flagged. That seemed backwards until she looked closer. The best teams weren’t making more errors. They were reporting them. They had the safety to surface a mistake quickly, which meant it could be corrected before it became a disaster. The lower-performing teams had lower reported error rates, not because they made fewer mistakes, but because people didn’t feel safe reporting them. Their errors stayed invisible until they became catastrophic. Think about what that means for you specifically, in whatever room you lead. If it isn’t safe to bring you bad news, you will not receive bad news until it’s already past the point where it can be easily fixed.

Here’s how the account actually gets built, and it’s built through your behavior, not through anything you declare. Every time you respond to unwelcome information with genuine curiosity instead of defensiveness, you make a deposit. Every time you say “thank you for telling me that — tell me more” when someone challenges you, you make a deposit. Every time you punish the messenger, even subtly, even with a flash of irritation that passes in three seconds, you make a withdrawal, and it takes several deposits to repair a single one of those withdrawals. Your team’s actual behavior is driven by that balance, not by what you say you want from them. People respond to your history, not your stated preferences.

So ask yourself something honest right now. In the last ninety days, has anyone on your team told you something you didn’t want to hear? Not a minor scheduling update — a real challenge to one of your assumptions, a flagged problem with your strategy, real pushback on a decision you made. If the answer is no, or if the answer is “almost never,” you don’t actually have a team without problems. You have a team without the safety to tell you about the problems they’ve already found. That silence you’ve mistaken for good news is, in fact, the single most expensive silence in your business.

Before you move on, run a quick check on yourself. These are the signs your own team is already showing you, whether or not you’ve noticed them yet.

If two or more of those are true for you right now, you already have your answer.

Radical Candor’s Dark Side

Kim Scott spent years working inside some of the most demanding companies on earth — Google, Apple — before she built the framework she calls Radical Candor: caring personally while challenging directly. The failure modes she identified out of that experience have become some of the most useful tools in leadership development. I want to walk you through the two most common ones. Understanding both is essential if you want to give feedback that actually produces change in someone, rather than defensiveness, performance, or a resignation letter.

The first and most common failure is what Scott calls ruinous empathy: you care personally, but you fail to challenge directly, and the result is feedback so softened and hedged that it carries no real information. You know the line. “You’re doing great overall, there are just a few small areas to work on” — said to someone whose performance is genuinely unacceptable. That is not kindness on your part. It’s cowardice, dressed up as consideration, and it will eventually be devastating for both of you. The person doesn’t know how serious the problem actually is. You stay frustrated without ever giving them the information that would let them fix it. And the eventual consequence is always worse. The performance review that comes out of nowhere. The restructuring that quietly removes them. The hard conversation that only happens after the project has already failed. All of it is far more painful than the honest conversation you avoided having six months earlier would have been.

But there’s a second failure mode in Scott’s framework that gets talked about far less, and it might be the one that actually describes you: obnoxious aggression. That’s challenging directly without caring personally. It’s delivering accurate feedback in a way that communicates contempt, dismissiveness, or superiority, instead of genuine investment in the other person’s growth. The feedback itself might be completely correct. But the delivery makes it useless, because the person receiving it is now in a defensive, threat-activated state where they can’t actually process the content — they can only respond to the threat. A brain that’s processing a social threat isn’t processing feedback. It’s building a defense. And the accuracy of your critique means nothing to someone who’s busy defending against it. They are not in a state to hear you.

Here’s the uncomfortable part. Plenty of leaders who pride themselves on being direct — who see themselves as people who say what needs to be said and refuse to sugarcoat anything — are operating deep in obnoxious aggression territory without ever recognizing it. The tells are specific, and you should check yourself against them. Feedback delivered in front of others, with no private conversation first. Challenges to someone’s idea that are really evaluations of their intelligence. Repeating feedback you’ve already given, as if saying it more forcefully will somehow change their capacity to act on it. A pattern of always being “right” that makes it socially costly for anyone to disagree with you. A style in meetings that reliably produces visible discomfort in whoever you’re challenging. None of that feels like aggression to you when you’re the one delivering it. It feels like rigor. It feels like standards. It feels like honest communication. But it is experienced as aggression by the people on the other end of it, and their experience is what determines how they behave around you afterward.

The damage this does is subtle, and it compounds. People who work for an obnoxiously aggressive leader stop telling you when you’re wrong, because being wrong in front of someone with a track record of publicly noting wrongness is expensive. They stop bringing you early-stage ideas, because early-stage ideas are underdeveloped by definition, and underdeveloped ideas are easy targets for aggressive criticism. What they develop instead is a performance calibrated to survive your judgment rather than to actually solve the problem in front of them — and those two things are not the same goal. The entire creative and cognitive capacity of your team gets redirected, away from producing excellent outcomes and toward producing defensible ones. In stable, predictable environments, excellent and defensible look a lot alike. In anything that requires real creativity or real risk, they pull apart. And the team you’ve optimized for defensibility will underperform its actual capability in exactly the moments you need that capability most.

Effective directness — the kind that’s genuinely useful to someone, not just cathartic for you to deliver — requires you to actually believe the person receiving it is capable of handling it and worth investing in. That belief has to come through in your tone and your framing. You can’t just assert it afterward and expect it to land. People can tell whether you actually believe in them or whether you’re delivering a verdict, and that difference changes everything about whether they can use what you’re telling them. The exact same factual content, delivered with real investment in someone’s growth versus delivered with contempt for their current limitations, produces two completely different responses in the person hearing it. The content isn’t the variable here.

The relationship carrying the content is the variable.

So which one are you, most days, without noticing? Are you the leader who softens things until they carry no signal, or the one whose accuracy nobody can actually hear because of how you deliver it? Sit with that question honestly before you move on, because most men reading themselves into this episode default hard toward one side or the other, and you almost certainly know, somewhere underneath your own story about yourself, which side is really you.

Victor Chen and the 78 Percent Accuracy Rate

Let me make this concrete for you with another composite — a pattern I’ve seen enough times to give it a name. Call him Victor Chen. Victor had a 78% accuracy rate predicting which projects at his company would succeed and which would fail. His analytical instincts were some of the sharpest in the organization. He was also the leader whose team had the highest turnover rate in the company, three years running. Those two facts are not a coincidence.

Victor’s pattern was consistent, and you may recognize a piece of yourself in it. When someone brought him an idea, he’d analyze it in real time, find its weaknesses within ninety seconds, and raise those weaknesses immediately. He was usually right — the weaknesses were real. But he raised them before asking a single question about what the person had already considered. He raised them before he understood the full context. In a group exit interview, his own team finally put a name to what it felt like from the other side:

“It felt designed to prove you hadn’t thought about it.”

That was never Victor’s intent. It was his impact. And the gap between those two things is what cost him three years of departures.

Here’s what happened as a result. People stopped bringing Victor early-stage ideas altogether. They only brought him ideas that had already been developed far enough to survive his analysis, which meant those ideas had already absorbed a lot of time and energy before anyone showed them to him. Which meant the ideas that could have been redirected early and cheaply were instead developed all the way to the point of high commitment before anyone scrutinized them. Victor wasn’t actually getting better ideas out of this. He was getting later-stage ideas, at a point where the cost of the pivot he usually recommended had gotten much higher. His genuine analytical strength was being deployed in a way that increased the cost of the exact process it was supposed to improve.

More importantly for you to hear: the people with the best early-stage instincts — the ones whose ideas were intuitively strong but not yet fully worked out — stopped bringing them to Victor entirely. They took those ideas to other teams. Other managers. Other companies. Victor’s accuracy was costing him access to exactly the people and the ideas he needed most, and the ones who left weren’t the ones who couldn’t withstand his criticism. They were the ones with better options, and they used them.

So what actually fixed it? Not making Victor less analytical, and not making him less direct. The fix was sequence. Lead with curiosity before you lead with critique. Ask two or three genuine questions before you name a weakness. Let the person find the weaknesses themselves first — they almost always can, if you give them the room — before you raise them. The same analytical content, delivered after genuine engagement with someone’s thinking, gets received as collaborative refinement instead of dismissal. Victor’s accuracy didn’t drop one point when he made this change. His retention rate doubled within eighteen months. He didn’t become a softer thinker. He became a more effective deployer of the rigor he already had, because he stopped deploying it in a way that scared off the exact people he needed bringing him things.

If you recognized yourself in Victor a minute ago, you’re not alone, and you’re not broken. Your analytical instinct is not the problem you need to fix. It’s the sequence you deploy it in. Change the sequence and you keep every bit of the sharpness that made you valuable in the first place, while you stop paying for it in departures you didn’t see coming.

The Strengths-Based Leadership Trap

Marcus Buckingham’s research on strengths-based leadership is among the most replicated work in organizational psychology, and it’s worth knowing exactly what it says and exactly where it gets misused. The core finding: people develop faster, perform better, and sustain effort longer when their work draws on their natural strengths instead of forcing them to constantly fight their own limitations. Gallup’s data shows that people who use their strengths daily are six times more likely to be engaged at work, and three times more likely to report a high quality of life. That finding is real, and it has genuinely improved how good leaders develop their people.

But the misapplication of this research is rampant, and you need to hear it plainly: strengths-based leadership does not mean ignoring weaknesses. This produces one of the quietest, most destructive patterns in management today. You know someone’s strengths, you celebrate them, and then you use those strengths as your excuse for never addressing the behavioral patterns that are actually limiting them and costing your team. The strengths language becomes avoidance language. The positive framing becomes cover for a hard conversation you don’t want to have, and that the person genuinely needs you to have.

Think about the man on your team who’s brilliant at building client relationships but routinely misses internal deadlines. A strengths-based approach that just celebrates the relationship brilliance and quietly excuses the missed deadlines isn’t helping him. It’s harming him. Those missed deadlines have real costs, to your projects, to his colleagues, to the trust your organization runs on. And when you accommodate the failures without ever naming them, you’re telling him, implicitly, that the behavior is fine. Which means he doesn’t change it. Which means the pattern compounds. Which means the eventual reckoning, once the costs become undeniable, is much harder and much more damaging than an honest conversation early on would have been. The strengths-based leader who never names the weakness hasn’t been kind to that man. He’s delayed a necessary conversation until the delay itself becomes part of the damage.

Applied properly, strengths-based leadership does not mean focusing only on strengths. It means you understand what someone is naturally excellent at, and you deploy that excellence where it matters most. It also means you address the weaknesses — not by trying to turn a limitation into a strength, but by managing around it and being honest when a specific weakness is causing a specific, costly problem. The strengths framework tells you where to put your development energy. It never tells you to pretend the limitations aren’t real, or that their costs aren’t real.

Here’s a simple test for you. Are there things people on your team are doing right now that cost you and the team real value, that you’ve never explicitly, directly named, because you’d rather focus on the positive? If the answer is yes, you’re not practicing strengths-based leadership. You’re practicing avoidance, dressed up in developmental language. The positive framing is real and useful. The avoidance is real and costly. And the two aren’t actually incompatible — you can be genuinely strengths-focused and still have direct, honest conversations about specific behaviors causing specific problems. The best leaders do both. The mediocre ones use one to justify skipping the other.

If you want a broader framework for building teams that hold up under pressure rather than optimal conditions, that’s exactly what resilience as a leadership trait gets into. It covers how the best leaders prepare their people, long before the pressure ever arrives.

Lencioni’s First Dysfunction

In every meeting, find something you’re genuinely uncertain about and say so out loud.
Find a mistake you made that’s relevant to the discussion, and name it before someone else has to.
Ask for input on something you genuinely need help with, and then visibly use what you get back, so people understand the asking wasn’t rhetorical.

Patrick Lencioni’s Five Dysfunctions of a Team identifies absence of trust as the foundational failure underneath every dysfunctional team — the root everything else grows out of. The trust he’s describing isn’t the general sense of believing someone is honest. It’s vulnerability-based trust: your willingness to be open about your weaknesses, your mistakes, your fears, and your limitations without expecting to be judged or punished for it. That kind of trust, the kind that lets a person say “I don’t know,” “I made a mistake,” and “I need help” in front of their colleagues, is the substrate everything else in a high-performing team gets built on. Without it, disagreement turns political instead of productive. Accountability turns into blame instead of shared commitment. And attention to actual results gets displaced by everyone quietly protecting themselves.

Here’s what gets missed constantly in how people apply this model: you, the leader, create or destroy this kind of trust more powerfully than any dynamic on the team itself. If you don’t model vulnerability — if you show up as the person in the room with all the answers, who’s never uncertain, never wrong, never in need of anyone’s input — your team will mirror that back at you. Nobody is going to be vulnerable when the authority figure in the room has just told them, without saying a word, that vulnerability is weakness. Your team takes its cues from you. A leader who’s never uncertain produces a team that performs certainty it doesn’t actually have. A leader who’s never wrong produces a team that hides its mistakes. A leader who never asks for help produces a team that struggles alone instead of asking for what it needs.

This is a particularly acute problem if you’re a man, because the socialization toward performing certainty runs deep in most professional settings. Showing uncertainty feels like incompetence to you. Admitting you don’t know something feels like handing over your authority. Saying “I was wrong about that” feels like undermining your own credibility. So you — especially if you’re newer to leadership, or operating somewhere genuinely competitive — perform certainty and competence even when you don’t actually have it. That performance is convincing enough to fool anyone who isn’t paying close attention. It doesn’t fool the people working closely with you, because they see the decisions your performed certainty produces, and those decisions have a specific quality: they don’t incorporate the information that genuine uncertainty would have gone looking for.

The result is a team performing certainty and competence right back at you, which means the actual state of knowledge in the room is hidden behind everyone’s performance, yours included. Decisions get made on stated certainties that are secretly uncertainties nobody wanted to admit to. Problems get ignored, because admitting you have a problem means admitting you didn’t have it handled. Initiatives fail in ways that were perfectly predictable, but that nobody said out loud, because saying it out loud required public uncertainty. There is more collective intelligence sitting in that meeting room than any single decision you make actually reflects. The intelligence is hiding behind a performance. And that performance is calibrated to avoid the exact social cost your system has quietly attached to being vulnerable.

So here’s the intervention, and it’s concrete. Model vulnerability first, last, and consistently.

None of that is a weakness signal. It’s an authority signal. The most credible people in any room are the ones whose certainty, when they finally express it, is believable, because you’ve also seen their uncertainty. Performed certainty is transparent to everyone watching it. Genuine certainty that coexists with genuine uncertainty is credible. That’s the entire distinction between a leader who commands real authority and one who only commands the compliant performance of authority — a performance that vanishes the moment someone has an exit option they’re willing to use.

Michelle Torres and the Attribution Habit

Here’s a second composite worth sitting with. I’ve drawn this one as a woman, because the pattern shows up in leaders of every kind. It’s worth seeing without your own defenses going up right away. Call her Michelle Torres. She’d been Vice President of Operations for four years when her company brought in an organizational health consultant. The 360-degree feedback process that followed produced results Michelle described as a slap in the face. Her direct reports, unanimously, described a leader who was intelligent and organized, but who they did not trust with real information. Their phrasing, anonymized across several responses, clustered around one idea: they didn’t tell Michelle the full picture, because she’d use it against them if something went wrong.

Michelle hadn’t built this culture on purpose. She’d built it through one specific pattern she was completely unaware of, until the consultant named it out loud for her. When something went wrong on her team, her first move, every time, was attribution. Who made this decision? Who had this information? The questions were framed as operational learning, but the emotional register underneath them was unmistakably accountability-first. Her team understood that being associated with a failure inside Michelle’s attribution process meant being associated with that failure in Michelle’s memory going forward. It wasn’t formal punishment. It was social and reputational, and it shaped who got the visible projects and how people worked with her afterward. Her team had learned this accurately, from watching it happen. They were responding rationally to what they’d learned.

So they adapted, the way any smart team would. They communicated with Michelle in ways that minimized their exposure to her attribution process. They surfaced problems late, only after they already had a solution worked out, so the problem and the fix arrived together instead of the problem arriving alone. They filtered out any mention of risks that hadn’t materialized yet, because naming a risk meant owning it if it ever did. Michelle’s picture of her own operation was systematically incomplete — not because her team was incompetent or dishonest, but because they were intelligent adults who had read the incentives she’d created with total accuracy.

The consultant’s prescription surprised her. Before addressing anything else, Michelle needed to stand in front of her team and publicly, specifically own a recent organizational failure that had multiple contributors. Not the vague version — “we all could have done better” — but the specific version: I made this decision, it was wrong, and here’s exactly what I’m doing differently. She resisted for weeks. The resistance made sense to her at the time. She’d built her entire professional identity around competence, and the admission being asked of her felt like publicly dismantling that identity. What she couldn’t see, until the consultant forced her to look at it directly, was something else entirely. The identity she was protecting was the very thing costing her the operational effectiveness she needed, in order to protect that identity in the first place.

She finally did it in a team meeting about a product launch that had underperformed. She named her specific decision. She named why she believed it had contributed to the outcome. And she asked the room, directly, what they would have recommended instead. Within six months, her team’s information-sharing had measurably changed. Problems started surfacing earlier. Risks got named without a pre-attached solution stapled to them, just to make them safe to mention. The quality of Michelle’s operational picture improved dramatically, because the incentives around sharing real information had actually changed. She hadn’t become a softer leader. She’d become a more effective one. Her credibility went up, not down, because her certainty was now credible — it coexisted, visibly, with her willingness to own uncertainty and error.

You may be sitting with a version of Michelle’s discomfort right now, just thinking about doing what she did. That discomfort is not a sign you shouldn’t do it. It’s a sign of exactly how much your team has already learned to read you, and how much they’re waiting to see whether you can be trusted with the truth the way you’ve been asking them to trust you with theirs.

Daniel Goleman’s Pacesetting Trap

Daniel Goleman’s research on leadership styles, published with Richard Boyatzis and Annie McKee in Primal Leadership, identified six distinct leadership styles and how each one affects organizational climate. Five of the six work well in different situations. One of them, the pacesetting style, produces reliably negative climate effects whenever it’s used as your primary, default mode. And here’s the twist: it’s the default style of many of the most talented individual performers who get promoted into leadership. That’s not a coincidence. Pacesetting is a natural extension of the exact habits that made you excellent as an individual contributor, deployed in a context where those same habits now produce a completely different result.

As a pacesetter, you lead by example and by high standards. You do excellent work yourself, you set high expectations for others, you notice fast when standards slip, and you step in to correct it, often by taking over or by showing someone the right way to do it. In the short term, this produces impressive results. Standards stay high. The work is good. Problems get handled quickly. You’re visibly excellent, and your excellence communicates expectations more effectively than any policy document ever could. In a small team, or in a genuine short-term crisis, this can be exactly the right approach. Goleman never says pacesetting is always wrong. He says it produces specific damage when it becomes your default, permanent mode.

That damage builds over time, and it compounds in a way you might not expect. Your presence in every detail communicates, without you saying it out loud, that you don’t trust your people to handle the details. Your quick corrections communicate that your standards are the only standards that count, which means people stop developing their own judgment and just try to match yours instead. Your habit of taking over when something goes wrong means people never get the chance to build real problem-solving capacity through the productive struggle of working through a difficulty themselves. As a pacesetter, you’re accidentally preventing the exact team capability you need, by being too good at the thing you’re asking them to develop.

Goleman found that teams led by pacesetters often show high engagement in the first months of working together, followed by a steep decline as people start feeling micromanaged, underestimated, and permanently not-quite-good-enough for a standard that seems to keep moving. The goalposts aren’t actually moving. You’re just good at your job, and you keep doing it well in a way your team can’t match yet, because they’re not as experienced as you are. But from inside the team, the experience is one of perpetual inadequacy — never quite good enough, working hard to meet a standard that’s always slightly out of reach. That experience isn’t motivating past a certain point. It’s exhausting. It produces high initial engagement, a steady decline in sustained engagement, and the exact kind of departure that happens when someone’s worked hard for two years and concluded the environment simply won’t let them become what they’re capable of becoming.

The distortion sitting at the center of pacesetting is the belief that demonstrating excellence and demanding excellence are the same thing as developing excellence in someone else. They are not. Developing excellence in another person requires you to tolerate watching imperfect execution without stepping in. It requires giving feedback after the fact instead of during. It requires accepting that the path someone else takes to excellence is going to look different from the path you took. None of that comes naturally to high performers. All of it is necessary if you actually want your team’s capacity to eventually exceed your own. A leader who can’t tolerate watching his team do something less well than he’d do it caps his team’s ceiling at his own. A leader who can tolerate it, who makes room for people to develop through productive struggle, builds a team whose ceiling eventually passes his. That’s the only outcome worth calling real leadership.

If you’re a pacesetter, and you probably know by now whether you are, here’s what you need to hear directly. You did not get here by accident. You got here because you were genuinely excellent, and excellence got rewarded, and nobody ever told you the exact thing that made you excellent as an individual would need to be partly unlearned to make you excellent as a leader. Nobody tells you that. You have to hear it now, from me, and then you have to decide what you’re going to do with it. You can keep being the best person in every room you lead. Or you can start building rooms that don’t need you to be the best person in them anymore. Only one of those scales beyond you.

There’s a deeper distinction worth exploring here between high performers and effective leaders. The exact skills that made you excellent as an individual contributor actively work against you in certain leadership situations. It’s worth knowing which situations those are.

What the Research Says About Who Actually Changes

They pick one or two specific behaviors to change, not a long list. Trying to fix everything at once is how you end up fixing nothing.
They state the behavior in observable, measurable terms — not “be more approachable,” but something you could watch them do or fail to do in a specific meeting.
They build an accountability structure around it — a coach, a peer, or direct reports who give them ongoing feedback on whether the behavior actually changed.
They measure the downstream outcome the behavior was supposed to produce, not just the behavior itself — safety scores, retention, the quality of the work coming out of the team.
They treat the whole thing as a competency-building project, not a personal improvement aspiration they hope sticks.

Jack Zenger and Joseph Folkman have compiled 360-degree feedback data on more than a hundred thousand leaders over two decades. Their research produces a finding that’s both encouraging and sobering at the same time. Leaders can change. Your development trajectory for leadership effectiveness is not fixed. Leaders who receive honest feedback, commit to specific behavioral changes, and measure their progress consistently show measurable improvement on the exact dimensions they worked on. The data on this point is clear. Leadership effectiveness isn’t a trait that gets set the day you’re hired. It’s a capability that develops in response to honest feedback and deliberate practice.

Here’s the sobering part. Most leaders never receive honest feedback in the first place, never commit to a specific behavioral change, and never measure their own progress. Zenger and Folkman found that most leaders who do receive 360-degree feedback don’t change measurably. It’s not because the feedback was wrong, and it’s not because they lacked the capability to change. The process stopped at the feedback and never produced the behavioral commitment and repeated practice that real change actually requires. Insight without practice doesn’t produce durable change. This is the single most common failure in leadership development. You read the feedback. You feel appropriately motivated for about a week. You make some general resolution about being more open, or more approachable, or better at delegating. And two months later, you’re behaving exactly the way you were behaving when the feedback was collected in the first place. Not because you were dishonest, and not because you weren’t committed. Because general resolutions dissolve the moment they run into the habits they’re competing against. Specific behavioral commitments, with specific measurement attached, survive that pressure far better.

So who actually changes? The leaders who show measurable, sustained improvement in Zenger and Folkman’s data share a specific profile, and I want you to hear it as a checklist for yourself.

That difference in approach produces a visible difference in outcome. Everything I’m about to walk you through in the Leadership Audit Protocol is designed to put you inside that profile — the leaders who actually change — rather than the majority who only ever intend to.

The Leadership Audit Protocol

All five of the mistakes you’ve just heard share one structural feature: they’re invisible from inside your own perspective. If you’re making them, you don’t know you’re making them. You have a story about your own behavior — caring, direct, high-standards, decisive — and that story is accurate about your intent and inaccurate about your impact. The gap between those two things is where the damage lives, and closing it requires a systematic, honest, data-grounded process. Not a vague intention to be better. Not another leadership book. An actual audit that produces actual data about your actual patterns and generates actual behavioral commitments you can measure.

Before you can close that gap, you have to hear a hard truth some of you are probably already wondering about: what if what the audit reveals is too large, or too entrenched, to actually fix? Here’s the honest answer. The audit is not a verdict. It’s a diagnosis. Patterns that are large and entrenched are harder to change than patterns that are recent and situational, but they are not unchangeable. What matters is whether the pattern is behavioral or dispositional. Behavioral patterns — specific things you do in specific situations — respond to deliberate practice. Genuinely deep dispositional patterns, chronic contempt, an inability to regulate anger, pervasive mistrust of everyone around you, may need more than this protocol provides. Be honest with yourself about which one you’re actually looking at. Most of what damages teams is behavioral. Behavioral patterns are hard to change, but they yield to consistent practice in a way that deep temperament simply doesn’t.

Let’s build the protocol together, in three phases.

Phase One: Getting Honest Data

The first thing you need is honest data about your impact, and that means creating the actual conditions under which honest data can be offered to you. Standard 360-degree feedback processes fail at this constantly, because people know that anonymity in a corporate feedback process is frequently less complete than it’s advertised to be, and they self-censor accordingly. The value of a 360 review is real when the conditions for honest input are genuine. When they’re not, what you get back reflects your official reputation, not your actual impact.

The most reliable method is a structured, individual conversation with each of your direct reports, run by someone they trust who isn’t you. The questions need to be behavioral and specific, never evaluative. Don’t ask “how effective is your leader?” Ask something like: “Can you give me a specific, recent example of a time you had information relevant to a decision your leader was making, and chose not to share it? What led to that choice?” Behavioral specificity bypasses the performance of loyalty or politeness that a straight evaluation question triggers. People can answer a behavioral question honestly far more easily than they can evaluate you directly, because a behavioral question just asks them to report, not to judge.

If a structured third-party process isn’t available to you, self-administered data can still be valuable, as long as the questions stay behavioral and honest. Keep a log for two weeks. Every time you respond to a piece of information your team brings you, write down what the information was, what your actual response was, and what emotion you felt in that moment. Then ask yourself what a rational outside observer would conclude about whether it’s safe to bring you information like that. The emotion question matters more than it sounds like it should, because the emotions you feel in the moment are often visible to other people even when you believe you’re managing them well. The slight tightening when bad news arrives. The edge that creeps into your voice when a decision gets challenged. People perceive these things. They’re informative about your actual safety climate, and they need to be part of your data set.

Phase Two: Finding the Pattern

Isolated incidents are not patterns. A pattern requires at least three to five instances of a behavior with similar triggers and similar effects. What you’re looking for in this audit is a pattern, not an individual misstep. Everyone has individual missteps. That’s not the question in front of you. The question is whether these behaviors cluster into something consistent and predictable — something the people around you have already identified and adapted to, even if you haven’t identified it yourself yet.

Here are the specific patterns to check yourself against, and they map directly onto the five mistakes you’ve already heard. Do people in your meetings speak up early, or do they wait to see which way the room is moving before they commit to anything? When something goes wrong, who bears the social cost in the conversation afterward — you, or the team? When someone brings you an underdeveloped idea, what’s your first move, curiosity or immediate critique? How often in the past six months have you explicitly said “I don’t know” or “I was wrong” in front of your team? How often have you taken over a task because watching it done imperfectly felt worse to you than the development cost of letting the person work through it themselves? Those questions produce real behavioral data. Behavioral data, across multiple instances, reveals a pattern. Patterns are what you actually change.

And here’s a question I’d guess some of you are already asking: how do you know which of these five mistakes is actually costing you the most? Look at where the biggest gap exists between what you know and what your team knows. If problems are surfacing late, the safety issue is your most likely culprit. If your team executes existing plans well but rarely brings you genuinely novel ideas, the critique-before-curiosity pattern is probably it. If your best people leave consistently after eighteen to twenty-four months for no obvious reason, look at pacesetting and strengths-without-accountability. If everyone agrees with you in meetings, that’s your vulnerability and trust problem showing itself. The symptom you’re seeing in your team’s performance is usually your diagnostic. Match the symptom to the most likely cause before you start doing the work, because changing the wrong behavior while the real one goes unaddressed just produces exhausting effort with nothing to show for it.

Phase Three: Changing One Thing

The mistake most leaders make once they finally have this kind of self-awareness is trying to change too many things at once. Your leadership behavior is deeply habitual. The neural pathways producing your default responses under pressure have been reinforced across thousands of repetitions, and changing them requires concentrated, repeated practice on one specific behavior, not diffuse good intentions spread across a wide front. Decide on the single most important change and make only that one. Execute it consistently for thirty days. Measure the specific outcome you predicted it would produce. Then decide whether to keep going, adjust it, or add a second change on top of it.

Identify, from the data you’ve already collected, the single mistake that’s doing the most damage to your team’s performance. Not the one you’re most comfortable addressing. The one actually costing you the most. Commit to one specific behavioral change that targets that exact pattern. State it in behavioral terms. Don’t say “be more open to feedback.” Say “ask two genuine questions before I note a weakness in any idea someone brings me.” Don’t say “create psychological safety.” Say “when someone brings me a problem without a solution attached, respond with a question instead of an answer, for the next thirty days.” That specificity isn’t pedantic. It’s the entire mechanism. General intentions dissolve under pressure. Specific behaviors are executable in the moment, and they generate specific feedback on whether you actually changed anything at all. You can’t rationalize your way around a specific behavior the way you can around a vague intention. At the end of thirty days, the evidence is clean: you did it, or you didn’t. There’s no middle ground, and that clarity is the entire point.

Context Is Everything

When you walk into a meeting, are you defaulting to command because the moment genuinely requires it, or because command is simply your comfort zone?
Can you name the last time you deliberately chose a coaching approach over a directive one, and why you chose it?
Do the people around you get more of your patience in a real crisis, or less?
If you had to justify your default style to your own team, out loud, could you do it in one honest sentence?

One of Goleman’s most important contributions is the demonstration that no single leadership style works everywhere. The coaching style — long-term development, vulnerability, curiosity, strengths-based support — is the highest-impact style in most situations you’ll face. It is not effective in a genuine crisis where you need rapid, unambiguous direction. In a real crisis, an authoritative or even a coercive approach might be exactly right. A team that needs twenty minutes of democratic deliberation during a building fire is not being well served by the coaching style. But a team that needs coaching for years and instead gets command-and-control the entire time isn’t being served by the pacesetting style either. Context is the variable that decides which approach actually serves the moment you’re in. If you don’t understand that, you’ll deploy your default style regardless of what the situation actually calls for. If you do understand it, you have the range to choose the right approach on purpose.

This matters for your audit, because it protects you from misapplying everything you’ve just heard. The goal isn’t to eliminate your tendency toward any particular style. The goal is to develop the range to deploy the right one for the context you’re actually in, and the self-awareness to know which style you’re currently running and whether it’s the right call. This audit isn’t about becoming a softer leader, or a warmer leader, or a more democratic one. It’s about becoming a more accurate leader — someone who can read a situation correctly and respond with whatever approach that situation actually needs. That accuracy starts with self-knowledge, because you can’t make a deliberate stylistic choice if you don’t know what your own default is and what it produces.

Try this quick self-audit before you move on. Ask yourself these four questions honestly, right now, about the room you lead.

If you struggled with any of those four, that’s useful information about you, not a verdict on you.

One more question worth answering directly: what if your organization or your industry genuinely requires authoritative leadership? Some contexts genuinely do, and Goleman’s research acknowledges that plainly. Emergency medicine. Military operations under active engagement. Crisis management during an organizational catastrophe. These situations require clear authority, fast decisions, and high compliance with command. The real question for you is whether you’re actually operating in one of those contexts. Or whether you’re using the theoretical possibility of a crisis to justify a default mode that doesn’t actually serve you in the environment you’re really working in day to day. Most knowledge-work environments, most business, product, and creative contexts, benefit from the full range of styles, with coaching and a genuinely affiliative approach providing the baseline from which an authoritative intervention becomes credible and effective when you genuinely need one. The credibility of that intervention depends entirely on the relationship you built in coaching mode beforehand. A leader who only commands has no relational capital to spend when command is genuinely required. A leader who mostly coaches, and occasionally commands, has all the credibility that command needs to land the way it’s supposed to.

Research on emotional intelligence, which is Goleman’s larger contribution to leadership psychology, isn’t really about being warmer or more empathetic in some general sense. It’s about having the perceptual accuracy to read what a specific situation and a specific person actually require, and the behavioral range to deliver it. Self-awareness is the prerequisite for that accuracy, which is exactly why this whole conversation starts with the audit rather than with a list of things leaders should do. You cannot consistently do the right thing if you don’t first see clearly what you’re actually doing right now.

You can go deeper on how emotional intelligence operates in high-stakes environments and why self-awareness is the single highest-impact skill a man in your position can develop.

Robert Sullivan and the Shadow Communication System

One last composite, because it shows you what all of this looks like when it’s hiding in plain sight. Call him Robert Sullivan, managing a twelve-person product team at a mid-size technology company. His own leadership regarded him as one of the strongest managers in the organization — high delivery rates, low drama, consistent performance, quarter after quarter. What neither Robert nor his leadership knew was that his team had built an extensive shadow communication system underneath him. There was a group chat he wasn’t in. There was a set of pre-meetings before the real meeting. And there was a set of informal norms about what could and couldn’t be said in front of him.

An organizational health review, triggered by the company preparing for a Series B round, uncovered the shadow system. The consultant’s interviews with Robert’s team produced a consistent picture. Robert was predictable. He was fair in the formal sense. He was free of the most obvious leadership pathologies you’d expect to find. But three specific patterns had convinced his team that real communication — about risk, about interpersonal friction, about genuine strategic disagreement — was not safe through the official channels. First, Robert visibly preferred consensus. When someone raised a counterpoint to a direction he’d already indicated he favored, he’d acknowledge it politely, then spend more time and more energy restating the reasoning behind his original position. His team learned to read that as a clear signal, one they eventually put into words for the consultant:

“He’s going where he was already going. Raising a counterpoint just makes the meeting longer without changing the outcome.”

That was the read. Second, Robert’s response to mistakes was calm, but pointed. He’d identify exactly who made which decision and trace the causal chain from that decision to the error, with real precision. Third, in two years of weekly team meetings, nobody on his team could recall a single time Robert said “I don’t know” or “I’m not sure.”

None of those three patterns were dramatic on their own. None of them were malicious. But together, cumulatively, they’d built a team that was performing competently and hiding exactly the information that would have let them perform excellently. That shadow communication system held the team’s real risk assessments, their real interpersonal friction, and their real strategic disagreements, all of which could have meaningfully improved Robert’s decision-making, if he’d ever known about any of it. The high delivery rate his leadership saw was real. It was also the ceiling of what his team could produce inside a system optimized for defensibility instead of excellence.

Robert’s audit identified these patterns clearly, and he addressed them with targeted behavioral changes over six months. Eighteen months after the review, his team ranked in the top quartile for psychological safety on the company’s next organizational health survey, up from the bottom quartile the time before. His delivery metrics held steady. His team’s innovation output, the number of new initiatives proposed and actually adopted, went up substantially. The hidden communication had contained real value the whole time. Surfacing it cost Robert some of the certainty-performance his reputation had been built on. What it returned to him was a team actually performing at its real capability, instead of the ceiling his own defaults had quietly imposed on it.

Ask yourself honestly whether you have a shadow system running underneath you right now. You may not be able to see it from where you’re standing — that’s exactly what makes it a shadow system. But your team knows. They always know. The only question is whether you’re willing to go find out what they know, or whether you’d rather keep believing your delivery numbers are telling you the whole story.

What Good Leadership Actually Costs

Here’s the part of this conversation you won’t find in most leadership books, because it isn’t comfortable to say out loud. The behaviors that build psychological safety, that develop people, that create the conditions for genuine team excellence, are not easy. They are not natural for most people who perform well as individuals. They require you to give up things that feel important to you. Your willingness to give those things up isn’t a test of your warmth or your emotional intelligence. It’s a test of whether you’ve actually understood what leadership requires, and whether you’re willing to pay what it actually costs.

You already know, if you’re honest with yourself, which of these costs you’re least willing to pay. Maybe it’s the certainty you’d have to give up. Maybe it’s the credit you’d have to share, or the control you’d have to loosen your grip on. Name it to yourself right now, quietly, before you keep listening. You don’t have to say it to anyone else yet. You just have to stop pretending to yourself that you don’t already know exactly what it is. That single act of honesty, just between you and yourself, is where every real change you make from here actually starts. Nothing after this point works if you skip it.

Vulnerability requires you to give up the performance of certainty that comes bundled with your position. Genuine curiosity before critique requires you to give up the immediate satisfaction of showing off your own analytical skill. Tolerating imperfect execution without stepping in requires you to give up the short-term quality that stepping in would have produced. Naming your own mistakes requires you to give up the reputational cover that silence would have offered instead. These costs are real, and I’m not going to pretend otherwise. They’re also costs the best leaders pay routinely, not as a sacrifice, but as an investment in the one thing that actually scales past you: other people’s capacity to perform without needing you standing over them.

And the benefits are just as real. A team that tells you the truth. A team that brings you early-stage problems instead of hiding them. A team that develops beyond what you alone could ever build. A team that stays and invests in the work, rather than leaving or quietly checking out. Those benefits compound over years. The best teams don’t run on your individual capacity. They run on their own, and your role shifts from being the best performer in the room to being the architect of the conditions other people need to perform at their best. That shift is not a reduction in your standards. It’s a different, more demanding version of excellence, one that most technically brilliant individual contributors resist for years before they finally make it, and some never make at all. The ones who never make it build teams that work around them. The ones who make it build organizations that outlast them.

For a broader look at the psychological demands of building something that requires other people, stoic leadership principles get into what the great leaders throughout history understood about the relationship between self-mastery and the capacity to actually lead others.

The Transition Most Leaders Never Complete

There’s a developmental transition in leadership that separates the men who build things from the men who just do things, and most high performers never complete it cleanly. It’s the transition from individual contributor to team architect, from “I am valuable because of what I produce” to “I am valuable because of what I enable other people to produce.” This is not a subtle shift for you. It’s a fundamental reorientation of how you measure your own contribution, where you direct your energy, and what you count as a win on any given day.

The individual contributor model is simple, and it’s genuinely rewarding while you’re inside it. Effort produces output. Output is visible. Visibility produces recognition. Recognition produces advancement. That feedback loop is short, clean, and highly motivating. When you’re a high-performing individual contributor, you know exactly how good you are, because you can measure it directly. The output is yours. The quality is legible to everyone.

The recognition follows the work in a straight causal line.

The team architect model is none of that. The output belongs to the team, not to you. Your contribution is often invisible. It’s the conversation that opened up someone’s thinking. It’s the environment that let someone take the risk that produced the breakthrough. It’s the feedback you gave six months ago that’s now showing up as a capability that person didn’t know they’d developed. You can’t easily measure any of that. You can’t point to it in a performance review. You don’t get recognized for it the same direct way you used to. That’s genuinely uncomfortable, especially if you spent decades in school and in the early part of your career learning to measure your own value strictly in terms of individual output.

Every one of the five mistakes you’ve heard about tonight is a symptom, in a different form, of this exact incomplete transition. A leader who demonstrates expertise instead of developing it in others hasn’t fully made the move from individual contributor to team architect. A leader who creates unsafe conditions for honest feedback is protecting his own competence performance instead of building the team’s collective intelligence. A leader who applies strengths language without addressing weaknesses is avoiding the difficult developmental conversations that team architecture actually requires of him. A leader who can’t model vulnerability is protecting an individual reputation instead of building a team culture. The pacesetter who keeps taking over is doing the work himself, instead of developing the people who are supposed to do it.

The complete transition requires you to accept a fundamental change in where your professional identity and your satisfaction actually come from. No longer “I am the person who does this best.” Instead: “I am the person who builds the environment where others do this best.” Eventually, they do it better than you ever could. That second identity is genuinely harder to live inside than the first one. It doesn’t produce the same clean, immediate feedback you’re used to. It requires faith in a process whose results are usually delayed and diffuse. It requires the kind of long-term thinking that short-term performance culture actively works against, every single day. And it produces the only outcome that actually scales — a team capable of doing things no single person, including you, could ever do alone.

Men who complete this transition tend to describe it the same way, almost word for word. It’s the moment they stopped competing with their own team and started competing with the team’s potential instead. The first competition has a ceiling: your own capability. The second one doesn’t. The leaders who build organizations that outlast them, whose teams keep performing after they’ve moved on, whose people go on to become excellent leaders themselves — these are the men who made the transition all the way through. They didn’t give up on excellence. They upgraded their entire definition of it.

What Happened to Derek

Derek eventually got the feedback. Not through any formal process — through a resignation conversation with one of his best people, someone who was finally honest with him in the specific way that departing employees sometimes are, once they have nothing left to lose. He sat with it for three weeks before he did anything at all. Then he brought in an executive coach, ran a real 360-degree feedback process, and started the actual behavioral work.

It took him fourteen months. Not to become a perfect leader — nobody becomes that — but to become one whose team was no longer secretly updating their LinkedIn profiles in the parking lot after his meetings. That’s the real goal here, and I want you to hold onto it. Not perfection. An accurate understanding of your own impact, and the willingness to do the work that closes the gap between what you intend and what you actually produce.

Most leaders never get the honest conversation Derek eventually got. They lose their best people to “better opportunities” that are really just better bosses somewhere else. They wonder why their team consistently underperforms its own talent. They blame the talent instead of looking at themselves. The audit you’ve just heard is the alternative to all of that. It’s the deliberate, honest, data-grounded examination you do before someone walks out the door. It’s how you hear what they should have been able to say to your face, in your last team meeting, instead of in a resignation letter.

You don’t have to wait for your version of that resignation conversation. You can start tonight. You can ask yourself the questions this episode gave you. You can write down the one mistake you flinched at. You can name the single behavior you’re going to change for the next thirty days, in exact, observable terms, and you can tell one person you trust that you’re doing it, so someone besides you knows to watch for whether you actually followed through. None of that requires a consultant. None of it requires a crisis. It only requires you, tonight, choosing to see what’s actually true about your own impact instead of what you’d prefer to believe about it.

Before we close, ask yourself where you actually stand right now, today, not where you’d like to stand. Which of the five mistakes did you feel yourself flinch at while you were listening? That flinch is data. Don’t argue with it, and don’t explain it away. Write it down tonight, before the feeling fades and your own defenses talk you out of what you already know about yourself.

One last thing before we close, and I want you to actually hear this part. The audit isn’t a one-time event. It’s a practice. The leaders who build the most effective teams aren’t the ones who fixed their leadership problems once and declared themselves finished. They’re the ones who audit continuously — who’ve built into their regular habits the discipline of seeking accurate data about their own impact, questioning their own default behaviors, and making specific adjustments in response to what they actually find. The audit doesn’t end. The improvement doesn’t plateau. The gap between what you intend and what you produce is never closed completely. It’s managed, it’s narrowed, and it’s made visible, over and over again. That visible narrowing, sustained over years, is what builds the kind of leadership reputation actually worth having. Not a reputation for being impressive. A reputation for making the people around you better. The leaders who earn that are the ones people remember.

The ones who were merely impressive get replaced.

Editorial Standards Corrections Medical Disclaimer About Our Content Affiliate Disclosure Site Map

The Meeting That Ended Early — Why Confusing Kindness With Safety Makes Them Hate You