I spent the first decade of my career convinced a good leader never let anyone see him sweat. Calm voice in the standup. Confident answer in the retro. No "I don't know" allowed, even when I didn't know.
The mask worked right up until the moment it didn't.
The Meeting Where the Mask Cracked
I was leading a team through a rewrite already two months late. Everyone in the room felt it slipping further. I stood at the front and gave the usual performance: we've got this, small adjustments, nothing to worry about.
Nobody believed me. I saw it on their faces. Worse, nobody spoke up, because if the person at the front wasn't worried, why would anyone else be the one to say it?
The next night I sat down with the honest version of the plan and realized the confident version I'd given the team was fiction. So the next day, I did something I'd never done in a leadership role before. I told the truth.
"I don't have a plan to get us there on time. I need your help building one."
The room went quiet for a few seconds. Then someone said, "Okay, here's what I think is broken." The real conversation started.
The Myth: Strong Leaders Never Show Weakness
There's a story many of us got told early in our careers, sometimes explicitly, sometimes only by watching who got promoted. Strong leaders have answers. Strong leaders are steady. Strong leaders don't say "I'm not sure."
I bought into it for years. I wore a mask claiming I always knew the way forward, because I thought it was the job. What I built instead was a team who stopped telling me the truth, since the mask signaled the truth wasn't welcome.
Kul Mahay, who writes about leadership and humanity, put it well: the mask meant to make you look strong is often the exact thing killing your team's ability to innovate. If people believe the person leading them never gets it wrong, they stop bringing you the moments where something is wrong.
Some of this goes back further than my tech career. In the Army, I learned to project calm under pressure, since a shaky leader spreads faster than a shaky plan. This lesson is real and I still use it. What I missed for years was the second half of the lesson: projecting calm and pretending to have every answer are not the same skill. Soldiers trust a leader who says "here's what we know, here's what we don't, here's the plan," far more than one who fakes certainty and gets it wrong later. I carried the first half of this lesson into my tech leadership and left the second half behind. The mask I wore in the rewrite meeting wasn't steadiness. It was a guess dressed up as a fact.
What the Research Shows
I'm skeptical of leadership research most days, so I went looking for something solid before writing this. Google ran a two-year study called Project Aristotle, analyzing 180 of its own teams to figure out what separated the best ones from the rest. It wasn't who was smartest. It wasn't who had the most experience.
The single biggest factor was psychological safety: whether team members felt able to take a risk, admit a mistake, or say "I don't know" without getting punished for it.
Here's the part matters for this post: psychological safety on a team starts with the leader. If I show up every day wearing the mask, performing certainty I don't have, I'm teaching my team admitting uncertainty is dangerous. They learn the lesson fast. Then they stop bringing me the hard truths, the early warnings, the "I think this is going to break" conversations able to save us weeks.
Brené Brown has spent years making a related argument from a different angle: vulnerability isn't the opposite of strength, it's where trust and new ideas come from. I resisted this idea for a long time because it sounded soft. It isn't. It's a discipline. Admitting what you don't know, in front of people who report to you, takes more control than performing false confidence.
The Cost I Didn't See Coming
The rewrite project I mentioned? We didn't hit the original deadline. We hit a real one, together, because the team started telling me things three weeks earlier than they would have if I'd kept performing.
Before the meeting where I told the truth, I had engineers who suspected the architecture wouldn't scale and said nothing, since I'd never given them a reason to think I wanted to hear it. After the meeting, the same engineer who told me my plan was fiction became the person who caught our next three problems before they turned into fires.
Here's the cost of the mask: it isn't people thinking less of you for wearing it. It's people no longer giving you the information you need to lead well. You end up flying blind, surrounded by people who see the fog and choose not to mention it.
Taking the Mask Off Without Losing the Room
Dropping the mask doesn't mean showing up unprepared or turning every meeting into group therapy. There's a difference between vulnerability and dumping your anxiety on your team. I learned this distinction the hard way too, by overcorrecting and turning a status update into a confession booth. Nobody needs it either.
What worked for me was narrow and specific: name the exact thing I don't know, and ask for help with it. Not "everything is falling apart," but "I don't have a plan to hit the deadline, and I need your read on where we're stuck." It's honest without being chaotic. It gives people something to act on instead of only something to worry about.
I've built this into how I coach leaders now through Step It Up HR and the BAT framework at Step Up To BAT, since self-awareness only helps if you're willing to act on what it shows you. Knowing you're wearing a mask and keeping it on anyway isn't progress. It's only a more informed performance.
Three Small Habits Replacing the Mask for Me
Name the gap, not the panic. Instead of "I'm worried about everything," say "here's the one piece I don't have an answer for yet." Specific gaps invite help. Vague dread invites nothing but worry.
Ask before you announce. When I don't know the way forward, I bring the open question to two or three people on the team before I bring a decision to everyone. Half the time, they already had the answer I was pretending to search for on my own.
Say the hard number out loud. Late deadline, budget cut, a feature not working the way we hoped. Say the actual number or fact, not a softened version of it. Softening it to protect your own image costs the team more time than the discomfort of hearing it straight ever will.
None of these habits require you to fall apart in front of your team. They require you to stop pretending you're the only one on the team who isn't supposed to have doubts.
Where This Leaves You
If you're leading a team right now and something is broken, ask yourself honestly: have you told them, or have you told them the version keeping you looking steady?
The people on your team already know when something is wrong. The only question is whether you'll be the one who says it first, or the last one to admit it.
What's one thing you're not telling your team right now they likely already suspect?