Apple Podcast: Deliberate Leaders
Have you ever shared too much in the name of being authentic?
That moment where you realized mid-sentence, “Oh no, I shouldn’t have said that.” And then you can’t take it back, and you’re watching people’s faces trying to figure out if you crossed a line.
We’ve all been there. I know I have.
Vulnerability has become leadership gospel. Be real. Be open. Be transparent. Show them you’re human. There are TED talks about it, books about it, entire leadership programs built around it.
And here’s the thing: I’m not saying it’s wrong. Vulnerability, when done well, can be incredibly powerful. It builds trust. It fosters genuine connection. It reminds your team that you’re a real person, not a leadership robot programmed to speak only in corporate jargon.
But here’s the paradox that trips up even the most well-intentioned leaders:
Vulnerability without boundaries isn’t strength. It’s exposure.
And there’s a massive difference between the two.
The Oversharing Epidemic
I’ve watched this pattern repeat itself countless times: leaders who mistake oversharing for authenticity. They pour out every stress, every fear, every frustration, thinking it makes them relatable. Thinking their team will appreciate the raw honesty.
James was one of these leaders. He prided himself on being an “open book.” He’d share everything—his marriage struggles, his financial stress, his doubts about whether the company would survive the quarter.
At first, his team seemed engaged. They’d nod sympathetically. They’d say things like “thanks for being so real with us.”
But over time, something shifted.
People started hesitating before bringing him problems. They’d sugarcoat bad news. They’d avoid raising challenges because, frankly, they were worried about adding to his pile.
One of his directors finally pulled me aside after a particularly difficult team meeting. She said something that still echoes in my mind: “I feel like I need to take care of him. And that’s not what I signed up for.”
That’s exactly what happens when vulnerability tips into oversharing. Your team doesn’t feel inspired or connected. They feel responsible for your stability. They feel like they need to protect you instead of being led by you.
That’s not connection. That’s collapse.
The Hidden Cost of Unfiltered Vulnerability
When leaders overshare, the organizational costs are significant and often invisible until the damage is done:
Emotional burden transfers. Your team starts managing your emotions instead of focusing on their work. They become reluctant to bring you challenges because they’re worried about your capacity to handle more.
Trust erodes paradoxically. While you think you’re building trust through transparency, you’re actually undermining it. People start wondering: “If they can’t handle their own challenges, how will they handle leading us through ours?”
Decision-making hesitates. Teams begin second-guessing whether to escalate issues. They make decisions in a vacuum because they don’t want to add to your visible stress load.
Psychological safety reverses. Instead of feeling safe to be vulnerable themselves, your team feels they need to be strong for you. The dynamic inverts, and they start performing stability rather than expressing authentic concerns.
The irony is devastating: you’re trying to create connection through vulnerability, but you’re actually creating distance through dependency.
Strategic Vulnerability: The Diana Model
Let me contrast James’s approach with a different leader—Diana, an executive going through a genuinely difficult time. The company was in transition, she was exhausted, and personal challenges were affecting her energy.
She could have walked into her all-hands meeting and unloaded everything. She could have asked for sympathy. She could have made it about her struggle.
But instead, she said something I still think about years later:
“I want to be honest with you. I’ve been struggling with burnout lately, and I’ve realized I wasn’t protecting my energy the way I needed to. So here’s what I’m doing to fix it. I’m blocking focus time on my calendar. I’m delegating differently. I’m saying no to things that don’t align with our priorities. And I’m sharing this with you not because I need you to worry about me, but because I want us all to learn how to protect our energy better. Because if I’m not modeling sustainable leadership, how can I expect you to practice it?”
Can you hear the difference?
That’s professional vulnerability. Honest, but contained. Real, but responsible. She named the struggle, but she centered the lesson.
Her team didn’t walk away worried about her. They walked away with permission to set boundaries themselves. They walked away with a framework they could actually use.
That’s the power of strategic vulnerability.
The Scar vs. Wound Principle
Here’s a rule I use in my own life and share with every client I work with:
If the story still hurts when you tell it, it’s not ready to be shared.
Share from the scar, not the wound.
Think about it this way: When you have a fresh wound, it’s raw, it’s bleeding, it needs care and protection. You don’t go showing that to everyone. You tend to it privately until it heals.
But once it becomes a scar? That’s different. A scar has a story. A scar shows you survived something. A scar can teach someone else how to survive too.
That’s what your team needs. Not your pain. Your perspective.
They don’t need to know you’re drowning. They need to know you learned how to swim.
How to Apply the Scar Principle
Time matters. Give yourself distance from the challenge before sharing it. If you’re in the thick of a crisis, that’s not the time to process it publicly with your team.
Resolution matters. Can you share not just the problem but the path forward? If you can’t yet articulate what you’re learning or how you’re addressing it, wait.
Purpose matters. Are you sharing to teach, to give permission, to normalize struggle? Or are you sharing to process, to vent, to seek comfort? The former serves your team. The latter serves only you.
The Lighthouse, Not the Storm
There’s a quote I love: “You can be the lighthouse or the storm, but you can’t be both.”
As a leader, your job is to be the lighthouse. Steady. Visible. Guiding people through the darkness, through uncertainty, through choppy waters.
Not adding to the chaos. Not becoming another thing your team has to navigate around.
Does that mean you have to be perfect? Absolutely not.
Does it mean you can never be human? No.
It just means you’re thoughtful about what you share, when you share it, and why you’re sharing it.
The Three Elements of Lighthouse Leadership
Steadiness. You can acknowledge challenges without transmitting panic. You can name difficulty without dramatizing it. Your emotional regulation becomes the team’s anchor.
Visibility. You’re present and real, but you’re not performing your struggles. People can see you’re human without feeling they need to rescue you.
Guidance. Even in sharing challenges, you’re pointing toward a direction. You’re modeling how to navigate difficult waters, not just announcing that the waters are difficult.
The Service Test
Before sharing something vulnerable, ask yourself this critical question:
“Am I sharing this to serve them, or to relieve myself?”
If it’s to relieve yourself, find a therapist, a coach, a trusted friend, a peer group. That’s what they’re for. Those are your safe spaces for processing raw emotion and unfiltered struggle.
If it’s to serve your team—to teach them something, to give them permission to be human too, to model healthy boundaries—then share it. But share it from that place of “here’s what I learned,” not “here’s what I’m going through.”
This distinction changes everything.
Practical Application of the Service Test
Serving yourself sounds like:
- “I’m so overwhelmed I don’t know how we’ll get through this quarter.”
- “I’m questioning whether I’m cut out for this role.”
- “My personal life is falling apart and I can barely function.”
Serving your team sounds like:
- “I’ve realized I was taking on too much, so here’s how I’m restructuring my time.”
- “I’ve learned that imposter syndrome hits everyone, including me. Here’s how I work through it.”
- “I’ve had to set better boundaries between work and home. Let me share what that looks like.”
See the shift? One creates burden. The other creates permission and learning.
Strategic Vulnerability in Practice
Here’s what professional vulnerability actually looks like across different scenarios:
When You’ve Made a Mistake
Oversharing: “I completely screwed up that client meeting and now I’m spiraling about whether I’ve lost my touch.”
Strategic vulnerability: “I made a call in that client meeting that didn’t land well. Here’s what I learned about reading the room better, and here’s how we’ll approach the follow-up differently.”
When You’re Facing Uncertainty
Oversharing: “Honestly, I have no idea if this strategy will work and I’m terrified we’re heading in the wrong direction.”
Strategic vulnerability: “We’re navigating uncertain territory with this new strategy. Here’s our hypothesis, here’s what we’re watching for, and here’s how we’ll course-correct if needed. I’m comfortable with measured risk when we have clear decision points.”
When You’re Setting Boundaries
Oversharing: “I’m completely burned out and can barely drag myself to work anymore.”
Strategic vulnerability: “I’ve realized I wasn’t modeling sustainable work practices, so I’m making some changes to protect my energy. I’m sharing this because I want us all to think about what sustainable high performance looks like.”
Notice the pattern? Strategic vulnerability always includes the struggle and the response. It gives people a map, not just a confession.
Three Reflection Questions for This Week
1. What’s one truth you can share that builds connection without crossing your own boundary?
Think about a challenge you’ve recently navigated successfully. What did you learn that your team might benefit from hearing? Frame it from the other side of the struggle.
2. Where can you be honest about your humanity without making your team carry the emotional weight of it?
Identify an area where you can normalize struggle without dramatizing it. Where can you give permission for imperfection while still modeling capability?
3. What lesson have you learned that your team actually needs to hear right now?
Look at your calendar from the past month. What pattern or challenge kept emerging? What did you figure out about navigating it? That’s probably worth sharing—from the scar, not the wound.
Your Practice for This Week
Before your next team interaction where you might be tempted to share something personal or challenging, pause and run it through this filter:
- Is this a scar or a wound? (Has enough time passed for perspective?)
- Does this serve them or me? (What’s my real motivation?)
- Can I share the lesson, not just the struggle? (What’s the actionable insight?)
If you can’t answer all three clearly, wait. Give it more time. Process it privately first.
Where Authenticity Meets Discernment
Real trust doesn’t come from unfiltered transparency. It comes from the intersection of authenticity and discernment.
It’s being real about challenges while remaining responsible for your impact.
It’s being honest about your humanity while protecting your team’s psychological safety.
It’s sharing your journey while still maintaining your role as the guide.
That’s where genuine leadership presence lives—not in performing invulnerability, and not in oversharing vulnerability, but in the thoughtful space between the two.
Your team doesn’t need you to be perfect. They need you to be steady.
They don’t need you to have it all figured out. They need you to model how to navigate uncertainty with grace.
They don’t need to know every struggle you’re facing. They need to learn from how you’ve faced struggles before.
That’s the difference between being exposed and being authentic.
One leaves everyone feeling uncertain. The other builds unshakeable trust.
The next time you’re tempted to share something vulnerable, remember: you can be the lighthouse or the storm, but you can’t be both.
Choose to be the lighthouse.
Not sure if you're the bottleneck? Find out in 2 minutes →
