Written by: David Carneal – Digital Efficiency Consulting Group – DECG
Read Time: 4 min
Confidence is one of those leadership traits everyone says they want until they meet the bargain-bin version of it. Real confidence helps people move. Fake confidence fills the room with certainty, shuts down questions, and somehow needs everyone to clap before the meeting ends.
The tricky part is that defensiveness rarely feels defensive from the inside. It feels responsible. It feels protective. It feels like standards. It feels like, I know this process better than anyone else, which may even be true. But truth is not a hall pass for making the process impossible to challenge.
Strong leaders make decisive calls. Defensive leaders protect territory. That is the line. It is not about whether you make decisions quickly. It is about whether your decisions can survive honest review without your blood pressure trying to file a complaint.
In operations, this shows up everywhere. A leader defends an approval path because they designed it. A manager defends a reporting structure because changing it would reveal years of duct tape. A supervisor defends a workaround because it is the only thing keeping output moving, and admitting that would create uncomfortable questions from above. Congratulations, the process now has feelings. Very efficient.
The real danger is not that someone is wrong. Everyone is wrong sometimes. The danger is when being wrong becomes emotionally expensive, so the organization starts avoiding the topic entirely. That is how businesses keep broken workflows alive long after everyone knows they are broken.
Here are a few signs confidence may have drifted into defensiveness
- You explain before you understand the concern.
- You treat outside perspective as criticism by default.
- You ask for feedback but only reward feedback that confirms your view.
- You describe old decisions as if they are sacred artifacts.
- You confuse someone questioning the process with someone questioning your competence.
That last one is the root of many operational knots. A process can be flawed even if the person who built it is smart. A workflow can need redesign even if it worked beautifully three years ago. A system can be outdated even if it once saved the company from chaos. Past usefulness does not guarantee current fitness. Processes age. Markets shift. Teams grow. Software gets patched by what appears to be a committee of raccoons wearing headsets. Things change.
A confident leader can say, this made sense when we built it, but let us see whether it still serves the business. A defensive leader says, this is how we do it because it works, then quietly ignores the pile of exceptions proving otherwise.
There is a practical way to test yourself. The next time someone questions your process, pause before answering and sort the comment into one of three buckets:
- Is this a clarity issue? They may not understand the purpose, inputs, ownership, or decision rules.
- Is this a friction issue? They may be pointing to delay, rework, handoff confusion, or duplicated effort.
- Is this a trust issue? They may not believe leadership will actually do anything with the information.
That third bucket is the spicy one. When people stop believing concerns will be handled well, they stop bringing clean information. They bring polished updates, partial truths, and the occasional emergency wrapped in a spreadsheet. Then leaders wonder why they did not know sooner. A timeless business comedy, unfortunately performed live.
You do not need to accept every critique. Some feedback is incomplete. Some suggestions ignore constraints. Some ideas are basically glitter with a calendar invite. But you do need a way to separate weak ideas from uncomfortable truths. Defensiveness makes that separation almost impossible because it reacts to the feeling before it examines the facts.
One useful operating habit is the two-response rule. First response: ask a clarifying question. Second response: repeat the concern back in neutral language. Only after that do you explain, decide, or redirect. This small delay keeps your ego from grabbing the microphone and turning a process review into a hostage situation.
Leadership confidence should create psychological room for better information. It should not become armor so thick that nothing useful gets through.
CTA: In your next process conversation, try the two-response rule. Ask one clarifying question, summarize what you heard, and then respond. Tiny move, big signal.