Three years.

He has a vision deck. He has a vision document. He has a vision one-pager for the people who won’t read the vision document, and a vision summary email for the people who won’t read the one-pager.

He has run the vision through two consultants, a brand strategist, and at least one offsite where someone drew a picture of a mountain and everyone nodded.

The vision is genuinely good. I’ve read it. It’s ambitious, it’s clear, and it articulates exactly where the company is trying to go.

But, the company has not moved.

When I finally asked him about it, he looked at me like I’d suggested they skip a step in a recipe. “We’re still refining,” he said. “We want to make sure everyone is aligned before we start executing.”

They had 22 employees.

I want to be careful here because I know this guy well, and he’s not lazy. He’s not disengaged. He’s not one of those leaders who checks out and calls it delegation. He works constantly. He thinks about the company every day. He talks about where they’re going with a level of genuine conviction that would make you want to follow him anywhere.

Anywhere being, in this case, another planning session.

What he has is something I’ve started calling Vision Paralysis Syndrome.

The vision deck was 64 slides. Nothing had shipped. Both facts were true simultaneously, which is impressive in its own way.

Here’s the thing that makes Vision Paralysis Syndrome sneaky: it looks like leadership.

Here’s how…

You’re thinking about the future. You’re communicating direction. You’re bringing people along. And you’re investing in clarity, which everyone says leaders should do. You’re being strategic instead of reactive. You’re playing the long game.

All of this sounds correct.

The problem is that “playing the long game” eventually requires you to play. The long game is still a game. Games have moves.

Vision work, at its best, is the thing that makes execution coherent. It answers the question of why, so that the people doing the what don’t have to stop and ask every five minutes. It creates a north star so the daily decisions have a direction.

Vision work, at its worst, is the most socially acceptable form of avoidance available to a person with a whiteboard. You know this to be true. I can see you nodding.

I’m not immune to this. I want to say that clearly before anyone thinks I’m writing about other people.

I have started things I believed in deeply, spent an embarrassing amount of time on the framing, the name, the structure, the articulation of the idea, and then, when it was time to actually put the thing into the world, found seventeen more things to refine. Because refined things don’t fail yet. An idea that lives entirely in a document is still safe. It’s still perfect. The gap between what I imagined and what exists hasn’t opened up yet.

Execution is where the dream meets reality, and reality is notoriously bad at matching the original vision.

So I refine. you refine.

And I revise. And you revise.

And I get really good at presenting slides.

And you get really good at presenting slides.

We are in this boat together, arent’ we?

The psychological move underneath Vision Paralysis Syndrome is something most of us recognize the moment someone describes it clearly, which is: we are protecting the vision from contact with reality.

Because once you execute, you find out what’s true. You find out if the strategy holds. You find out if the market cares. You find out if your team can actually deliver it, or if the delivery reveals gaps you didn’t account for, or if the whole thing works differently in practice than it did in the planning doc.

And all of that information is useful. Every single piece of it. Failure data is data. Pivots are not disasters. Finding out you were wrong about something is not the same thing as being a leader who was wrong about something.

But try telling that to the part of your brain that wrote a really beautiful vision.

That part of your brain is not interested in data. That part of your brain wanted the vision to be right. It spent time on this. It has feelings about the font.

So instead of executing and finding out, you stay in the planning space a little longer. Just to be sure. Just to get everyone aligned. Just until the conditions are right.

Buy hey. Please hear me. The conditions are never perfectly right. That’s not a flaw in your strategy. That’s just what conditions are.

I want to distinguish Vision Paralysis Syndrome from something that looks similar but isn’t: genuine strategic patience.

There are leaders who wait on purpose.

Who hold a strategy through turbulence because they’ve thought through the turbulence in advance.

Who don’t execute immediately because the timing actually matters, not because execution feels dangerous.

That’s real, and it’s different.

The tell is what you’re doing in the waiting period.

If you’re waiting and doing, building quietly, gathering resources, running small experiments, then you’re being strategic.

If you’re waiting and presenting, revising the deck, holding another alignment session, hiring a consultant to validate what two previous consultants already validated, you’re not being patient. You’re orbiting the work without landing.

The vision is supposed to create momentum. When you notice that the vision itself has become the destination, that’s the diagnosis.

The other tell is what happens in your body when someone asks when you’re going to start.

If the answer is mild annoyance because you have a timeline and they’re interrupting your focus, fine.

If the answer is a spike of something that feels a lot like anxiety, and you immediately start explaining all the reasons why now isn’t quite the moment, that’s information worth sitting with.

That spike is the Syndrome talking.

The paid post this week has the diagnostic and the framework, and I’ll be honest, the diagnostic is the part I’m most proud of because it will make you uncomfortable in a way that’s specific and actionable rather than just uncomfortable in the general ambient way most leadership content achieves. That’s what we do here at Gutsy Leaders.

There’s also a framework for what I call the Minimum Viable Vision, which is the practice of getting a concept small enough and concrete enough to touch reality without abandoning the larger goal. It’s not about lowering your standards. It’s about giving your vision somewhere to live besides the deck.

If you’re a paid subscriber, it will be waiting for you Thursday. If you’re not, the upgrade link is below, and I will tell you sincerely that this particular post is worth it if you’ve ever caught yourself in another alignment session wondering why nothing seems to change.

Subscribe now

Next week we’re naming something I see happen quietly in almost every organization, where responsibilities that were clearly assigned to specific people somehow, over time, become no one’s responsibility at all. No one dropped them. They just converted from solid commitments into ambient vapor.

We’re calling it Responsibility Evaporation.

More Tuesday.

Gutsy Leaders is a psych-savvy leadership publication for people who are done performing. New issues every Tuesday.

Share

Now we’re going to find out if you have one.

The Trophy Audit

Five questions. Answer honestly. No one is watching.

1. When you explain your leadership philosophy or approach, what time period are you drawing from most often?

a) The last 12 to 18 months b) A few years back, but it still mostly applies c) A specific season, a particular company or role, that I think about a lot d) I have a story I tell that I realize I’ve been telling for a very long time

2. When someone on your team proposes a new approach to something you’ve done before, what is your first instinct?

a) Genuine curiosity about whether it might work better b) Cautious openness, but I usually want to see evidence first c) Skepticism, because I’ve seen a lot of approaches come and go d) A fairly strong pull to explain how we solved this problem before

3. How often do you reference a previous company, role, or team as the benchmark for how things should work?

a) Rarely, I try to assess each situation on its own terms b) Sometimes, when it’s genuinely relevant c) More than I probably should, if I’m being honest d) Regularly, it’s usually my clearest example of what good looks like

4. When you think about the version of yourself you are most proud of as a leader, how far back are you going?

a) I feel pretty good about who I am right now b) A couple of years, but I’ve grown since then too c) There’s a specific season that still feels like the peak d) There’s a specific role or company that I think I never quite replicated

5. When the company or team around you changes significantly, what do you feel first?

a) Mostly curious, change usually brings new opportunities b) Some discomfort, but I adapt reasonably well c) A real loss, like something that was working got taken away d) A strong instinct to return to what worked before the change

Scoring

Assign points: a = 1, b = 2, c = 3, d = 4. Add them up.

5 to 9: Anchor-light. You are generally updating yourself in step with your environment. You may have a trophy or two on the shelf, but they’re decoration, not navigation. Keep watching for the moments when a strong opinion about “how things should work” is based on evidence from your current context versus a previous one.

10 to 14: Anchor present. You have some weight on you. You are probably drawing on past success in ways that feel like wisdom but are occasionally functioning more like resistance. The paid framework this week is going to be useful. Read it slowly.

15 to 17: Anchor heavy. You are working harder than you need to, in part because you are dragging something significant. The work below is not optional for you. There is a real cost to your team and your own satisfaction in staying here.

18 to 20: Full anchorage. You are at the coordinates. You may be getting good results through sheer talent and experience, but the gap between where you are and where your context needs you to be is widening. Something needs to change and you probably already know that.

This is the point in the essay where the real work begins. The diagnostic told you something. The framework below is what you do with it.

This content is for Calm Authority and Quiet Power Circle members.

[Upgrade to read the rest]

Subscribe now

The Release Protocol: Five Moves for Leaders Who Are Ready to Drop the Anchor

I am calling this the Release Protocol because “letting go of your past success” is both accurate and completely useless as an instruction. You are not going to just let go of it. It shaped you. It matters to you. It is part of how you understand yourself as a leader.

What you can do is change its location in your operating system. Right now it is in the driver’s seat. The Release Protocol moves it to the passenger seat, which is where it belongs: available for consultation, not in charge of the route.

Here are the five moves, in order.

Move 1: Name the anchor specifically.

Vague self-awareness does not change behavior. Specific self-awareness sometimes does.

So instead of “I know I rely on my past experience too much,” try to name the actual anchor. What was the season? What role, what company, what outcome? What specifically happened there that you are still trying to recreate or protect?

For the CEO from the free essay, his anchor was the zero-to-fifty sprint. The scrappiness, the speed, the feeling of everyone rowing together because survival depended on it. That was the thing he was trying to get back to. Not just the outcome. The feeling.

Naming it that precisely does two things. It shows you what you’re actually attached to, which is usually not the achievement itself but what the achievement made you feel. And it makes it easier to notice when you’re being pulled by it, because you can feel the pull more clearly when you know what’s pulling.

Write it down if you can. “My anchor is __________ and what I’m trying to protect or recreate is __________.”

That sentence alone is worth more than most leadership development sessions I charge a lot of money for.

Move 2: Audit your reference stories.

Every leader has a small portfolio of stories they tell to make a point. The founding story, the turnaround story, the time the team really came together, the thing that almost broke them and didn’t. These are not bad. Stories are how leaders transfer meaning and culture.

But your reference stories are also a map of your anchor. Whatever you keep returning to in conversation is where your identity is located.

For one week, every time you use a past example to illustrate a point in a meeting, a one-on-one, a conversation with your board, notice which story it is and how old it is. You do not have to stop telling old stories. You just need to know which ones you are telling, how often, and whether they are the most accurate evidence you have or just the most emotionally resonant.

If your reference stories are more than three years old and you are using them to make decisions about your current context, the anchor is probably doing more navigation than it should.

Move 3: Interview your current context like it’s a new client.

Trophy-anchored leaders tend to stop asking basic questions about their current environment because they believe they already know the answers. They have seen this before. They know how this goes.

Sometimes they’re right. Often they are working from a model of their organization, team, or market that is eighteen to thirty-six months out of date, because that was the last time they were genuinely curious about it.

The move here is structured re-inquiry. Pick three to five people in your organization who are closest to current reality: a team member dealing with frontline customer problems, a mid-level manager who sees what leadership doesn’t, someone who joined in the last twelve months and still has fresh eyes. Ask them some version of the following questions.

What is actually hard right now that leadership doesn’t seem to fully understand? What is working that we are not recognizing or building on? If you were going to describe the culture to someone from the outside, what would you actually say?

Then listen without defending. The gap between what you hear and what you assumed is the exact size of your anchor.

Move 4: Separate your identity from the win.

This one is slower and harder than the first three, and I want to name that clearly so you don’t think you’re doing it wrong when it takes a while.

Most Trophy Anchors are not really about the strategy or the playbook from the successful season. They are about identity. Specifically, about the version of yourself that the win confirmed: I am someone who can build something. I am someone who can turn this around. I am someone who knows how to do this.

When the environment changes and the old playbook stops working, it doesn’t just feel like a strategic problem. It can feel like a threat to the evidence you have about who you are.

The work here is to find evidence of your identity in your current context, not your past one. What are you learning right now? Where are you being stretched? What is hard in a way that is building you rather than just frustrating you? The goal is not to forget what you built before. The goal is to accumulate current evidence that you are still the kind of person who can build things, so the old evidence is less load-bearing.

This is where a coach, a peer, or a therapist who works with high-performers is genuinely useful. Not because you can’t do this work alone, but because identity work is much harder in isolation than it sounds on a page.

Move 5: Choose a practice of deliberate unfamiliarity.

Anchored leaders often make choices that feel comfortable not because they are lazy but because familiarity has become their primary signal for competence. If it feels familiar, it must be in my wheelhouse. If it’s unfamiliar, that’s a warning sign.

The problem is that at scale and over time, this produces an ever-narrowing range of what you’re willing to engage with. You start managing only the parts of the work you recognize and delegating everything else, not out of good judgment about your leverage but out of quiet avoidance.

The practice here is small and deliberate. Once a week, choose one thing to engage with that is genuinely outside your established expertise. Go to a meeting you would normally skip because it’s not your area. Read something you would not normally read. Ask a question in a domain you’ve been deferring to others without understanding. The goal is not to become an expert in everything. The goal is to train yourself back into comfort with not knowing, which is the precondition for genuine curiosity, which is the antidote to anchoring.

You cannot be curious and anchored at the same time. Curiosity is lighter. It moves.

One More Thing Before You Go

The leaders I have worked with who navigated this well had something in common that I don’t want to skip over, because the framework above can make it sound more intellectual than it actually is.

They were all, at some point, willing to be a beginner again in some part of their work.

Not publicly. Not dramatically. But quietly, in a few specific places, they chose not to already know. And that choice, repeated over time, changed how they related to their own experience. The past success became something they were grateful for rather than something they were trying to recreate. It sat differently. It traveled lighter.

You built something real. That doesn’t go away. But the leaders your team needs you to be right now exist in this season, not the last one.

