Early in my leadership career I managed someone who was talented, capable, and quietly making my job much harder
Not because he didn’t care. Fear was driving his decisions, and I didn’t have the language to address it.
I made every mistake a well-meaning leader makes. I was too soft when I needed to be direct. I used the wrong words at the wrong moments. And every time I tried to address the behavior, it got worse instead of better.
What I learned from that experience became the foundation of what I now teach through Leadership Linguistics. The words you choose as a leader either create psychological safety or confirm every fear your team member already has.
This post walks you through exactly how fear shows up on your team, how to tell the difference between fear and defiance, and the specific language that fixes it.
How Fear Makes Work Invisible
Fear on a team doesn’t look like you’d expect. It doesn’t look like someone cowering or refusing to work. It looks productive on the surface and corrosive underneath.
Here’s what fear actually looks like:
They don’t copy you on critical stakeholder communications. Not always because they are trying to work around you, though sometimes they are (we’ll talk about defiance later), but often because being seen in real time feels dangerous. What if the email isn’t perfect? What if they’re asking the wrong question? Visibility feels like exposure, so they remove you from the equation entirely.
They go down rabbit holes silently. Something is unclear. But asking for clarity feels like admitting they don’t know enough to be in this role. So they figure it out themselves. Three days later they surface with work that missed the mark entirely, and you find out too late to course correct.
They hide work that might be wrong. They’d rather spend days quietly redoing something than show you an imperfect draft. The result is wasted time, missed deadlines, and a leader with no visibility into what’s actually happening until the damage is done.
They go way out of their lane. Overcompensating by doing more rather than checking if they are doing the right thing. And because you can’t see it happening, the course never gets corrected.
They never say I don’t know. Because not knowing feels like proof they don’t deserve to be there. So they guess. And sometimes they guess wrong in expensive ways.
All of these behaviors have one thing in common. They create invisibility. And invisibility is expensive. For them, for you, and for the entire team.
What Leaders Say That Makes It Worse
When I was managing this person back then I said all the wrong things. Not because I was a bad leader. I was defaulting to the language most leaders use when they’re frustrated and don’t know what else to say.
Here’s what I said and why it backfired:
“Why didn’t you tell me sooner?”
This sounds reasonable. What it communicates is that sharing problems is punishable. He files that away and hides the next one even more carefully.
“Why did you do it that way?”
Even when you’re genuinely curious, why sounds like an accusation. They go immediately into defense mode instead of thinking mode. You get justification instead of insight.
“You need to speak up more.”
Completely unhelpful. They already know they’re not speaking up enough. What they needs is the language and the safety to do it differently.
“You should keep me informed.”
Should implies they already know what they’re supposed to do and are choosing not to. It adds shame to a situation that’s already driven by fear. Shame doesn’t create behavior change. It creates more hiding.
This is the most well-meaning mistake and possibly the most damaging. Using soft language around a hard requirement makes it sound optional, so it’s treated it as optional. Then you’re frustrated by non-compliance that your own words invited.
The gap between what you mean and what they hear is often just a few words. And those words are Leadership Linguistics.
Fear vs. Defiance
Not every difficult behavior is fear. Sometimes it’s defiance. Sometimes it’s a fierce assertion of independence. And they require completely different responses.
Fear looks like:
Avoidance, silence, over-explaining, hiding, disappearing into work without checking in, never flagging problems until they’ve become crises.
Defiance looks like:
Selective communication, working around you rather than with you, asserting independence in ways that undermine the team, hiding mistakes specifically to avoid accountability rather than out of genuine anxiety.
The way to tell the difference is this question asked with genuine curiosity and without accusation:
“I want to understand what’s getting in the way of this requirement. Can you help me understand your thinking?”
What instead of why. Curiosity instead of accusation. And then you listen without filling the silence.
If the answer reveals fear:
They are worried about being seen making mistakes. They’re not sure they’re handling it correctly. They’ve been trying to protect himself from scrutiny.
Respond with:
“I want to make sure you know there’s no version of this where I think less of you for asking a question or flagging a problem early. There is a version where I can’t help you because I didn’t know what was happening. Bringing me in early is exactly what I need from you.”
If the answer reveals defiance:
They’re confident they don’t need your oversight. They’re asserting that they can handle it independently. They’re working around you intentionally.
Respond with:
“I hear that you feel confident managing this directly. I respect that confidence. And I need you to keep me informed regardless, not because I don’t trust your judgment, but because I’m accountable for this project and I can’t be accountable for what I can’t see. That’s not negotiable. Can you confirm you’re comfortable with that going forward?”
That last question matters enormously. It’s not asking permission. It’s creating a verbal commitment. They have now agreed to the requirement rather than simply received an instruction. That’s a fundamentally different psychological contract.
Could vs. Will
The single most important language shift I made was learning when to use could and when to use will.
Could is coaching language. It opens a door. It invites without shaming. It’s appropriate when you’re creating new behavior in someone who needs safety to try something different.
“Before you spend more than an hour on something that feels unclear, you could come to me first. A five minute conversation up front could save us both days on the back end. That’s not weakness — that’s how effective leaders think.”
Will is accountability language. It closes the loop. It establishes the non-negotiable clearly and without apology. It’s appropriate when the requirement is real and the behavior needs to change.
“Going forward you will copy me on all stakeholder communication for this project. Not because I’m monitoring you, but because I’m accountable for this project.”
Using could when you mean will teaches them that your boundaries aren’t real. They will test them, not necessarily out of defiance, but because your language told them they were optional.
Using will when the situation calls for could damages trust and signals that your leadership style is punitive rather than developmental.
To do this, you need to know which conversation you’re actually in. Then choose your words accordingly.
Making Mistakes Safe — The Language That Changes Culture
There’s a broader cultural shift that happens when leaders choose their words intentionally. Here’s the language that builds a team where fear is creeping in:
“I’d rather hear about a problem early when we have options than late when we don’t.”
“When you made that mistake last month, what did you learn? That’s what I care about.”
“The fact that you’re asking questions tells me you care about getting this right.”
“I need you to keep me informed. Not to watch you, but so I can protect you if the direction gets questioned later.”
Model this yourself. Say I don’t know out loud in front of your team. Then find out and follow up. When your team sees you making not-knowing safe, they’ll stop pretending they always know.
Psychological safety isn’t a culture initiative. It’s a language practice. And it starts with you.
What Changed
The person I was managing eventually became one of the strongest members of the team (and found a leadership role with another company.) Not because I gave him a pep talk or sent him to a training. Because I learned to say the right thing at the right moment, and to tell the difference between when he needed a coach and when he needed a clear boundary.
Leadership Linguistics isn’t something you’re born with. It’s strategy. Every word you choose either makes it safer to tell you the truth or teaches your team to hide. Either builds a culture where problems get caught early or one where they compound in silence until it’s too late.
If you’re managing someone right now whose fear is making your job harder you’re not alone. The answer isn’t a performance improvement plan. It’s a language shift.
Ready to Apply Leadership Linguistics to Your Own Leadership Challenges?
Private one-on-one coaching gives you the specific language strategies for your real workplace situations, whether you’re navigating your own career or leading a team through complexity.
Video: Fear or Defiance? Know the Difference
Discover more from Sue Reynolds
Subscribe to get the latest posts sent to your email.
