By David, Founder of Digital Efficiency Consulting Group
Estimated read time: 7 minutes
Let's be honest with each other for a moment.
When most people hear the word "leadership," they picture corner offices, executive titles, and people who have their own parking spots. But that's not really what leadership is. Leadership is influence, and influence shows up everywhere.
It lives in the department head who sets the tone for how their team handles problems. In the operations manager who built the workflow everyone else depends on. In the frontline supervisor who knows the process so well they could do it backwards, and sometimes does.
If people look to you for direction, clarity, or a green light to move forward, you are a leader. And that means this article is for you.
Leadership demands confidence. It demands the courage to make decisions with incomplete information and own the outcome. Those aren't optional qualities. They're what separates people who lead from people who just manage calendars.
But confidence has a twin that nobody puts on their LinkedIn profile. And the longer you lead, the easier it is for that twin to show up uninvited.
It's called ego. And unlike most problems in business, it doesn't announce itself.
When Confidence Quietly Turns Into Defensiveness
Here's the thing about ego: it rarely feels like ego from the inside. It feels like experience. It feels like standards. It feels like protecting what you've built.
Strong leaders make decisive calls. Defensive leaders protect territory.
That territory looks different depending on where you sit. At the executive level, it might be a strategy that hasn't worked in three years but feels too personal to abandon. At the management level, it might be a workflow that only makes sense to the person who designed it. At the team level, it might be a spreadsheet that lives on one person's desktop, unshared, undocumented, and absolutely irreplaceable if that person ever leaves.
The form changes. The dynamic doesn't. Wherever influence lives, ego can attach itself quietly and call itself wisdom.
When was the last time you genuinely invited someone to critically evaluate your area of responsibility?
Not a status update. Not a polished quarterly recap designed to highlight the wins and bury the concerns. A real review, the kind where someone could actually tell you something you didn't want to hear.
When that moment came, did your team see you welcome it? Or did they watch you manage it?
There's a difference. And the people around you already know which one happened.
The "We're Fine" Reflex
A while back, I reached out to a business leader. We'd had a few thoughtful exchanges online, the kind of conversations that make you think this might be someone worth knowing. My message was simple: a professional hello and a note about something I'd found interesting in their industry.
The response came back almost immediately: "We don't need your services. Everything is great here."
No services had been offered.
My first reaction was confusion. Then I wondered if my message had come across wrong. Too forward, maybe? Poorly timed? I read it again. No, it was a straightforward hello.
But after sitting with it, I realized this wasn't really about that particular person or that particular message. It was a reflex. One I've seen play out dozens of times across organizations, from executive boardrooms to warehouse shipping docks.
The assumption that outside perspective equals threat. That someone asking questions is someone looking to expose you. That the safest answer is always "we're fine."
Here's what I've learned after 25+ years working with businesses: the ones who say "we're fine" the fastest are often the ones who need help the most. Not because they're failing, but because that reflex is actively preventing them from getting better.
When someone suggests reviewing your process, your team, or your department, what is your immediate internal reaction?
Not your polished, professional response. Your real one. The one that shows up in your gut before your brain has a chance to coach it.
Is it curiosity? Or is it a quiet, protective "why are they asking?"
That reaction tells you a lot.
Tribal Knowledge and the Quiet Danger of Being Indispensable
Every organization has one. The person who "knows everything."
You know exactly who I mean. They've been there forever. They know where the bodies are buried, metaphorically speaking, hopefully. When something breaks, people go to them. When a new system gets implemented, they're the ones who quietly keep the old one running on the side because they don't trust the new one yet.
That person might be a senior executive who has never documented a decision-making process in their life because "it's all in my head." It might be a mid-level manager who's spent a decade making themselves the single point of contact for everything important. It might be a frontline team lead who owns a critical step in the process and has made sure, consciously or not, that no one else fully understands it.
The level doesn't matter. The pattern does.
When knowledge is centralized and protected, even with the best intentions, the organization becomes fragile. Vacation becomes a liability. Turnover becomes a crisis. Growth becomes a ceiling.
And here's the part that stings a little: the person holding that knowledge often believes they're doing the organization a favor. They're the expert. They're reliable. People need them. That feels like value, and in some ways it is. But there's a version of "indispensable" that's actually just undocumented dependency wearing a cape.
If you stepped away for two weeks, what would slow down or stop entirely?
Think about that seriously. Not what you'd like the answer to be. What would actually happen.
Is that good organizational design? Or is it a dependency that's been quietly building for years, one that makes you feel needed but makes your team fragile?
Ego, Fear, or Just Being Human?
I want to be careful here, because this is the part of the conversation that can go sideways fast.
Not all resistance is arrogance. Not every defensive response comes from a place of pride.
Sometimes it's fear. Real, legitimate fear.
A team lead who hides a process flaw isn't always protecting their ego. Sometimes they're protecting their job. A director who deflects scrutiny isn't always being territorial. Sometimes they're operating in an environment where admitting problems gets punished, not rewarded. An executive who resists outside perspective isn't always arrogant. Sometimes they've been burned before by consultants who parachuted in, told them what was broken, and then disappeared before anything actually got fixed.
Different levels. Different pressures. Same deeply human instinct: protect yourself.
That's worth understanding, not judging. But understanding it doesn't mean letting it run the show.
Would Your Team Feel Safe Telling You the Truth?
If someone on your team identified a real flaw in your process tomorrow, would they bring it to you?
And if you found a flaw in your own process, would you bring it to your leadership?
Or would the quiet fix happen in the background, smoothed over before anyone noticed? Not because anyone is dishonest, but because the environment makes honesty feel risky?
For senior leaders especially, there's a second layer worth examining.
Are the leaders below you encouraged to surface problems early? Or are they rewarded for keeping their numbers clean and their departments drama-free? Because those two things are not the same. And the difference between them determines whether your organization learns or just performs.
Culture cascades. So does ego. So does fear. And so, thankfully, does psychological safety, if someone at the top is willing to model it first.
The Slow Cost of Ego
Here's why this matters beyond any one conversation or interaction.
Ego rarely causes sudden collapse. There's no dramatic moment where everything falls apart and someone points to the ego in the room as the culprit. It's far subtler than that. It causes quiet erosion, the kind that doesn't show up on a dashboard until the damage is already done.
At the executive level, ego stalls strategy. Initiatives that should evolve get defended. Market feedback that should inform decisions gets dismissed. Smart people stop raising concerns because they've learned that raising concerns doesn't go well.
At the mid-management level, ego blocks the cross-functional collaboration that makes organizations actually work. Silos form. Information stops flowing. "That's not my problem" becomes a culturally acceptable sentence.
At the team level, ego hides process inefficiencies. Workarounds become standard practice. The right way to do something gets buried under the way one person has always done it.
Same behavior. Different altitude. Compounding cost.
The strongest leaders I've worked with, at every level, share one quality that doesn't get talked about enough. They are not afraid of being wrong. They are genuinely, viscerally afraid of staying wrong.
That distinction changes everything.
A Thoughtful Close
None of this is meant to be a critique. It's an invitation.
Leadership is hard. It requires you to be confident and humble at the same time, to hold conviction in one hand and genuine openness in the other. That's not a contradiction. It's the whole job.
The goal isn't to appear flawless. It's to build something that works, teams that are resilient, processes that can survive a personnel change, cultures where people actually say what they see.
Whether you lead ten people or ten thousand, the questions in this article matter at the same level. The stakes just look different.
If any of these questions landed uncomfortably, good. That discomfort isn't an indictment. It's information. Awareness is always where improvement starts, and you don't have to do anything dramatic with it today.
Sometimes the next step isn't a major organizational overhaul. Sometimes it's a structured conversation, one that brings executives, managers, and team leads into the same room with a neutral facilitator and a shared goal: not to assign blame, but to find the gaps before they find you.
That's the kind of work DECG facilitates. Candid, practical conversations about where knowledge is concentrated, where defensiveness is quietly costing you, and how to build processes that don't depend on any one person being irreplaceable.
Not to expose what's broken.
To strengthen what's worth protecting.
About the Author
David is the founder of Digital Efficiency Consulting Group. He works with organizations to diagnose workflow friction, uncover hidden operational bottlenecks, and build practical improvement roadmaps that make teams more efficient and resilient.