Put the trophy on the shelf. It’s a beautiful shelf.

Next week: the leader who can describe the vision with extraordinary clarity and passion and somehow has not moved the organization toward it in two years.

More Tuesday.

There was a CEO I worked with a few years back. Smart guy. Built something genuinely impressive. Took a company from eight people in a co-working space to just under three hundred employees in six years. That is a real achievement. The kind that gets you on podcasts and keynote stages and, apparently, into a permanent personality loop.

Because from the moment I started working with him, every answer to every question began the same way: “When we were scaling from zero to fifty…”

Pricing model. “When we were scaling from zero to fifty…” Team structure. “When we were scaling from zero to fifty…” How to handle a difficult board member. “When we were scaling from zero to fifty…”

He had 280 employees. He was in a completely different industry context. His zero-to-fifty playbook had been obsolete for about four years.

But he was so proud of what he had built in that season, so defined by it, so in love with the version of himself that pulled it off, that he could not stop using it as the instruction manual.

His company was not scaling. His team was quietly exhausted. And he genuinely could not understand why.

We have a word for this now. You’re welcome.

The boat left. The anchor did not.

Here is what I want you to consider for a second. The Trophy Anchor is not a story about arrogant leaders who don’t care about growth. It is a story about leaders who care deeply about having been great, and who have quietly confused that with being great right now.

The distinction matters because the cure is completely different. Buckle up.

An arrogant leader needs a reality check. A trophy-anchored leader needs something harder: they need to grieve.

Because the past success is real. The zero-to-fifty win was real. The thing that made them feel competent and capable and like they finally cracked the code on something difficult, that was real. And somewhere between then and now, the environment changed, the company scaled, the team changed, the market changed, and they kept waiting to feel that same certainty again before they were willing to adapt.

The anchor isn’t the trophy.

The anchor is the belief that the trophy is the most accurate evidence they have about who they are as a leader.

I have watched this play out in three versions, and I am going to describe all of them because I want you to feel uncomfortable at least once.

Version one is the founder who can’t stop running the company like a startup even though it is no longer a startup.

Every process that slows things down feels like betrayal. Every layer of management feels like bureaucracy. Every “no, we should put that through proper channels” sounds like someone trying to steal the culture. The scrappiness that won. The scrappiness that is now creating quiet chaos in a 200-person organization. They have the trophy on the shelf and they are insisting on living inside the season it came from.

Version two is the long-tenured executive who was genuinely excellent in a previous era and has slowly, quietly stopped learning.

Not because they’re lazy, but because they learned so much in that previous era that they have a sophisticated and fluent answer for everything. They got good enough that they stopped needing to ask questions. And now they are five years behind on their own industry and no one is telling them because they answer so confidently that it feels rude to push back. Their competence is real. Their currency is old.

Version three is the one that is going to sting a little. It is the leader who had one transformational moment, one big leadership win, one team that they built that actually worked, one initiative that became the thing they’re known for, and they have been reconstructing that season ever since.

Every new team, every new role, every new company is an attempt to recreate the conditions of the thing that worked. And they don’t understand why it never quite lands the same way, because they don’t realize they are trying to run a play from a different game.

You can be successful and still be anchored. That’s the unseen part. The anchor is under water.

The reason Trophy Anchoring is so hard to see in yourself is that it does not feel like being stuck. It feels like having standards. It feels like being the person who remembers what actually worked when everyone else wants to chase something shiny. It feels like protecting the organization from repeating mistakes.

Share

It can even look like wisdom from the outside, for a while. The person who grounds the room in what’s actually been proven. The person who asks hard questions about whether the new direction is better or just different. That’s valuable. That’s important leadership.

The difference between wisdom and anchoring is whether you are grounding the conversation in the past to inform the future, or using the past to avoid moving toward the future.

One of those is mentorship. The other is self-protection with good vocabulary.

The question worth asking yourself is this: When you think about the best version of yourself as a leader, what year are you picturing?

If the answer is recent, you’re probably okay. If the answer is a specific season that has clearly ended, and you have been quietly trying to get back there ever since, the anchor is down.

You don’t have to abandon what worked. I am not asking you to pretend the past success didn’t happen or wasn’t real or doesn’t tell you something meaningful about what you’re capable of. The trophy is yours. You earned it.

I’m just asking you to put it on the shelf instead of in the engine room.

The leaders who do this well, the ones who genuinely update themselves across different seasons and scales of leadership, they tend to have one thing in common. They are deeply curious about who they need to be now, not just proud of who they were then.

Curiosity is lighter than trophies. It moves faster. It doesn’t drag.

Next week we’re going somewhere darker: the leader who has the vision, the passion, and the extraordinarily compelling ability to talk about both, and somehow never quite connects any of it to anything that actually happens.

More Tuesday.

Gutsy Leaders is the newsletter for leaders and business owners who are done performing. If someone forwarded this to you, you can subscribe here.

Subscribe now

This week’s word is Competence Drag: the phenomenon in which a leader expends more energy performing the appearance of knowing what they’re doing than it would have taken to simply know what they’re doing. The free essay is here if you want the full story. Either way, let’s get into the work.

This post has two parts. First, a short audit so you can see exactly where Competence Drag is operating in your leadership right now, and how heavy it is. Then a framework I call the Clarity Conversion: five moves that let you trade the performance for something that actually works, without blowing up your credibility in the process.

Start with the audit.

The Competence Drag Audit

Answer from your actual behavior, not your intentions. The whole point of Competence Drag is that it feels reasonable from the inside. So the question is not what you believe about yourself. It’s what you do.

For each question, pick the answer that most honestly describes what happens in real life. Keep score as you go.

Question 1

You receive an agenda item two days before a meeting that covers territory you’re not fully current on. You most often:

a) Reach out to someone who knows the subject well, get the information you need, and walk in prepared with actual knowledge. (0 points)

b) Do some research, get enough to sound fluent, and fill any remaining gaps with confident-sounding summary language. (2 points)

c) Review enough to track the conversation, plan to ask clarifying questions that redirect attention, and rely on reading the room. (3 points)

d) Show up and manage it in real time using reframing, strategic agreement, and whatever the last person said. (4 points)

Question 2

Someone senior asks you a question in a meeting and you genuinely don’t have a confident answer. Your most common response is:

a) “I don’t have enough information on that right now. Let me get back to you by [specific date].” (0 points)

b) A version of the answer that is partially correct, delivered confidently, hoping the gaps don’t get pressed. (2 points)

c) Restating the question back to them or asking a clarifying question to buy time. (3 points)

d) Pivoting to something adjacent you do know and hoping the thread drops. (4 points)

Question 3

Think about the last week of meetings. How much of your preparation time went toward understanding the actual content versus preparing how you’d come across?

a) Most of it went toward content. I was trying to genuinely understand the material. (0 points)

b) Roughly split. I wanted to know the material and I wanted to present it well. (1 point)

c) More toward presentation. I focused on language, framing, and how I’d handle questions. (3 points)

d) Mostly presentation. Knowing the material deeply felt less important than knowing how to talk about it. (4 points)

Question 4

When a direct report brings you a problem that’s outside your current expertise, you most often:

a) Tell them honestly, help them think through who does know, and loop back once you’ve gotten smarter on it. (0 points)

b) Offer general leadership guidance while being clear you’re not the subject matter expert here. (1 point)

c) Give them an answer that is directionally plausible even though you’re not fully sure, because you don’t want them to lose confidence in you. (3 points)

d) Redirect the conversation toward what they should do, which keeps the focus off what you don’t know. (4 points)

Question 5

How often do you leave meetings feeling relief that no one found out you were less certain than you appeared?

a) Rarely or never. I’m generally operating from genuine understanding. (0 points)

b) Occasionally, maybe once or twice a month. (1 point)

c) Regularly. It’s become a familiar feeling. (3 points)

d) Often. It’s part of most weeks. (4 points)

Scoring

0 to 3 points: Low Drag. You’re operating with real transparency around what you know and don’t know. You may still feel the pull toward performance occasionally, but you’re not letting it run the show. The framework below is still worth reading, but you’re in good shape.

4 to 8 points: Moderate Drag. The performance layer is present and it’s costing you something, even if it’s not obvious yet. You’ve probably got a few rooms where you’re more honest and a few where you default to projection. The Clarity Conversion will help you identify which is which and start shifting.

9 to 14 points: Significant Drag. This is a pattern, not an occasional move. The energy you’re spending is real and the cumulative effect on your team’s willingness to bring you genuine problems is worth taking seriously. The framework below is exactly where to start.

15 points or above: Full Drag. Performance has become the primary operating mode and it’s likely affecting both your energy and your team’s trust in ways you may not be able to see clearly from the inside. The Clarity Conversion gives you a concrete path out, and I’d genuinely encourage you to use it.

The Clarity Conversion

Five moves. In order. Don’t skip to the ones that feel easier.

The goal of the Clarity Conversion is not to make you seem less competent. It is to help you lead from what’s real, which is both more sustainable and more effective than leading from what’s performed.

Every move below has been used by actual senior leaders who were deeply entrenched in Competence Drag and came out the other side with their credibility intact. The transition is uncomfortable for about six weeks. Then it becomes a relief.

You got the guts for this move? If so, let’s go…

Move 1: Audit the drag zones.

Not all of your leadership is in Competence Drag. Some rooms, some topics, some people bring out your actual self. Others trigger the performance almost automatically. Your first move is to identify which is which.

Spend one week tracking the moments when you feel that specific combination of relief and mild shame after a meeting ends. Write them down. Don’t analyze yet. Just notice and name the rooms, the people, the topics that trigger the performance most reliably.

You cannot convert what you haven’t located.

Move 2: Build one honest sentence.

For each drag zone you identified, write one sentence you could say instead of performing. Just one. It doesn’t have to be confessional. It doesn’t have to be a dramatic admission. It just has to be true.

“I want to think about that more before I give you an answer.”

“I’m not current on that. Let me get back to you by Thursday.”

“That’s outside my expertise but here’s how I’d think through finding the right answer.”

These sentences feel terrifying before you say them. They feel obvious after. Practice them in lower-stakes conversations first. Let them become familiar in your mouth before you need them in a high-stakes room.

Move 3: Replace one performance per week.

You don’t have to overhaul your leadership style in a quarter. You have to replace one performed response with an honest one, once a week, for six weeks.

That’s it. Pick one moment where you would normally deflect, reframe, or perform certainty, and use the honest sentence instead.

Track what happens. In most cases, nothing collapses. In some cases, something actually gets better: the other person trusts you more, the problem gets solved faster because you stopped pretending you’d already solved it, or someone in the room who actually knows the answer gets to contribute it.

The evidence accumulates. Let it.

Move 4: Separate credibility from certainty.

This is the psych layer, and it’s the one most leaders need to hear directly. Competence Drag is built on a belief that your credibility depends on appearing to know things. It doesn’t. Credibility is built on consistency, follow-through, good judgment, and honesty over time.

The belief that you must perform certainty to be respected is usually formed early in your career, in an environment where not knowing something was treated as evidence of not belonging. That environment may no longer exist. The belief is running on old data.

Your job in this move is to gather new data. Every time you say “I don’t know” and the room doesn’t collapse, file it. You are retraining a belief system that has been protecting you for years. It needs evidence, not just intention.

Move 5: Create a knowing gap system.

Once you’re out of active drag and operating more honestly, the final move is to build a system that keeps you genuinely informed rather than performatively fluent. This looks different for everyone, but the core components are the same: a small number of trusted people who will tell you what you don’t know, a practice of asking questions before meetings rather than preparing answers, and a clear signal for yourself about when you are actually current on something versus when you’re relying on vocabulary.

The difference between a leader who knows their field and a leader who sounds like they know their field becomes very apparent over time. The first one gets brought in earlier. The second one gets managed around.

You want to be brought in earlier.

A note before you go.

None of this means you have to know everything. That was never the point of good leadership. The point was that you were supposed to know when you didn’t know, and be honest about it, and then go find the right person or the right information to close the gap.

The leaders who do that without drama are the ones people actually want to follow into hard problems. They are what we call Gutsy Leaders.

You can be that leader. The Clarity Conversion is just the path back to it.

Next week we’re naming something I’ve been watching quietly for years. It’s the condition that keeps technically excellent leaders anchored to the version of themselves that worked five years ago, unable to update their identity to match the scale they’re now leading at.

We’re calling it The Trophy Anchor.

More Tuesday.

I once spent forty-five minutes preparing a confident answer to a question I didn’t understand.

This was not a pop quiz. I had the agenda in advance. I had time. I could have called someone who knew the answer, written it on a Post-it, and read it out loud.

Instead, I researched the language around the topic, memorized three industry phrases, and prepared what I can only describe as a vibes-based response that sounded, to the untrained ear, completely plausible.

The meeting went fine. No one pushed back. I drove home with that particular cocktail of relief and low-grade shame that I now recognize as a warning sign.

The problem wasn’t that I didn’t know the answer. The problem was how much energy I burned not admitting that.

There’s a name for this now.

It’s drag in the physics sense. Resistance created by the leader themselves, slowing everything down, burning fuel that was supposed to go toward actual movement. The performance of competence, when practiced long enough, starts to replace competence. And no one around you says anything because they’ve been doing the same thing, and the whole room is just a drag coefficient.

I want to be clear that Competence Drag is not a character flaw. It’s an adaptation.

