Written by: David Carneal – Digital Efficiency Consulting Group – DECG
Read Time: 4 min
It is tempting to label every defensive leader as arrogant. Tempting, tidy, and occasionally emotionally satisfying. Also, sometimes wrong. Business would be much easier if every problem came with a little sticker that said ego, fear, confusion, bad incentive, or spreadsheet goblin. Sadly, humans remain inconsiderately complex.
Not all resistance is ego. Sometimes it is fear. Real fear. Practical fear. The kind that comes from working in an environment where admitting a problem is treated less like improvement and more like confessing to a felony in the conference room.
A team lead may hide a process flaw because they believe it will make them look incompetent. A manager may deflect scrutiny because their department has been told to keep numbers clean at all costs. An executive may resist outside perspective because they have been burned before by consultants who parachuted in, created a slide deck, named all the obvious problems, and vanished like budget-funded smoke.
That does not make defensiveness harmless. It just means the cause matters. If leaders misdiagnose fear as ego, they may respond with pressure when the real need is safety and structure. If they misdiagnose ego as fear, they may tolerate behavior that keeps the organization stuck. Either way, the workflow pays the bill.
The first clue is what people do with bad news. In healthy cultures, bad news moves early. Not perfectly, not joyfully, and not with confetti, but early enough to do something useful. In fear-based cultures, bad news gets delayed, softened, renamed, or buried under a heroic workaround.
Listen for these phrases
- We fixed it before anyone noticed.
- I did not want to make it a bigger issue.
- I thought leadership already knew.
- We have always worked around that.
- I did not want to throw anyone under the bus.
Some of these are polite. Some are kind. Some are survival tactics wearing khakis.
Leaders can start by asking a better question: what would happen if someone raised this problem earlier? Not what should happen. What would actually happen? Would they be thanked? Questioned? Blamed? Given more work? Quietly labeled negative? If the reward for surfacing problems is pain, do not be shocked when people become masters of decorative silence.
There is a difference between accountability and punishment. Accountability asks, what happened, what did we learn, and how do we prevent the same issue from repeating? Punishment asks, whose fingerprints are on this? Accountability improves systems. Punishment improves hiding.
A practical leader can create a safer problem-reporting rhythm without turning the business into a feelings retreat with name tags. Try a recurring process review with three fixed questions:
- What slowed down this week?
- What had to be fixed manually?
- What did we avoid telling another team because it would become complicated?
The third question is wonderfully nosy in the best possible way. It often reveals cross-functional friction, unclear ownership, and the little political landmines people step around daily.
Then set a rule: the first conversation is about understanding the system, not assigning blame. If a person made a mistake, deal with that appropriately later. But do not let the first response train everyone else to hide the next issue.
Senior leaders have extra responsibility here because culture cascades. If executives reward clean updates over honest updates, managers learn to polish reality. If managers polish reality, supervisors learn to keep problems local. If supervisors keep problems local, frontline employees learn to make workarounds invisible. By the time the dashboard finally shows trouble, the organization has been paying for it quietly for months.
Fear is not fixed with one inspirational speech. Please do not gather everyone and announce, this is a safe space, while three people remember what happened to the last person who spoke up. Trust is built through repeated evidence. Leaders have to show, again and again, that surfacing problems early leads to support, learning, and better process design.
The goal is not to remove discomfort. Work has pressure. Tradeoffs are real. Deadlines do not care about our emotional growth arcs. The goal is to make truth less dangerous than silence.
CTA: In your next team review, ask what people fixed quietly before it became visible. Then thank them before you analyze it. Tiny order change, big culture signal.