Most leaders I work with developed it in environments where admitting you didn’t know something felt career-adjacent to admitting you didn’t deserve your seat.

So you learned to project. To rephrase the question back to the person who asked it. To say “that’s a great point, and I want to build on what Sarah said” while Sarah’s point was the first coherent thing anyone had said in twenty minutes and you needed a second to catch up.

You got good at it. That’s the problem.

The energy math stops working somewhere around VP. Early on, performing competence costs you relatively little because the stakes are low and the audience is forgiving. You can get away with a lot of strategic nodding at the director level. But as the complexity increases and the room gets more expensive per hour, performing takes more and more out of you.

The gap between what you actually know and what you’re projecting widens. You start preparing for meetings the way actors prepare for auditions, and the actual work of leading your function starts happening in the margins of your calendar, when you can finally think without an audience.

I’ve watched brilliant leaders spend their best hours on optics. On making sure no one found out what they didn’t know. On constructing a confident exterior around a genuinely uncertain interior, and then wondering why they felt so tired by Thursday.

That’s drag. It has weight. You can feel it.

The team can tell, even when they can’t figure out what to call it. This is the part people don’t want to hear. Your direct reports are not fooled, at least not the sharp ones. They can feel the difference between a leader who is genuinely thinking through a problem and a leader who is performing thinking through a problem. The tell is usually in the questions. Real thinking generates specific, curious questions. Performed thinking generates questions designed to redirect attention or buy time. You’ve seen this, right?

Your team has probably been having quiet conversations about this in the parking lot or over Slack DMs, the way teams always have quiet conversations about the things nobody says in the room. Not because they don’t respect you. Because they’re frustrated that they can’t bring you the real problems.

When someone is in Competence Drag, the unspoken rule becomes: don’t give them anything they might visibly not know how to handle. Protect the performance. Keep it smooth.

That rule is costing you more than you realize.

Saying “I don’t know” is not a credibility collapse. I know it feels like one. I know the first time you do it in a room full of senior people, your heart rate goes up and your brain starts offering you seventeen ways to walk it back.

But the leaders I’ve seen do it cleanly, who look at a board member and say “I actually don’t have enough information on that to give you a good answer, let me get back to you by Friday,” those are the leaders people trust with the big things.

You don’t earn trust by being right all the time. You earn it by being honest about what you know and what you don’t, and then closing the gap.

That’s it. That’s the whole thing.

The leader who performs certainty all the time is a beautiful, well-maintained machine that everyone is slightly afraid to give real information to. The leader who can say “I need to think about that more” is the one who gets the real problems, which means they get to solve the real problems, which means they actually build something.

Competence Drag keeps you smooth. It costs you depth.

If you’re reading this and feeling a flicker of recognition, that’s worth thinking into. Not because you’re doing something wrong, but because this recognition is where the shift begins. This is where you change…

The paid post this week goes deeper: there’s a short self-audit to help you locate where the drag is heaviest, plus a framework I call the Clarity Conversion, five moves that let you replace performance with presence without imploding your credibility in the process.

Subscribe to the paid tier so you get it tomorrow morning.

Subscribe now

Gutsy Leaders is a newsletter for senior leaders who are done performing and ready to actually lead. If this one landed, forward it to someone who’s been nodding through too many meetings.

Share

The free essay is about this Week’s Word that Doesn’t Exist, But Should and what it feels like to be on the receiving end. This post is for the other side of the table.

Specifically, it’s for the leader who suspects they might be doing this and isn’t quite sure, or the leader who knows they’re doing it and hasn’t figured out how to stop.

Both of those people are more common than either of them would like to admit.

The Ambient Firing Audit

These five questions are designed to surface what most leaders don’t say out loud, even to themselves. Read them honestly. Score yourself honestly. Nobody sees this but you.

For each question, choose the response that most accurately reflects your actual behavior, not your intended behavior.

Question 1

You have a direct report who is no longer a good fit for their role. In the last 30 days, you have:

A. Had a direct conversation with them about performance concerns or fit (0 points)

B. Documented concerns internally and plan to have a conversation soon (1 point)

C. Mentioned concerns to HR but not yet to the employee (2 points)

D. Not said anything directly, but have started reducing their responsibilities or visibility (3 points)

Question 2

When you think about this person’s involvement in upcoming projects or meetings, your approach has been:

A. Including them based on their skills and role, same as before (0 points)

B. Keeping them involved but in a reduced capacity, without explaining why (2 points)

C. Routing around them when possible and hoping they don’t notice (3 points)

D. Actively looking for ways to reassign their work to others (3 points)

Question 3

If this person came to you tomorrow and asked directly, “Is my position secure? Do you have concerns about my performance?” you would:

A. Tell them the truth about where things stand (0 points)

B. Reassure them that things are fine, because the conversation feels premature (2 points)

C. Give a vague answer that neither confirms nor denies anything (3 points)

D. Feel a spike of anxiety because you have not been honest and you know it (3 points)

Question 4

The last time you gave this person substantive feedback about their work, it was:

A. Within the last 30 days (0 points)

B. Within the last 90 days (1 point)

C. More than 90 days ago, and it was mostly positive (2 points)

D. You honestly cannot remember (3 points)

Question 5

What is your honest reason for not having a direct conversation about this situation?

A. There is no issue that requires one (0 points)

B. I’m gathering more information before I act (1 point)

C. I’m not sure what to say or how to say it (2 points)

D. I’m hoping the situation resolves itself without me having to address it directly (3 points)

Scoring

Add up your points.

0 to 3: You’re in the clear. Whatever is happening with this person, you’re managing it with enough directness that it doesn’t qualify as an ambient firing. Keep the communication open.

4 to 7: You’re in early territory. The avoidance is starting, but it hasn’t calcified yet. This is the easiest place to course-correct, and the framework below will help you do it.

8 to 12: You’re in it. The person you’re thinking about is probably already aware that something has shifted, even if you haven’t said anything. The gap between what they know and what they’ve been told is creating damage you can’t see. You need the framework below, and you need to move on it soon.

13 to 15: You’ve been ambient firing for a while. It has its own momentum now. That does not mean it’s too late, but it does mean the conversation ahead is harder than it would have been three months ago. Go slow. Be honest. Read all five steps before you do anything.

The Clarity Conversation: Five Moves for the Talk You’ve Been Not Having

What follows is the framework I use with coaching clients when they’re deep in avoidance about a personnel situation and know they need to get out of it. It is not a script. It is a sequence of moves that help you think clearly, prepare honestly, and show up for a conversation that is hard but necessary.

These five moves work whether you’re having a performance conversation, a role-change conversation, or an honest “this isn’t working” conversation. They also work if you’re somewhere in between and haven’t quite decided what the conversation is yet. That’s a real place to be, and we’ll start there.

Move 1: Get honest about what you actually know versus what you’ve decided.

Before you have any conversation, you need to separate two things that have probably blurred together: the facts about this person’s performance or fit, and the conclusion you’ve already reached about them.

Leaders who are ambient firing have usually made a decision. The problem is they haven’t examined it. They’ve let the conclusion run the show while the evidence stays unorganized in the background.

So start here. Write down the specific, observable things that led you to where you are. Not interpretations, not impressions, actual behaviors, missed deliverables, skill gaps, or conflicts that you can describe specifically and that happened at a specific time.

Then write down separately what you have concluded based on those things. Often when you do this exercise, you find one of two things: either there’s less concrete evidence than you thought, which means the conversation needs to be exploratory rather than declarative, or there’s more concrete evidence than you’ve been willing to say out loud, which means you’ve been protecting yourself from a conversation that is already overdue.

Either way, you now know what you’re actually dealing with.

Move 2: Decide what this conversation is.

There is a meaningful difference between these three conversations, and conflating them is one of the main reasons leaders stay in avoidance:

A performance conversation is about specific behaviors or outcomes that need to change, with clear expectations and a defined timeline. The person stays. The situation is addressable.

A role-fit conversation is about a mismatch between this person and this role, which may or may not be resolvable. Sometimes it leads to a transition within the organization. Sometimes it leads to an exit. But the conversation names the mismatch directly.

A separation conversation is about the fact that this person’s time in this role is ending, and your job is to handle that with honesty and care.

You need to know which one you’re having before you walk into the room, because the structure of the conversation, the outcome you’re working toward, and what you owe this person by way of preparation are all different. If you don’t know yet, that means Move 1 isn’t finished. Go back.

Move 3: Give them the real version, not the softened one.

This is the move most leaders skip, and it is the one that turns a hard conversation into a damaging one.

Softening feedback to the point of inaccuracy is not kindness. It is self-protection. When you tell someone their performance is “mostly great, just a few areas to work on” and you’ve already decided they’re not going to make it, you’ve given them false information about their own situation.

They will make decisions based on that information. They will not look for another job. They will not adjust their self-assessment. They will be blindsided when the real news arrives, and they will be right to feel deceived.

The goal is not to be brutal. The goal is to be clear enough that the person can actually use what you’re telling them. That means saying the thing you’ve been not saying, in plain language, without so many qualifiers that the message gets lost.

If you’ve decided this person is not right for this role, that is what you say. Not “I wonder if there might be a better fit somewhere,” not “I’ve been thinking about how we can set you up for success going forward.” The actual thing. Said plainly. With enough care in your delivery that it lands as honest rather than harsh.

Move 4: Let it be a conversation, not a verdict.

Here is what I see leaders do when they finally have a hard conversation they’ve been avoiding: they over-prepare the delivery and under-prepare for what comes next. They say the thing and then they wait, slightly frozen, for the other person to react.

A conversation requires you to be present for the whole thing, including what happens after you say what you came to say.

The person may be shocked. They may be angry. They may have information you don’t have. They may have a completely different read on the situation than you do.

All of those responses deserve a real response from you, which means you need to be in the room as a person, not just as someone delivering a pre-planned message.

This doesn’t mean the conversation is negotiable if it isn’t. A decision is a decision. But there is a real difference between stating a decision with clarity and stating it without any regard for the human sitting across from you, and the people you lead will remember which one it was.

Move 5: Close with something concrete.

The worst version of a hard conversation ends with vague next steps that leave the person more confused than when they walked in. “Let’s keep talking about this” and “we’ll figure it out together” are not closes. They are more ambiguity, which is what got you here.

A real close names the next specific thing that will happen. When you’ll talk again. What the decision point is and when it comes. What they can expect from you and by when. What you need from them and in what timeframe.

If this is a performance conversation, the close is a written summary of expectations and a defined timeline for review. If this is a separation, the close includes next steps for transition, timeline, and what support looks like.

If you leave the room and neither of you knows exactly what happens next, the conversation isn’t finished.

One more thing, and I mean this.

If you’ve been ambient firing someone for months and you know it, the hardest part of this process isn’t the conversation. It’s letting yourself acknowledge that you already owe this person an apology before the conversation even begins.

Not a groveling apology. Not a guilt spiral that makes the conversation about your discomfort. Just an honest acknowledgment that you should have said this sooner and that you’re saying it now.

“I’ve been sitting with some concerns for a while and I should have brought them to you sooner. I want to have an honest conversation today.”

That sentence does a lot. It models the exact behavior you’re asking them to trust. It names the gap without making excuses for it. And it signals that what follows is real, which is the one thing they most need to believe.

Next week we’re getting into something that might feel like the opposite problem: the leader who says everything and means none of it. We’re calling it Vision Drift, and if you’ve ever sat through a quarterly planning session and wondered whether the leadership team is actually committed to any of it, that one’s for you.

You’re reading the Calm Authority paid post for Gutsy Leaders. Free essays publish at 7 AM on Tuesdays. This post goes out to paid subscribers. If someone forwarded this to you and you want the full archive, you can upgrade below.

The Ambient Firing (n.) The gradual, conversation-free removal of a person from meaningful work, accomplished through a series of subtle exclusions, smaller rooms, and increasingly irrelevant responsibilities, executed in the hope that they will eventually dematerialize from the org chart without anyone having to say a difficult sentence out loud. Technically, they still work there. Functionally, they’ve been managed to the margins so efficiently that the word “fired” would actually be a compliment, because at least that would have required someone to look them in the eye.

I’ve been in this field long enough to have watched a lot of hard things happen to good people.

Performance reviews that didn’t match reality. Promotions that went to the wrong person.

Toxic cultures that stayed toxic because nobody wanted to be the one to name it.

I’ve seen a lot.

But the ambient firing might be the thing that bothers me most. Maybe because it’s so quiet. Maybe because the person it’s happening to usually knows something is wrong before they can prove it, which puts them in this awful position of second-guessing their own instincts about their own career.

Maybe because the leader doing it almost always tells themselves they’re being kind.

They are not being kind.

I want to tell you about a woman I’ll call Renata. She’d been with her organization for almost seven years. Good at her job. Trusted. The kind of person who actually made things work rather than just talking about making things work, which turns out to be rarer than you’d think.

When the new VP came in, he met with everyone on the team. He was warm. He was thoughtful. He said all the right things.

And then, over the next several months, Renata noticed she was on fewer emails. A project she’d been leading got quietly reassigned. She was moved from a steering committee to an “advisory” role, which meant she received meeting notes afterward. Her one-on-ones moved from weekly to monthly and then started getting rescheduled.

Her title didn’t change. Her badge still worked. Nobody said anything to her directly. She just kept getting smaller.

It took her close to a year to put the full picture together, and by then she’d already started looking for another job, which was probably the intended outcome all along.

If you’ve been Renata, you know how disorienting that experience is. You can feel something happening, but because nothing has been stated, you can’t respond to it.

You don’t know if you’re being managed out or just overlooked. You don’t know if you should fight for relevance or read the room. The ambiguity is the whole problem, which is also what makes it cruel.

If this is resonating, you can subscribe here and get every issue delivered on Tuesdays.

Subscribe now

The thing that makes an ambient firing different from ordinary neglect is intention. Regular neglect is a manager who’s overwhelmed and not paying attention. The ambient firing is a manager who has made a decision and is hoping the consequences of that decision will unfold without their direct involvement. It is avoidance structured as a management strategy.

It is so very wrong.

And leaders who do this typically believe, sincerely, that they are sparing the person.

Which is also so very wrong.

They tell themselves they’re giving someone time to find something else. That this is gentler than a formal termination. That the person is smart and will figure it out.

What they’re actually doing is transferring all of the discomfort of their decision onto the person who is least able to carry it, and calling that mercy.

Every week the conversation doesn’t happen is another week that person is trying to function in a role that has been quietly hollowed out, without the information they need to make a real decision about their own life.

There’s also this: the person almost always knows. They feel the calendar gaps. They notice when their name stops appearing in conversations. They are reading the situation correctly, and then being gaslit by the silence into thinking maybe they’re not.

I have watched that erode people’s confidence in themselves in ways that follow them long after they leave.

I want to be honest here, because I know this isn’t always a story of a callous leader making a calculated choice. Sometimes it’s a good leader who inherited a hard situation and doesn’t know what to do. The conversation feels complicated. The relationship has a long history. Something more urgent keeps coming up. I’ve coached leaders in exactly this spot, and I know it’s rarely simple.

The direct conversation, even when it’s imperfect, gives someone the information they need to make choices about their own life. It respects them enough to be honest. The ambient firing takes that away and replaces it with months of quiet confusion, which is not a gift.

Renata left on her own terms eventually. She told everyone who would listen exactly what had happened. The VP probably thought it had all worked out fine.

The badge stopped working for him about eighteen months later, but that’s a different story.

If you recognize yourself in this as the leader, not Renata, the paid post this week is the one you need. I put together something I’m calling the Clarity Conversation: five specific moves that help you have the conversation you’ve been not having, in a way that’s honest without being brutal. There’s also a short diagnostic to help you figure out how far into ambient firing territory you’ve already gone, because sometimes we’re further along than we realize.

The hard conversation takes about twenty minutes. The alternative takes, apparently, about a year.

Get the Diagnostic and the 5 Moves Here

[Upgrade to the Paid Version to help you get out of this mess.]

Gutsy leadership isn’t about being fearless. It’s about being willing to say the thing that needs to be said, even when it’s uncomfortable, especially then. That’s a decision you get to make every single time.

You can make it differently. You can be a GUTSY Leader.

Gutsy Leaders publishes every Tuesday. Free essays at 7 AM. Paid companion posts for Calm Authority and Quiet Power Circle members at 8 AM.

This week’s word is Humility Hostage:

“…the compulsive redistribution of all credit and visible contribution to anyone in the room except yourself, performed with such consistency that the organization eventually takes you at your word and stops expecting you to have done anything in particular. The free essay is here if you want the full story first. Either way, you are in exactly the right place.”

This post gives you the diagnostic and the framework. Specifically, the five questions that will show you where the pattern lives in your day-to-day, and then a sequenced set of moves for starting to tell the truth about your own work without losing the values that made you worth following in the first place.

Let’s start with the audit.

The Humility Hostage Diagnostic

Before you can change a pattern, you have to see it clearly. And the tricky thing about Humility Hostage behavior is that it hides behind language that sounds virtuous. So this diagnostic is going to ask you to look at specific behaviors, not your intentions.

Answer from what you actually do, not what you mean to do or would like to do or believe you do in your better moments.

Pick the answer that is most honest, not the one that is most flattering.

Question 1

The last time someone senior praised a project you led, your response was closest to:

a) I named the specific people who contributed and what they each did, then said something brief about my own role. (0 points)

b) I said something like “thank you, the team really came together on this one.” (1 point)

c) I deflected entirely to the team and said something like “honestly it was all them, I just kept things organized.” (2 points)

d) I felt uncomfortable and changed the subject or minimized the whole project. (3 points)

Question 2

When you describe a decision you made to a peer or a leader above you, you most often say:

a) “I decided to go with this approach because...” (0 points)

b) “We landed on this approach, and I was the one who pushed for it.” (1 point)

c) “We kind of collectively landed on this.” (2 points)

d) “The team came up with this.” (3 points)

Question 3

Think about the last three times you started a sentence about your own contribution at work. How many of those sentences included the word “just”? As in “I just made sure everyone had what they needed” or “I just connected some dots.”

a) Zero times. I removed “just” from those sentences a while ago. (0 points)

b) Once, and I noticed it. (1 point)

c) Twice, and I am noticing it now for the first time. (2 points)

d) All three, and honestly I had not thought about it until right now. (3 points)

Question 4

Your annual review is coming up. If you had to write your own list of contributions from the past twelve months right now, without asking anyone else what they remember you doing, you would:

a) Have a clear, specific list ready. I track this. (0 points)

b) Remember the big things but struggle with the details. (1 point)

c) Have a vague sense but feel uncomfortable claiming things specifically. (2 points)

d) Genuinely not know what to write, partly because I have been describing my contributions as “the team” for so long I am not sure what was mine. (3 points)

Question 5

When you imagine naming your own contribution out loud, in front of someone senior, in a clear and specific sentence, your first instinct is:

a) That sounds fine. I do that. (0 points)

b) A little uncomfortable, but I can do it. (1 point)

c) It feels like bragging and I worry about how it will land. (2 points)

d) It makes me want to immediately add a qualifier, credit someone else, or change the subject. (3 points)

Scoring

Add up your points and find yourself below.

0 to 3: You are giving credit accurately, including to yourself. The framework below will sharpen instincts you already have.

4 to 8: The pattern is present but not entrenched. You are underselling yourself in specific situations, probably when the stakes feel higher. The framework will help you see exactly where it is happening.

9 to 12: You are a practicing Humility Hostage. The behavior is consistent and the organizational cost is real, even if it is not fully visible to you yet. Do not skim what follows.

13 to 15: You have been erasing yourself so thoroughly and for so long that you may have lost track of what you have actually built. That is fixable, and this is where we start.

The Accurate Voice Framework

I want to name what this framework is not before I tell you what it is, because the fear of becoming a Credit Hoarder is exactly what keeps Humility Hostages stuck.

This is not a permission slip to overclaim. It is not a plan for performing confidence you do not feel. It is not a suggestion that you stop crediting your team or minimize what other people contributed. If you take anything from this framework and use it to hoard, you have missed the point entirely and you should go back and read last week’s issue again.

What this framework is: a structured way to tell the truth. Accurately. About everyone, including yourself.

The moves below are just different applications of that one principle.

Move 1: Audit the “just”

Before you can replace the behavior, you have to hear it. For the next two weeks, every time you describe your own work to anyone, listen for the word “just.” Write it down if you need to. “I just held it together.” “I just made sure the timeline stayed on track.” “I just kept an eye on the budget.”

You are not trying to stop yourself in the moment yet. You are building awareness first, because most Humility Hostages have been using “just” as a minimizer for so long that they genuinely cannot hear it anymore.

Once you have found it, the replacement is simple. Remove the word. That is the entire edit.

“I just held it together” becomes “I held it together.”

“I just kept an eye on the budget” becomes “I managed the budget.”

You will notice that the second version sounds uncomfortably direct at first. That discomfort is information, not a reason to add the word back.

Move 2: Write the contribution before the meeting

This is the move that the man from the free essay used, and it is the one I recommend most often to coaching clients because it works before the anxiety of the room kicks in.

Before any executive presentation, skip-level meeting, performance conversation, or any interaction where your work might come up, write down three things you personally decided, drove, or built in the past month. Not the team’s things. Your things. Three sentences, specific enough that a stranger could understand what you did without further explanation.

Then find a way to say one of them out loud in the room.

Not all three. One. The goal is not a highlight reel. It is one accurate sentence, spoken clearly, in your own voice, without qualifiers.

If the sentence wants to end with “but the team really did most of it,” let it end before that part.

Move 3: Use the And Construction

The Humility Hostage’s default sentence structure is either “I did X” (which feels like bragging and gets softened) or “the team did X” (which erases you entirely). The And Construction gives you a third option.

It sounds like this: “[Name] did X, and I built the conditions that made X possible.”

Or: “[Name] led the client relationship, and I coached her through the conversations that almost fell apart in week three.”

Or: “The team delivered on the timeline, and I was the one who held the boundary when leadership pushed for early delivery in week two.”

The And Construction does not choose between you and your team. It tells the truth about both. The contributor gets named specifically. You get named specifically. Neither person disappears from the sentence.

This takes practice because it requires you to know, concretely, what you actually contributed. If you find yourself unable to complete the second half of the And Construction, that is useful data. It means you need to spend more time noticing your own contributions in real time, before they get attributed elsewhere.

Move 4: Name the decision, not just the outcome

Humility Hostages tend to describe outcomes and skip the decisions that produced them. “The project shipped on time” is an outcome. “I made the call in week four to drop two features so the core product shipped clean” is a decision, and it is a very different sentence.

Decisions are where your leadership actually lives. Outcomes are what happened.

When you describe only outcomes and credit them to the team, you are not lying, but you are telling a version of the story in which you do not appear to have done very much.

Start noticing your decisions. Write them down when they happen. Not every micro-decision, but the ones where you assessed a situation and chose a direction and accepted responsibility for the result. Those are yours. They belong in the sentence.

Move 5: Sit with the discomfort instead of editing around it

Every time you are about to add a qualifier, deflect to the team, or shrink a sentence, pause for one beat and ask yourself: is what I am about to say more accurate or less accurate than what I just thought?

If it is less accurate, say the more accurate version. Even if it is uncomfortable. Even if you have to stop and breathe first.

This sounds small. It is not small. The Humility Hostage pattern is maintained, one sentence at a time, by choosing the smaller version of the truth every time the choice comes up. Breaking it works the same way. One sentence at a time. One moment where you did not shrink.

Over a quarter, that compounds into something an organization can see.

A note on what is underneath this

If you scored in the 9 to 15 range on the diagnostic, I want to say something directly to you before you close this post.

The pattern you have been running is not a character flaw. It is a response that made sense at some point, probably in an environment where staying small was actually safer than being seen. The problem is that you carried it into a context where it is no longer protecting you, it is just costing you.

You are not going to fix this by deciding to be more confident. Confidence is downstream of clarity, and clarity comes from practice, specifically the practice of saying accurate things out loud in real situations until your nervous system learns that the worst-case scenario you are anticipating does not actually happen.

It takes longer than a week. Sometimes it takes coaching. I’d be honored to be your coach and in your corner. Let’s roll play. Let’s practice this outloud. Click here to land on my calendar so we can see if coaching is a fit for you.

Next week

Coming Tuesday: the leader who is not missing from their own sentences. They are present in all of them, at full volume, at all times, whether or not it is their turn. The condition does not have a clinical name yet, but it will by 7am.

Share

And then they left anyway.

Here’s what may surprise you: retention isn’t an HR problem. It’s a leadership problem. And most leaders are solving the wrong one.

In this live conversation with the brilliant Heather Ioerger, Dr. Linda Travelute breaks down what it actually means to lead like a CEO — the kind of leader people choose to stay for. Not because the snacks are good. Not because of the flex Fridays. But because the culture you’ve built makes them feel like they’d be crazy to leave.

We’re talking about the invisible architecture of teams that stick — and what’s quietly dismantling yours if you’re not paying attention.

Watch this if you manage people. And definitely watch it if you’re losing them.

Get more from Dr. Linda Travelute in the Substack app

Available for iOS and Android

Get the app

His name was not on the slide. I noticed that before he did. The director was presenting to the executive team, a capabilities overview, clean deck, sharp talking points, and she kept saying “the team” the way people say “the team” when they mean a specific person and cannot quite bring themselves to name him. Brain fog? Not quite.

“The team developed the approach.” “The team caught the risk in week two.” “The team really delivered on this one.”

After the meeting, I pulled him aside. “You built that framework,” I said. “The whole thing. You know that, right?”

He shrugged. “It was really a team effort.”

It was not a team effort. I had watched him build it. I had watched him stay late, rework the model twice, and talk the director off a ledge in week four when the timeline almost collapsed. He was the framework, he just could not say that out loud in front of anyone who mattered.

Six months later, the director got promoted. He got a very sincere thank-you card.

He still has it. The thank you card.

Last week we talked about Credit Hoarding Disorder, the compulsive need to absorb all visible wins into one’s personal brand until the team exists only as a backdrop. If you recognized someone you have reported to in that description, you were not alone. My inbox proved it. Thanks to those of you connecting with me on this.

But Credit Hoarding Disorder has an inverse. A twin, raised in a different house, with completely opposite symptoms.

This week’s word that should exist is Humility Hostage.

If you are a Humility Hostage, something probably just landed in your chest. Maybe not a full recognition, more like a low-grade, vaguely uncomfortable feeling that the definition is about someone you know very well.

That is because this pattern is hard to see from the inside. From the inside it looks like virtue, servant leadership, and the right way to operate, because at some point you absorbed the message, from a boss or an organization or a bad experience with someone who was genuinely arrogant, that claiming credit is the same thing as being arrogant, and being arrogant is the worst thing you can be, and so the safest version of you is the one that never takes up too much space.

The hostage-taker, in other words, is a value. A real one that got overcooked. And now it runs the show.

I want to talk about the word “just” for a minute, because I think it is the clearest signal of this pattern, and most people who use it this way have no idea they are doing it.

“I just kind of held it all together.” “I just kept things moving.” “I just made sure everyone had what they needed.” “I just connected the dots.”

The word “just” in all of these sentences is doing the same thing. It is taking a real, significant contribution and sandpapering it down until it sounds accidental. Until it sounds like something that happened in the background, automatically, requiring no particular skill or judgment or effort.

You held a nine-month initiative together through two leadership transitions and a budget cut. You did not “just” anything.

Stop using it.

The sentence you actually need is two words shorter and considerably more accurate: “I held it together.” Fourteen fewer qualifiers. Zero loss of humility. Full presence of truth.

I catch myself doing this sometimes and it is startling when I notice it, because I know better and I still do it anyway. There is something in the wiring that keeps reaching for the smaller version of the sentence.

The team credit deflection is its own variation of this, and it is trickier to see because it genuinely looks like good leadership from the outside.

“The team really showed up on this one.” And they probably did. Teams that show up usually have a leader who made showing up feel safe and worthwhile, and that is not a coincidence, and it is also information that is quietly disappearing from that sentence.

There is a version of crediting your team that includes you.

“Dana led the client relationship and I built the conditions that made her confident enough to do it” is a sentence that contains two people, two contributions, and zero false modesty. It does not shrink Dana to elevate you. It does not erase you to elevate Dana. It tells the truth about what actually happened, which is that two people did two different things and both of those things mattered.

The Humility Hostage version skips the second half of that sentence because naming your own contribution feels, every single time, like it is going to come across as something it is not. So you leave it out. And then you leave it out again. And again. And eventually a director gets promoted and you get a thank-you card, and you frame it, which is very kind of you…and also beside the point.

Here is the thing I want to name, because I think it matters more than the behavioral stuff.

If I never put my name on the outcome, I cannot be blamed when the outcome turns out to be more complicated than the slide made it look.

If I stay in the background, I stay protected. The background is a very comfortable place to stand. Nobody can evaluate you there.

The problem is that the background is also where careers go to plateau.

This is the part that I think deserves a moment, because I see it constantly in coaching and I do not think people are naming it directly enough.

The Humility Hostage is often incredibly skilled. They are frequently the most competent person in the room. And they have constructed a very sophisticated system for making sure nobody has to reckon with that, which protects them from the vulnerability of being truly seen and also, not coincidentally, from the possibility of being truly advanced.

It is anxiety.And it makes complete sense. And it is costing you.

You do not have to become a Credit Hoarder to stop being a Humility Hostage. Those are not the only two options, even though they can feel that way.

There is a third option, which is just accurate.

It names the team’s contribution and it names yours. It tells the truth about who did what without inflating anyone and without erasing anyone. It is a factually correct sentence about what actually happened and who was responsible for it.

The people above you cannot advocate for a contribution they cannot see. Read that again. Please.

You are the only one with a clear view of what you actually built. If you keep the curtains drawn, they will assume there is nothing worth looking at.

There is something worth looking at.

You are just going to have to be the one who says so.

The paid companion post for this issue has a five-question diagnostic that will show you exactly how deep the Humility Hostage pattern runs and what is underneath it, plus the framework I use with coaching clients who are structurally excellent at their jobs and organizationally invisible. Specifically the part about how to start telling the truth about your own work without losing the values that made you good at this in the first place.

If any part of this issue made you think of yourself and not just someone you know, that is probably the post you need.

Subscribe below if you want it.

Subscribe now

He sent me a message a few months after that conversation. He had started doing one small thing differently.

His director asked him two months later if he was ready for more responsibility.

He was. He had been for a while.

He just had not told anyone.

The paid companion post for this issue has a five-question diagnostic that will show you exactly how deep the Humility Hostage pattern runs and what is underneath it, plus the framework I use with coaching clients who are structurally excellent at their jobs and organizationally invisible. Specifically the part about how to start telling the truth about your own work without losing the values that made you good at this in the first place.

Subscribe now

You are not going to fix this by deciding to be more confident. Confidence is downstream of clarity, and clarity comes from practice, specifically the practice of saying accurate things out loud in real situations until your nervous system learns that the worst-case scenario you are anticipating does not actually happen.

It takes longer than a week. Sometimes it takes coaching. I’d be honored to be your coach and in your corner. Let’s roll play. Let’s practice this outloud as I walk you through the framework one-on-one. Click here to land on my calendar so we can see if coaching is a fit for you.

If you did not, the short version: there is a pattern where high-performing leaders take credit that does not strictly belong to them, almost always without noticing, and the cost is paid by the team in quiet, irreversible disengagement.

What follows is the audit and the framework. The audit will tell you where you sit on the spectrum. The framework is what to do once you know.

I will warn you. The audit is uncomfortable. It is supposed to be. If you sail through it feeling great, you either scored a zero (rare) or you are doing the exact thing the audit is designed to catch. Sit with it.

The Credit Hoarding Audit

Five questions. Answer honestly. The scoring key is below.

1. In the last 30 days, when describing a team win to a senior stakeholder, how often did you name specific contributors? a) Every time (0) b) Most of the time (1) c) Sometimes (2) d) I mostly said “the team,” “we,” or “my group” (3)

2. When your team delivers something impressive, the first thing you feel is:

a) Pride in them (0)

b) Pride in yourself for building or leading them (1)

c) Quiet anxiety about whether you will get credit for it (2)

d) Calculation about how to frame it in your next update (3)

3. The last time someone senior praised your team’s work, you: a) Named specific contributors immediately (0)

b) Said “thank you, the team worked really hard” (1)

c) Accepted the praise and moved the conversation along (2)

d) Elaborated on your role in the outcome (3)

4. When you retell a recent win in your head, who is the protagonist of the story? a) A specific team member (0)

b) The team collectively (1)

c) You, with the team somewhere in the supporting cast (2)

d) You, and you cannot quite remember who else was in the room (3)

5. If your top performer left tomorrow and you had to explain to your boss what they actually contributed this year, you could: a) Give a specific, accurate breakdown of their wins (0)

b) Hit the high points (1)

c) Give a vague but appreciative summary (2)

d) Need to ask around first (3)

Scoring

0-3, Light fingerprints. You give credit generously and specifically. Your team trusts you. The framework below will refine an instinct you already have.

4-7, Habitual borrowing. You are not actively hoarding, but pronouns slip and names blur in front of leadership. This is fixable in a quarter with attention.

8-11, Active hoarder. Your kudos warehouse is full and your team is noticing. The Open Ledger work below is for you. Do not skim it.

12-15, Acute Credit Hoarding Disorder. The team has stopped bringing you their best work, even if you have not yet noticed. Read this twice. Read it again next week.

The Framework: The Open Ledger

The opposite of a warehouse is a ledger. Warehouses are private. Ledgers are visible. The point of the Open Ledger is not to perform humility (please do not perform humility, it reads worse than hoarding). The point is to attribute work accurately, in public, in a way that strengthens both the contributor and you.

The Open Ledger has four moves and one phrase.

Move 1: Name.

Specificity is the entire game. “The team did great work” gives the team nothing. “Priya led the redesign and made the call to scrap the original API approach in week two, which is the only reason we shipped on time” gives Priya everything.

Senior stakeholders remember names. They do not remember “the team.” When you name names in front of leadership, you are not just crediting Priya. You are building Priya’s reputation with people who have promotion power, which is what real leadership looks like from the outside.

If you cannot name a specific contributor for a specific decision, you do not know your team’s work well enough yet. Go find out before your next executive review.

Move 2: Sequence.

When you tell the story of a win, the contributor’s work comes first. Your role comes second. This sounds simple. It is not.

The hoarder’s default is to lead with their own framing (”I had the team work on...”) which puts the leader in the protagonist position by sentence structure alone, before anyone has said anything substantive.

The fix is grammatical. Lead with the contributor. “Marcus rebuilt the onboarding flow over a brutal two weeks. I cleared three meetings off his calendar so he could focus.”

Now Marcus is the protagonist. You are still in the story, accurately, but you are not pretending the flow rebuilt itself while you were nearby.

Move 3: Witness.

Credit redistributed privately is not redistributed. It is still hoarded, just whispered. The Open Ledger requires you to do the naming and sequencing where it actually costs you something: in front of your peers, in front of leadership, in writing, on the record.

The test is simple. Did the person whose work you credited hear about it from someone other than you? If yes, you did it right. If no, you did it in a closet.

Move 4: Hold.

This is the hardest move and the one most leaders skip. After you have named, sequenced, and witnessed, hold the credit there. Do not take it back in the next conversation. Do not re-narrate the win three weeks later with yourself at the center. Do not let the warehouse quietly refill while no one is looking.

Holding is mostly an internal discipline. You will feel the urge to re-claim. You will catch yourself, in a hallway conversation, drifting back into “I” language about Priya’s redesign. That moment, where you notice the urge and do not act on it, is the actual work of recovery.

The Phrase

“X did the work. My job was Y.”

That is it. Six to twelve words depending on how you fill it in.

It does three things at once. It credits X specifically. It clarifies your actual role accurately, because senior stakeholders do want to know what you did, and self-erasure is its own kind of dysfunction. And it signals to everyone in earshot that you are a leader who can tell the difference between those two things in real time.

A few in the wild:

“Priya led the redesign. My job was to keep the executive sponsors out of her way until it was done.”

“Marcus rebuilt the onboarding flow. My job was to defend his timeline when sales pushed back in week three.”

“The launch was Dana and Ben’s call from week one. My job was to make sure they had what they needed, and to take the heat when it almost did not ship.”

Notice what the phrase does not do. It does not say “I had nothing to do with it.” It does not erase you. It does not perform false modesty. It tells the truth about who did what, in the right order, in front of the right people.

The phrase is small. The compounding effect over a year is enormous. Teams notice within a week. Senior stakeholders notice within a quarter. And the warehouse, slowly, starts to empty out.

Next week

Tuesday’s word is the inverse condition. The leader who over-credits the team to the point of disappearing themselves, then quietly wonders why they keep getting passed over. Yes, this is also a dysfunction. No, the cure is not “hoard more.” The cure is something else, and it has its own name.

For this week: pick one win from the last 30 days. Use the phrase. Tell me in the comments how it lands.

Share

Then her CMO leaned in and said, “Tell us more about what you did.”

And she did. For seven full minutes.

I watched her senior director’s face shift from proud to puzzled to that flat, careful expression people get when they are quietly deciding whether it might be time to update their LinkedIn.

Her team had done most of that work. We had walked through every contributor the week before in our coaching session. She knew. She knew that she knew. And still, the moment the spotlight swung her way, her hands closed around every accomplishment in the room like she was afraid someone might come take one back.

She was not lying, she was not even exaggerating. She was doing what high-performing leaders have been quietly conditioned to do for their entire careers: collect every win, file it under “me,” and store it somewhere safe in case she ever needs to prove she belongs in that room.

She has Credit Hoarding Disorder.

(That suspicion, by the way, is half right. There is a scoreboard. It just is not measuring what you think.)

Here is the hard part. Once you see Credit Hoarding Disorder, you will see it everywhere. You will spot it in your boss. You will spot it in the peer whose name somehow lands in every leadership offsite recap.

You will spot it in your own mouth on a Wednesday afternoon when your VP asks how the launch went and the word “I” comes out of you with a confidence that, on closer inspection, is not entirely earned.

The pattern shows up in three places. Buckle up.

She uses “I” when the work was a “we.”

The story gets retold and the pronouns quietly migrate. The team led the workstream. The team made the calls. The team stayed late on a Sunday no one will remember by Friday. But by the time the story reaches the executive review, the leader is the protagonist and everyone else has been demoted to extras with no speaking lines.

Note. This is rarely conscious. It is, more often, the auditory equivalent of muscle memory. The pronouns do not even ask permission. They just go.

She thanks “the team” without naming a single human being.

Generic gratitude is the polite cousin of credit hoarding.

Yes, read that again. Please.

It looks like acknowledgment. In the moment, it even feels like acknowledgment. But anyone who has ever been part of “the team” knows the difference between being thanked and being named.

Share

Vague praise costs the leader nothing and gives the team nothing back. It is a participation ribbon worn by no one in particular, and it leaves the people who actually did the work doing math in their heads about how much of their best effort they want to bring to the next quarter.

She is the hero of every story she retells.

Not in the obvious way, nor in a single-handedly-closed-the-deal way. In a softer, more insidious way.

The pivot was her idea.

The save was her instinct.

The breakthrough came in a meeting she happened to be running, where her question, asked at just the right moment, unlocked everything.

By the third retelling, she is at the center of the story.

By the tenth, no one else is in the room.

The team members who were there in the original version have been quietly written out, the way old photos get cropped before they get framed.

The cost of all this is not subtle, even when the behavior is. People notice. They always notice. They notice when their name does not show up in the recap. They notice when “we” shrinks to “I” the moment leadership walks in. They notice when the win they spent three weekends on becomes a story about somebody else’s vision. Ouch.

What they do about it is the part that should worry every credit hoarder more than it does.

They do not confront, they do not push back, they do not write a strongly worded email. They simply, quietly, begin to do the smallest acceptable version of their job.

What’s the harm?

They stop bringing the ideas. They stop staying late. They stop volunteering for the cross-functional thing that is going to be brutal but career-defining. They give the leader exactly what is asked for and nothing more.

And the leader, deep in the warehouse of stored accomplishments, never quite figures out why the team’s output started flattening around the same time everyone stopped looking them in the eye.

The cruel irony of Credit Hoarding Disorder is that it produces the opposite of what it is trying to produce.

The leader hoards credit because they want to be seen as a high performer.

The hoarding makes them a worse performer.

The team’s discretionary effort dries up.

The pipeline of future wins thins.

The leader, sensing scarcity, hoards harder.

And the warehouse grows, and the work shrinks, and somewhere down the line a senior director updates her LinkedIn.

In tomorrow’s paid post, I am sharing the Credit Hoarding Audit. Five questions, scored, that will tell you with uncomfortable precision where you sit on this spectrum (yes, there is a spectrum, and yes, you are on it somewhere).

Plus the framework I walk clients through to redistribute credit in a way that does not feel performative or like you are auditioning for a best-in-leadership magazine, including the one phrase that rewires how your team experiences your leadership in front of senior stakeholders.

If you have ever sat in a meeting and realized halfway through that you have been saying “I” for ten minutes about work that was “we,” this one is for you.

Credit is not a finite resource. The committee you imagine is watching is not the committee that decides anything. And the warehouse, in the end, is just a room full of stories no one but you remembers.

Get the Credit Hording Audit plus the Framework by becoming a paid subscriber below.

Subscribe now

If you came in from yesterday’s free essay, you already know what the Authority Refund is. If you did not, here is the short version.

This post is the audit and the framework. The audit tells you how much of your week is currently being eaten by accepted refunds. The framework tells you what to do about it without making your team feel rejected, micromanaged, or set up to fail.

Pour the coffee.

The Counter Clerk Audit

Five questions. Score each one. Add them up at the bottom.

1. In the last two weeks, how many times has a direct report asked you to weigh in on a decision that was already inside their job description?

• 1 — Once or twice. Maybe.

• 2 — A handful. I noticed.

• 3 — More than I would like to admit.

• 4 — I am not sure I could count that high.

2. When someone says “quick gut check before I send this,” what is your most common response?

• 1 — I ask them what they think first, then we discuss.

• 2 — I give a yes or no, but I check in on the reasoning.

• 3 — I give a yes or no.

• 4 — I usually end up rewriting whatever they brought.

3. How much of your weekly calendar is currently dedicated to giving feedback on work you previously delegated in full?

• 1 — Less than 10 percent.

• 2 — Around 10 to 25 percent.

• 3 — Closer to half.

• 4 — Most of it.

4. When was the last time you said out loud, “You don’t need my approval for that, it’s your call,” to a direct report?

• 1 — Sometime in the last week.

• 2 — Sometime this month.

• 3 — Sometime this quarter.

• 4 — I am genuinely trying to remember.

5. If you went on vacation tomorrow with no phone, how many decisions would visibly stall in your absence?

• 1 — A handful, and they would survive a week without me.

• 2 — Quite a few, and someone would need a workaround.

• 3 — A lot. People would be waiting.

• 4 — I do not take phone-free vacations and now I know why.

Your Counter Position

5 to 8 — Authority Custodian. You handle decisions cleanly. Refunds get refused. You probably do not need the framework below, but you are welcome to use the language to coach the people around you who do.

9 to 12 — Casual Clerk. You accept the occasional refund, often the high-stakes ones. The pattern is manageable but not invisible. The framework below will tighten things up. Pay extra attention to step two.

13 to 16 — Senior Clerk. A meaningful share of your week is being eaten by decisions that are not yours to make. You are exhausted and slightly resentful, and you cannot quite name why. The framework below is for you. Read it twice.

17 to 20 — Counter Manager. You are not running a team. You are running a customer service desk for your own delegations. This is fixable, and it does not require a reorg. It requires three specific moves, repeated until the pattern resets.

The Return Policy

The mistake most leaders make when they finally notice the Authority Refund pattern is that they swing too hard the other way. They snap, “Why are you asking me this?” Or they go silent and let the team flail until trust evaporates. Both of those are versions of the same mistake. They treat refusing the refund as a one-time confrontation instead of a repeatable policy.

What you actually need is a Return Policy. Every store has one. Yours is going to have three steps.

Step 1: Read the Receipt

Before you respond, identify what is actually being asked. There are three categories.

The first is a real question. The team member has information you do not, and your input genuinely changes the outcome. Answer it. Move on.

The second is a refund. The team member has the information, the authority, and the capability. They are looking for cover. The language gives them away. “Quick gut check.” “Just want to make sure I’m not overstepping.” “Thoughts?” with no further context. These are not requests for information. They are requests for shared liability.

The third is a confidence check. The team member already knows what they want to do and wants to hear that you would do the same. This one is the trickiest, because

answering it feels supportive, but answering it consistently turns into refund acceptance over time.

You cannot run the rest of the policy without first naming which category you are looking at. Most leaders skip this step and go straight to answering. That is how they end up at the counter.

Step 2: Decline the Return

Once you have identified a refund, your job is to refuse it without making the person feel rejected. The trick is to send the decision back in a way that reads as confidence, not punishment.

Some language that works:

• “I trust your call on this. Tell me what you’re leaning toward and why.”

• “This one is in your lane. What are you thinking?”

• “You don’t need a yes from me on this. You need ten minutes to make the call.”

• “If I made this decision for you, I’d be doing your job. Yours is harder. Go do it.”

Notice what none of those say. None of them say, “I don’t have time.” None of them say, “Figure it out.” None of them say, “Why are you asking me?” Those phrases shame the team member and teach them to hide the next refund behind sneakier language. The goal is to refuse the return while affirming the person. Warm rebellion.

Step 3: Restock with Scaffolding

The refund-handing-back habit almost never resolves on the first refusal. Your team member did not develop this pattern overnight, and they will not lose it overnight either. What they need is a scaffold to lean on while the muscle builds.

A scaffold is not a decision made on their behalf. A scaffold is a small structure that helps them make the decision themselves. The two most useful scaffolds I give clients:

The first is the “what would you do if I were on vacation” prompt. Ask it sincerely. Then sit in the silence while they actually answer. Their first response will often be, “Well, I would probably ask Sarah.” Hold the silence. Their second response is usually the real one.

The second is the “give me your top two, ranked” prompt. Rather than asking what they think, ask them to present two options in order of preference, with one sentence on why. This forces a position. It also shifts the conversation from a refund request into a strategy discussion, which is the place where you actually add value.

Used together, these two prompts tend to retrain the pattern in about six to eight weeks. The team member starts answering their own question before they even open the Slack message. That is the win.

A note before I let you go

If you run this audit on yourself and the score is uncomfortable, do not run it on your team. Resist that. The Authority Refund is a pattern that organizations train people into, and most of your team did not invent the behavior. They learned it, often from leaders before you, possibly from you on a bad day. Pointing at them as the problem is the fastest way to skip your own role in maintaining the counter.

Next Tuesday we are going to look at the inverse pattern. The version where the leader never lets go in the first place, dresses it up as standards, and calls it leadership. There is a word for that one too.

See you on the other side.

A week later she is in your office asking whether the announcement should go out Tuesday or Wednesday. You say Tuesday.

Three days after that she is asking which of two subject lines is better. You pick the second one.

By Friday you have approved the hero image, the send time, the segmentation, and the name of the post-launch Slack channel.

You delegated the launch. You also planned the launch. Both things are somehow true.

If you are running your own company, the version is: you hired a strong operations lead, wrote her a generous job description, and are now personally choosing the welcome email subject line at 10pm on a Tuesday.

The story senior leaders tell themselves about this is much more flattering than what is actually happening. The version they tell is, “I have to be involved in everything.” Or the soft martyr classic, “I guess I just care more.” That version is wrong. What is actually happening at the doorframe of their office is a return.

You see it in the “quick question” that takes thirty minutes.

You see it in the email forwarded to you with the word “thoughts?” as the only body.

You see it in the deck someone built brilliantly and then placed on your calendar for “feedback” the day before it ships.

Every clear decision you made last month came back this month in a slightly smaller package, asking for a yes.

There is a name for this, although there should not have to be. I call it The Authority Refund.

Original packaging. Receipt enclosed. The customer service counter is your office. The clerk is you.

You signed for it without realizing you were signing for it, and now the authority you handed off three weeks ago is sitting on your desk asking what font you would prefer.

The reason this dysfunction does not have a name is that it does not look like dysfunction. It looks like a really good team member being thoughtful.

The genius of the Authority Refund is that the packaging is indistinguishable from competence.

A normal refund is visible. Someone walks up to the counter holding the item. Both parties know a transaction is taking place. The Authority Refund is invisible because the person returning the item never says, “I am returning this.” They say, “I just want to make sure I’m not overstepping.” Or, “Quick gut check before I send this.” Or, “I value your input so much, I want your eyes on this first.” Every one of those sentences is a receipt. And you keep signing them.

Do I have your number?

You’re not alone. Read on.

Senior leaders accept these refunds so readily because the refund flatters them.

A returned authority arrives looking like a vote of confidence.

Someone wants your eyes.

Someone trusts your judgment.

The dopamine of being needed is one of the most reliable drugs in any executive’s bloodstream, and the Authority Refund is its purest dose.

The first lie the Authority Refund tells is: this is faster.

It is faster for the person returning the authority. It is significantly slower for the person now downstream of every micro-choice in a project they thought they had handed off. One person saves five minutes. One person loses an hour. You can do this twenty times a week without noticing, and many of you do.

The second lie the Authority Refund tells is: this is alignment.

Alignment is when two people who hold separate authorities make sure they are pulling in the same direction.

The Authority Refund is when one person hands their authority back so they do not have to pull at all. Your team is not aligning with you. They are asking you to drive the car they were given the keys to last quarter.

The third lie the Authority Refund tells is: this is humility.

The team member who keeps checking in looks humble. They are asking, not assuming. They are deferring, not dictating. This reads, to most leaders, like the absence of ego. But this version of “humility” is doing something more specific.

It is unaccountability dressed up as deference. There is a difference between “I want to know what you think” and “I want you to think for me.”

The first deserves your time. The second is asking you to absorb a risk that was never yours.

What I want you to see is that you are not a bystander to this pattern. You are the counter clerk.

Every time you process a refund without questioning it, you teach the team that the counter is open.

The team did not build the counter. You did, one yes at a time.

In tomorrow’s paid post: a five-question audit to figure out how much of your week is being eaten by accepted refunds you did not realize you were accepting, plus the framework I use with executive coaching clients to send authority back across the counter without making your team feel rejected, micromanaged, or set up to fail. If you have been reading this with a slowly sinking feeling about your Friday afternoons, go ahead and pour the coffee.

Subscribe now

The keys were not yours to keep. They were not the team’s to hand back. The fact that the exchange feels polite is exactly why it has been working for this long.

That still moment is what we’re working with today.

What I’ve found, after years of working with senior leaders, is that the Highlight Reel Hostage pattern almost never gets addressed head-on. Leaders don’t walk into a coaching session and say “I’ve been hiding from reality for eighteen months.” They say things like “I feel like my team isn’t fully on board” or “I’m not sure the feedback I’m getting is accurate” or just “something feels off and I can’t name it.”

The something that feels off is usually this.

So before we get to the reset, I want to start with a diagnostic. Because the way out of this pattern requires knowing exactly how deep in you are. And most leaders, when they finally look honestly, are surprised by the answer.

The Highlight Reel Audit

Go through these questions slowly. Not quickly, not optimistically. Answer for how you actually operate, not how you want to operate.

Score each one on this scale: 0 = Never, 1 = Sometimes, 2 = Often, 3 = Almost Always.

1. When something isn’t working, I spend time figuring out how to frame it before I decide what to do about it.

2. I have made a decision to stay the course on something not because I believed it was the right call, but because changing direction would have required explaining myself to people who had already been told a different plan.

3. When a team member raises a concern about our direction, my first internal response is some version of “they don’t have the full picture.”

4. I find it easier to talk about challenges with people outside my organization than with the people inside it.

5. There is at least one thing I know right now that I have not yet said out loud to the people who need to hear it.

6. If someone asked my team to describe my biggest blind spot, I think their answer would surprise me.

7. The story I tell publicly about my organization and the conversations I have privately about my organization feel like two different things.

8. I can tell when someone in a meeting is managing me rather than telling me the truth, but I don’t call it out.

9. I have kept a struggling initiative alive longer than I should have because publicly shutting it down felt like too much to explain.

10. When I imagine being fully honest about where things actually stand, my first feeling is something closer to fear than relief.

What your score means

Add up your total and find your range below.

0 to 10: You are either genuinely not caught in this pattern, or you answered too quickly. I say that with warmth, not accusation. Take five minutes and go back through questions 5 and 10 specifically. Those two are the ones people undercount most.

11 to 20: You have some Highlight Reel Hostage tendencies that are worth paying attention to. The pattern is present but not entrenched. This is actually the best place to be doing this work, because you still have enough access to reality to be honest with yourself about it.

21 to 30: This pattern has real weight in how you’re leading right now. The good news is that you just did something most leaders in this range won’t do, which is answer honestly. That matters. Keep reading.

Now that you have a sense of where you are, here is the framework I use with clients to get out.

I want to be clear about something before we go through it. The goal of The Reel Check is not to blow up your credibility, confess your way through a board meeting, or perform some kind of public reckoning.

Leaders in the 21 to 30 range especially tend to think that getting honest means getting dramatic, and it doesn’t. The goal is to quietly, carefully restore your own access to reality, and then rebuild the conditions around you so that reality can actually reach you again.

That’s it. That’s what we’re doing.

The Reel Check: A Four-Part Reset

Part 1: Name the story you’ve been protecting.

This is the foundational step, and it’s harder than it sounds because the story is usually invisible to the person living inside it. What you’re looking for is the specific narrative you have been most committed to defending, the one that has quietly been making decisions on your behalf.

Some examples of what it might sound like when you name it: “I have been protecting the story that this team is performing at a high level.” Or “I have been protecting the story that we made the right call on this product two years ago.” Or “I have been protecting the story that I am the kind of leader who always has a plan.”

Sit with this until you can say it in one sentence. Write it down. The sentence itself is not the problem. The sentence is just the thing you’ve been carrying, and naming it takes some of its weight off you.

Part 2: Find where reality and the story have pulled apart.

Once you have the story named, you can start looking at where the evidence doesn’t match it. This step is not about cataloguing your failures. It’s about identifying the specific gaps that your narrative has been working hardest to paper over.

I ask clients to answer three questions here.

First, what do you know that you haven’t said?

Second, what has someone told you in the last six months that you dismissed faster than it probably deserved?

Third, if your most honest team member wrote you an anonymous letter about what’s actually going on, what would it say?

You don’t have to act on any of this yet. You’re just getting a clear picture of the gap.

Part 3: Reintroduce reality incrementally.

This is where most leaders try to skip ahead, and it almost always makes things worse. The instinct when you’ve been hiding from reality is to overcorrect, to call a meeting and say everything you’ve been holding back, to mistake disclosure for honesty. But that’s not honesty. That’s a different kind of performance.

What actually works is much quieter. You start by closing the gap in your own thinking first. You practice saying the true thing privately, to yourself or to one trusted person, before you say it publicly. You stop letting the reframe be ready before the admission is allowed.

Then, when you do speak it outward, you do it proportionally. A conversation before a meeting. A question before a declaration. You’re not hiding anymore, but you’re also not making your clarity everyone else’s crisis. Honest and dramatic are not the same thing, and your team does not need both at once.

Part 4: Rebuild the feedback loop.

Here is the hard truth about the Highlight Reel Hostage pattern: by the time a leader recognizes it, their team has usually already adapted to it.

The people around you have learned, through trial and error, exactly how much truth you can receive and how to package the rest so it doesn’t land wrong.

They did this to survive. You can’t be angry about it. But you do have to fix it.

Rebuilding a real feedback loop takes longer than most leaders want it to. It requires asking different questions and then tolerating the silence that follows while people figure out whether you actually want an honest answer.

It requires responding to hard feedback in a way that makes people want to give you more of it. And it requires you to do what the Highlight Reel Hostage almost never does, which is say out loud, in front of your team, something that is actually true even when it complicates the story.

You don’t have to fall on a sword. You just have to let people see that you can handle reality. Most of them have been waiting a long time to find out if you can.

When I work through this with clients, the shift rarely looks the way they expected. It’s not a dramatic transformation. It’s more like a gradual loosening, a slow return to their own judgment.

They start making decisions that feel right instead of decisions that feel safe.

They start having conversations they had been postponing.

They stop walking out of meetings with that low-grade exhaustion that comes from performing confidence you don’t actually have.

What they get back is not just honesty. It’s themselves.

That executive director from the free essay eventually did the work. It took time, and it was uncomfortable, and she had some hard conversations with her board. But she stopped performing the winning version of a struggling organization, and she started actually leading one. The organization is still running.

That’s what’s on the other side of this.

Gutsy Leaders is psych-savvy leadership for people who are done performing. Published every Tuesday.

I was sitting in a nonprofit board meeting once when the executive director pulled up a slide titled “Momentum Indicators.”

The organization had lost thirty percent of its major donors that year. Thirty percent. And she was showing us a slide about momentum.

She had clearly worked very hard on the framing. The word she kept using was “recalibration.” Strategic recalibration of the donor portfolio toward long-term sustainability.

She said it three times with a completely straight face, and nobody in the room pushed back, because nobody wanted to be the person who said out loud that you cannot pay staff salaries with long-term sustainability.

I’ve thought about that meeting a lot since then, because what I was watching wasn’t dishonesty. It wasn’t even denial in the way we usually mean it. It was something more specific, and honestly, something more heartbreaking.

She had spent years building a public narrative about what a visionary, thriving, mission-driven leader she was. That story lived in her annual reports, her keynotes, her donor letters, her LinkedIn posts.

And somewhere along the way, she had stopped being the author of that narrative and had become its prisoner.

She couldn’t see the thirty percent, because seeing it would have broken something she had worked incredibly hard to build.

So she reframed it until it fit the story she needed to tell. And the board, who had helped her construct that same story and repeated it at their own dinner parties, couldn’t see it either.

The whole room was full of hostages. Nobody had a key.

This is what I call a Highlight Reel Hostage.

This isn’t about spin, or strategic framing, or the very reasonable desire to not look incompetent in front of your board. Most leaders do some version of that, and it’s fine. The Highlight Reel Hostage is past all of that.

They’re not managing the message anymore. The message is managing them.

If this is your first time here, Gutsy Leaders is psych-savvy leadership for people who are done performing. I publish every Tuesday.

The thing that makes this pattern so hard to see from the inside is that it doesn’t start as self-deception. It starts as competence.

You learn early in your career that leaders are supposed to project confidence. You learn to process uncertainty privately and present publicly as a plan. You figure out that the board, the investors, the team, the donors, they all need to believe you know where you’re going, because if they stop believing that, everything gets harder.

So you get good at the framing. You get good at finding the right angle on a bad quarter, and it works, and so you do it again.

And then one day you realize you’ve been doing it for so long that you can’t turn it off.

There are three ways I see this show up, and I want to name them plainly, because the Highlight Reel Hostage almost never identifies the pattern in themselves. Someone else usually has to say it first.

The performance becomes the plan.

This is when a leader’s actual strategy stops being about outcomes and starts being about protecting the story.

Decisions get made not because they’re the right call, but because they’re consistent with the narrative that’s already been published.

A pivot that would save the organization gets shelved because they announced this direction six months ago and people are watching.

A struggling product stays on life support because it’s featured in the deck that just went to the board.

When you’re a Highlight Reel Hostage, the story you told last quarter has veto power over the decision you need to make today.

Feedback becomes a threat assessment.

Every piece of input from the team gets evaluated not on its merits, but on whether it threatens the narrative.

The team member who raises a concern isn’t someone with useful information, they’re someone who “doesn’t understand the big picture.”

The client who churns isn’t a signal, they’re “not the right fit for where we’re going.”

A dissenting voice in a meeting doesn’t get engaged with. It gets managed.

Over time, the people around a Highlight Reel Hostage learn to give their feedback in ways that don’t threaten the story.

Which means the feedback stops being useful. Which means the story becomes the only thing left. Danger Danger.

Reality develops a two-week delay.

This one is subtle and I really want you to sit with it. When a Highlight Reel Hostage knows something is wrong, there’s a gap between when they know it and when they can officially know it.

Because before they can acknowledge reality, they need time to figure out how to frame it. T

he problem can’t just be a problem. It has to be “a challenge we’re navigating proactively” or “an area of strategic focus” or “something we identified early.”

The devastating irony here is that the leaders most likely to become Highlight Reel Hostages are usually the ones who built genuinely impressive things.

You don’t develop a narrative worth protecting if you haven’t done real work. You don’t become a hostage to a story nobody believed. The trap is built from your own accomplishments, and the lock is made of other people’s expectations.

I think about that executive director often. She wasn’t a bad leader. She was talented and driven and had built something real. But she had been telling the winning version of her story for so long that she couldn’t access any other version.

And the organization couldn’t afford for her to stay that way.

The moment I’ve seen leaders break out of this pattern is almost never dramatic. It’s not a public reckoning or a board intervention. It’s usually quiet, and usually private, and it almost always starts with some version of: “I think I’ve been telling myself a story.”

That sentence is the key. That sentence is the whole thing.

If this one is sitting with you, the paid post this week goes further. I’m walking through the exact process I use with clients to audit their own highlight reel, including the questions that help you figure out whether you’re framing reality or hiding from it, and a four-part reset for getting back to honest leadership without blowing up the trust you’ve already built. It’s called The Reel Check.

Access The Reel Check → Calm Authority & Quiet Power Circle with the Paid Tier.

Subscribe now

Gutsy Leaders is psych-savvy leadership for people who are done performing. Published every Tuesday.

Here’s this Week’s Word That Doesn’t Exist - But Should

What I want to do in this post is give you something concrete to work with. Naming a pattern is only useful if you can actually see it operating in your own context, so we’re going to start with an audit.

A way to look at your own recent decision-making and find out where the visibility tax is being collected on your team and by how much.

Then we’ll get into the framework, which is three structural shifts that interrupt the proximity default before it costs someone else an opportunity.

I’ll warn you upfront: the audit is the part that requires honesty. Not the brutal, self-flagellating kind, just the quiet clear-eyed kind where you look at what’s actually been happening rather than what you intended to happen.

Those two things are often pretty different, and the gap between them is where all the useful information lives.

The Visibility Tax Audit

For this to work, you need to think about a real window of time. The last 60 to 90 days is ideal because it’s long enough to see a pattern and recent enough that you can actually remember what happened.

Give yourself a score for each one:

0 if this almost never describes you

1 if it sounds familiar sometimes

2 if you recognize this happening regularly

3 if this is honestly how you operate most of the time

Section 1: How opportunities actually get distributed

• In the last 60 to 90 days, when a project or opportunity came up that I needed to hand off quickly, I chose the first person who came to mind rather than pausing to consider my full roster of options.

• When a senior leader or external contact asked me to recommend someone from my team, I named someone I’d interacted with recently rather than thinking systematically about who was actually best suited.

• If I look at the stretch assignments and high-visibility work from the past quarter, the same two or three names appear on most of them.

• I can think of at least one team member who has strong performance but hasn’t been tapped for anything significant in the past few months, and I don’t have a clear reason why.

Section 2: Who has access to you

• The people who reach out to me informally tend to be the same people over and over.

• My remote or hybrid team members interact with me primarily through scheduled meetings, while my in-person team members have more unstructured access to me throughout the week.

• Certain team members feel easy and natural to think about, and others I have to make a deliberate effort to remember to check in with.

• When I think about who I’d describe as my strongest performers, I’d have a hard time separating their actual output from how much I enjoy our interactions.

Section 3: How quiet and remote employees experience your leadership

• I have team members who do excellent work but rarely speak up in group settings, and I honestly don’t have a strong read on their ambitions or what they want to grow into.

• If I asked my most introverted team member whether they feel like they have fair access to opportunities, I genuinely don’t know what they’d say.

• My remote employees would describe our relationship as primarily transactional because we connect for work tasks but I don’t have much visibility into who they are beyond their deliverables.

• I’ve described a team member as “a little hard to read” or “not very visible” in a performance conversation, when the more accurate thing might have been that I hadn’t made enough effort to see them.

What your score tells you:

Add up your totals across all three sections.

0 to 10: Your proximity bias is relatively low, or you’ve already built habits that counteract it. The framework below will help you make sure what you’re doing is intentional rather than accidental.

11 to 20: You’re in the middle range, which is where most conscientious leaders land. You’re not running a Derek-only show, but there are real patterns here worth addressing. At least one or two people on your team are absorbing more of this tax than you realize.

21 to 30: The visibility tax is operating at a meaningful level in your leadership, and the people paying it have probably already noticed something feels off even if they can’t name it. The good news is that you’re here reading this, which means you’re already ahead of most leaders who never examine this at all. Start with the first shift in the framework because it creates the fastest visible change.

31 to 36: This is high, and I want to say something to you directly before we get into the framework.

The fact that you answered honestly matters more than the score itself. A lot of leaders would have scored themselves lower by answering aspirationally. You didn’t, and that’s the thing that actually makes change possible.

Take the audit results into your next one-on-one cycle and use them as a listening agenda. You’ll learn more in those conversations than from anything else I could give you here.

The framework is below. Three structural shifts, each one targeting a different part of the audit, each one designed to work in real leadership conditions when you’re busy and decisions happen fast and your brain is still going to default to proximity if you let it.

The Visibility Tax Return: Three Structural Shifts

I want to be clear about what these are and what they aren’t. These are not reminders to be more mindful or intentions to try harder. Those are useful for about four days and then the default takes back over.

What actually works is building something into the structure of how you operate so that the proximity default gets interrupted before it makes a decision for you.

Think of it like setting up automatic contributions to a retirement account. The reason that works for people isn’t willpower, it’s that the decision happens before the moment of temptation. These three shifts work the same way.

Shift One: The Opportunity Roster

The reason Derek keeps getting tapped for things isn’t that you’re consciously choosing Derek. It’s that Derek is who surfaces when you need someone fast, and fast is how most real opportunities get distributed.

The fix isn’t to think harder in those moments. It’s to do the thinking before those moments arrive.

Not whether they’re ready for any specific thing, just whether they’re genuinely in your field of consideration.

Anyone who isn’t, and there will be people because this is normal, gets a note next to their name.

What would they be right for?

What are they ready for that they haven’t had a chance to try yet?

What do you not know about their ambitions that you should find out?

This doesn’t take long and it doesn’t require any action right away. What it does is keep your full roster active in your brain so that when a fast decision comes up, you’re not pulling from the two or three names who happened to be most present that week. You’ve already done the thinking.

I started doing a version of this when I was running a team and kept noticing the same uncomfortable question surfacing in my end-of-year reflection: why did certain people get so many opportunities this year and others got almost none?

The roster habit fixed about seventy percent of that problem on its own, because it moved the decision out of the chaotic in-between moments and into a calmer, more intentional space.

Shift Two: The Two-Question Pause

This one is for the fast spontaneous decisions that happen in the hallway, at the end of a meeting, or in a Slack thread when someone needs an answer quickly. You can’t always slow these down, but you can build in a small intervention that changes the outcome.

Here’s the intervention

Before you say a name, ask yourself two things:

First: am I choosing this person because they’re genuinely the best fit, or because they’re the most available in my memory right now?

Second: who else on my team could do this, and have I actually considered them?

That’s it. Two questions, about ten seconds, and most of the time it won’t even change your answer.

Sometimes Derek really is the right call. But sometimes it will surface Priya, or the person who’s been doing excellent work in the background while someone louder was taking up more space in your mental inventory. And that’s the whole point.

The reason this works when general mindfulness reminders don’t is that it’s a specific question with a specific answer rather than a broad aspiration to be more equitable.

Your brain can argue with aspirations. It has a much harder time arguing with a direct question.

One thing worth noting: if you find yourself consistently answering “yes, they’re the best fit” for the same people over and over, that’s worth paying attention to.

Shift Three: Structural Access

This one addresses something the first two shifts don’t fully solve. Informal access to you is itself a career advantage, and right now that advantage is probably not distributed evenly across your team.

The people who can pop by your office, who share your physical space, who have the kind of comfort with informal conversation that makes them easy to approach, those people get something your remote and introverted team members don’t get.

They get unstructured time with you. Time where ideas get floated, where relationships deepen, where someone mentions they’ve been interested in a particular kind of work and you file that away for later. That’s not nothing. That’s actually quite a lot.

The shift here is to create intentional access points that don’t require physical proximity or social ease to benefit from.

What this looks like will depend on your team structure, but a few things I’ve seen work well:

• A monthly one-on-one conversation focused specifically on career and development rather than work status updates.

• A short async check-in at the start of each week where people can share what they’re working on and what they’d like more of.

• A habit of explicitly asking your quieter team members what they’re interested in taking on rather than waiting for them to raise their hand.

That last one matters more than it sounds. We tend to give opportunities to people who ask for them, and we interpret not asking as not wanting.

But a lot of your best people aren’t asking because they don’t know the opportunity exists, or because the culture hasn’t made it feel safe to advocate for themselves, or simply because they’re not wired to push for visibility.

Asking them directly changes the whole dynamic. It signals that you see them, that you’re thinking about their growth, and that they don’t have to perform proximity just to be considered.

The leaders who do this work well are not the ones who achieve perfect equity overnight. They’re the ones who stay curious about their own patterns and keep looking honestly at what’s actually happening rather than just what they intend.

The audit you did today is worth repeating every quarter, not as punishment, just as information. Calendar it. You’re welcome.

And if someone surfaced in your mind while you were reading this, someone you suspect has been paying this tax for a while, trust that instinct. Have the conversation. Tell them you’ve been thinking about their development and you want to make sure they’re getting the right opportunities.

You don’t have to explain everything. You just have to show up for them in a way that makes it clear they’re actually on your roster.

That’s where this starts. One leader, one conversation, one person who finally stops wondering if it’s them.

Questions, reactions, or a story from your own team? Leave a comment. I read every one.

Here’s how it usually goes. An opportunity opens up. A project, a stretch assignment, a chance to get someone visibility in front of senior leadership and you need to pick someone.

You’re not in a calm planning meeting with time to think this through. You’re in between two other things, and you need an answer. So your brain does what brains do and pulls up whoever is most available in your mental field of vision at that moment.

And nine times out of ten, that person is whoever you talked to most recently. Whoever stopped by your office that morning. Whoever replied to your last Slack message in under four minutes. Whoever you’ve just been around.

The result is that Derek, who is cheerful and nearby and makes great small talk, keeps getting tapped for things. And Priya, who has been doing some of the best work on your team for eight months straight, keeps getting passed over.

Not because anyone decided she wasn’t ready, but because she wasn’t standing in your peripheral vision when the moment came.

Priya is paying a tax she doesn’t know exists. And you’re the one collecting it.

I know that’s uncomfortable to sit with. It was uncomfortable for me too, the first time I really looked at my own patterns and recognized what I was doing. Because I genuinely believed I was making fair decisions.

I thought about my people. I cared about their development. And I was still doing this, consistently, because it wasn’t a values problem. It was a brain problem.

Our brains are wired to favor what’s familiar and available, and in a leadership context, familiar and available usually means whoever showed up in front of us most often this week.

Psychologists call it proximity bias. What it feels like from the inside is just making an obvious call.

What I’ve noticed, working with leaders across a lot of different organizations, is that the visibility tax tends to get collected in the unstructured moments.

Not during performance reviews or formal talent conversations, but in the small spontaneous decisions that don’t feel significant enough to slow down for.

Someone mentions they need a lead on a new initiative and you say a name without thinking.

A client asks if anyone on your team wants to present at their next leadership summit and you forward it to the person you had coffee with last Thursday.

A senior leader asks who you’d recommend for a task force and you mention the two people who’ve been most in your orbit lately.

None of those moments feel like high-stakes decisions. But they add up.

And the people who do their best work quietly, independently, or from somewhere other than your office…they’re falling behind in a race they don’t even know they’re in.

That’s what makes this particular leadership pattern so worth naming. The people paying the tax usually sense something is off.

They notice that Derek keeps getting chosen. They feel the gap between their output and their opportunities, and they can’t quite explain it, so they start to wonder if it’s them.

Whether they’re not visible enough, not assertive enough, not whatever enough. And sometimes they start performing proximity just to survive it.

Popping into the office more than they want to, messaging you more than the work requires, laughing a little louder at your jokes…because they’ve figured out the unwritten rule.

I don’t think that’s the culture any of us are trying to build. But it’s the culture we build by default when we’re not paying attention.

The other thing worth saying is that remote employees and introverted employees carry a disproportionate share of this tax, and I think most leaders understand that intellectually without fully feeling the weight of it in practice.

When someone is not in your physical space, they have to work significantly harder just to stay in your mental space.

When someone processes quietly and doesn’t fill silences, they can disappear from your awareness even when they’re sitting in the same room.

That’s not disengagement. That’s just a different way of working, and we’ve built a system that quietly punishes it.

The good news, and there really is good news here, is that proximity bias is one of the more fixable leadership patterns once you can actually see it happening.

It doesn’t require a personality overhaul or a massive restructuring of how you operate. It mostly requires building a few small structural habits that interrupt the brain’s default before it makes another Derek decision.

That’s what this week’s paid post is for. I walk through a straightforward audit that helps you see exactly who’s been absorbing the visibility tax on your team, and then three specific changes you can make to how you handle opportunity distribution going forward. Not sweeping changes, just practical ones that actually work.

If this essay made you think of someone on your team who might be paying this tax right now, that instinct is worth following.

In The Visibility Tax Return: A Gutsy Leader’s Guide to Stopping the Overpayment, you’ll find the full audit plus the framework for making sure your best people stop losing out to proximity. It’s practical, it’s specific, and it’s waiting for you.

Upgrade to read The Visibility Tax Return below.

Upgrade for The Visibility Tax Return

Gutsy Leaders publishes every Tuesday. If someone forwarded this to you:

Subscribe now

You can read the full essay [here]. This post is where we do something about it.

The Buy-In Audit

Five questions to find out if your room is thinking or just nodding

Before you can interrupt the Nod Mob, you have to know you’re running one. This diagnostic is designed to be uncomfortable in exactly the right places.

Think of a recent meeting where a decision was made. Answer honestly.

Question 1: Did anyone in the room change your mind — even slightly?

• A — Yes, something shifted in how I was thinking about it

• B — Not really, but there were good questions

• C — No. I left thinking exactly what I walked in thinking

Question 2: Who in the room was most likely to disagree with you — and did they?

• A — They pushed back and we worked through it

• B — They were quieter than usual

• C — They nodded. Which is not like them.

Question 3: How did you respond the last time someone challenged a decision in a group setting?

• A — I engaged with it seriously, even if I didn’t change course

• B — I acknowledged it but moved on fairly quickly

• C — I don’t remember it going well for them

Question 4: When you scheduled this meeting, had you already decided the outcome?

• A — No, I genuinely needed the room’s input

• B — I had a strong leaning but was open

• C — Yes. I needed people to see it and get on board.

Question 5: After the meeting, did anyone follow up privately with a different opinion than what they expressed in the room?

• A — No, what they said in the room matched what they said afterward

• B — One person had a small caveat they didn’t raise live

• C — Yes. The real conversation happened in the hallway.

Scoring

Mostly A’s — Clean Room Your meetings have oxygen in them. People are thinking, not just performing. This doesn’t mean you’ve eliminated the Nod Mob entirely — it means you’ve made disagreement safe enough to show up. Keep doing whatever that is.

Mostly B’s — Mild Mob Conditions The room is functioning, but there’s a slow drift toward comfort. People are self-editing. A few are testing the temperature before they speak. Left unaddressed, Mild Mob Conditions harden into full Nod Mob culture within a quarter. The scripts below are your intervention.

Mostly C’s — Active Nod Mob Your meetings are producing agreement, not alignment. People have learned that the cost of dissent outweighs the cost of nodding — and they’ve made the rational choice. This isn’t a team problem. It’s a leadership climate problem. The framework below is where you start.

The Nod Mob Interruption Scripts

A five-step framework for cracking the room open before the nodding calcifies into a plan nobody owns

A quick note before we get into the scripts: interrupting the Nod Mob isn’t about manufacturing conflict or performing humility. It’s about creating the conditions where real thinking can happen, because real thinking is the only thing that produces execution people actually follow through on.

These steps are sequenced deliberately. Don’t skip to step three because it sounds easier.

Step 1: Declare your bias before the meeting starts

The Nod Mob assembles in the silence between what you think and what you say. When you walk in with a strong leaning and don’t name it, the room reads it anyway — and calibrates accordingly.

So name it first.

“I want to be upfront — I’m leaning toward Option B going in. I’m bringing this to the group because I want to know what I’m not seeing, not to get permission. Push back if something feels off.”

This does two things. It removes the guessing game about what you want to hear. And it signals that disagreement is the actual assignment — not a social risk.

Step 2: Assign the dissent

Don’t wait for someone to volunteer a counterargument. Assign it.

“Before we go any further — [Name], I want you to make the case against this. Not because I think you disagree, but because I need the argument stress-tested and you’re good at that.”

Assigned dissent removes the social cost from the individual. Nobody has to be the brave one. The brave one was just appointed, which makes it a role rather than a risk.

Rotate who gets assigned. If it’s always the same person, it becomes their identity and everyone else stays comfortable.

Step 3: Ask for the hallway conversation out loud

You know the real opinions live in the Slack thread you’re not in and the hallway debrief after the meeting. So invite that conversation into the room before it migrates there.

“I want to ask something directly: is there anything you’d say about this in the parking lot that you haven’t said in here? Because I’d rather hear it now.”

The first time you ask this, you’ll get silence. Ask it anyway. The second time, you might get a small thing. The third time, you’ll get the real thing. It compounds.

Step 4: Make space for the slow thinkers

The Nod Mob is partly a speed problem. The fastest, most confident voices fill the room first, and everyone else reads that as consensus forming and stands down.

Build in a pause before you call anything decided.

“Before we land on this — I want to hear from anyone who hasn’t spoken yet. Not because I think there’s a problem, but because the quietest people in the room are usually processing something the rest of us skipped.”

This reframes silence as depth rather than agreement. It also tends to surface the most useful thing said in the meeting.

Step 5: Close with accountability, not applause

The Nod Mob’s favorite exit is the energetic close. Everyone leaves the room feeling good. Nobody owns anything specific. Three weeks later the initiative has quietly stalled and nobody can explain why.

Replace the energetic close with a friction close.

“Before we wrap, I want each person to tell me one thing about this plan they’re still not sure about. Not to reopen the decision, but so we know where the soft spots are going in.”

This converts performed agreement into documented uncertainty. You’re not looking for a reason to reverse course. You’re building a map of where execution is likely to get wobbly — so you can shore it up before it costs you.

A note on using these scripts

You don’t deploy all five in the same meeting. That’s its own kind of performance — the leader who’s so visibly trying to prevent the Nod Mob that the Nod Mob reforms around their effort.

The goal isn’t a perfectly dissent-filled room. The goal is a room where people know their real thinking is welcome — and eventually stop waiting to be asked.

Next issue, we’re naming something that happens when leaders confuse visibility with value. And why the people working hardest are often the least seen. More on that Tuesday.

Talk soon - Dr. Linda