Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / The Hidden Power of Manager Vulnerability
Transcript
- Lucas: There's a moment in every new manager's career where you're faced with a choice. You've made a mistake — maybe you misread a quarterly target, or you gave the wrong guidance on a project. Do you own it in front of your team, or let them think it was part of the plan? Luna: And most of us, especially early on, we pick the second option. We think leadership means projecting confidence. Lucas: Exactly. There's this unspoken rule that a manager should have all the answers. But the data tells a different story. Google's Project Aristotle — you know, that massive study on what makes effective teams — found the number one predictor of high performance was psychological safety. Not IQ, not experience. The feeling that you can speak up without being punished. Luna: And that starts at the top. If the manager never admits they're wrong, the team learns to hide their own mistakes. Lucas: Right. So today I want to look at a specific case. There's a mid-size SaaS company — I'll call them CloudMetrics, about 200 people — where the VP of Engineering did something unusual. After a product launch that missed deadlines by two months, she sent a company-wide email titled 'What I Got Wrong.' She listed three specific decisions she'd made that contributed to the delay. Luna: That takes guts. Did it backfire? Lucas: Quite the opposite. Over the next quarter, their employee engagement scores went up twelve points. Voluntary turnover dropped by fifteen percent year-over-year. And the time to raise concerns in project meetings — that actually went down because people stopped waiting for permission to speak up. Luna: So vulnerability didn't weaken her authority. It strengthened it. Lucas: That's the counterintuitive finding. When you're a first-time manager, you worry that admitting uncertainty makes you look incompetent. But what it actually signals is that you're human, and that you value truth over ego. Now, there's a nuance here — vulnerability has to be balanced with decisiveness. If every week you're saying 'I don't know' and never landing on a decision, you lose trust the other way. Luna: So what's the right cadence? How often should a manager share a mistake? Lucas: I'd say it's less about frequency and more about the type of mistake. Share the ones that had a material impact on the team's work — not every trivial thing. And always tie it to a lesson. Like, 'I pushed us to ship the feature early because I underestimated QA time. Next time we'll add a buffer.' That's vulnerability with forward action. Luna: That makes sense. It's not just confessing — it's teaching. Lucas: Exactly. And there's another dimension. When you model that behavior, you give your team permission to do the same. I've seen teams where after a manager starts doing this, the weekly stand-ups become more honest. People flag risks earlier. Blame goes down, problem-solving goes up. Luna: But there's a risk, right? Some leaders might fake vulnerability — the humblebrag version, where they admit a small flaw to seem relatable but never share anything real. Lucas: Teams see right through that. The CloudMetrics VP — she shared specifics that people already knew about. Everyone in the company knew the launch was late and why. She just acknowledged her part in it. That's the key: it has to be genuine and tied to something people can verify. Luna: Okay, so for a first-time manager listening — how do you start? What's the first step? Lucas: I'd say pick one recent decision that didn't go well. Maybe you assigned someone to a task that didn't match their strengths, and it slowed the team down. In your next one-on-one with that person, say something like, 'I think I put you in a tough spot with that assignment. I should have checked your bandwidth first. Let's find a better fit next time.' Luna: That's a low-stakes start. It's private, it's specific, and you're taking responsibility. Lucas: Exactly. Then over time, you might do it in a team meeting. I've seen managers open a retro by saying, 'Here's one thing I'd do differently.' It sets a tone that the retro is for learning, not for pointing fingers. Luna: There's also research from Brené Brown on this — she talks about how vulnerability is the birthplace of innovation. If your team is afraid to fail because their manager will penalize them, they'll never try anything new. Lucas: That's the real cost. And it's not just innovation — it's also retention. Gallup data shows that managers account for at least 70 percent of the variance in employee engagement. And a big piece of that is whether employees feel their manager cares about them as people. Admitting mistakes is one of the quickest ways to show that you're not above them. Luna: I want to push back a little though. What about when the team is in crisis — say, a major client is unhappy, and the manager needs to project confidence. Is vulnerability still the right move? Lucas: That's a fair challenge. In a crisis, you need to be decisive first. You can still be vulnerable about the past — 'I made some assumptions that didn't hold' — but in the moment, the team needs to see a plan. The vulnerability comes after the immediate fire is out, during the post-mortem. So it's not about being vulnerable 24/7. It's about choosing the right moments. Luna: That's helpful. So the rule of thumb might be: in a crisis, lead with certainty. In normal times, lead with honesty. Lucas: I like that. And honesty includes saying 'I don't know' when you genuinely don't. That's another form of vulnerability. You can follow it up with 'but here's how I'll find out.' It shows you're resourceful, not clueless. Luna: You know, this conversation is exactly the kind of thing that makes this show worthwhile for me. Real, practical, no fluff. And if it's hitting for you too, listener — we keep this ad-free because of people like you. Lucas: Absolutely. We've never run a sponsor spot, and we never will. The only thing that keeps us going is listeners who find value in it. So if today's episode was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Luna: And it genuinely helps. We see those notifications come in, and it's a reminder that this work matters. Lucas: Okay — back to vulnerability. Another thing I've seen work well is what I call the 'learning moment share' in team meetings. Once a month, the manager spends five minutes talking about a recent failure and what they learned. It's almost like a mini case study. Luna: And then you can invite others to do the same. That builds a culture. Lucas: Right. I know a team lead at a fintech company who started doing that. Within two months, the team was voluntarily sharing their own mistakes in stand-ups. One developer said, 'I deployed a config change that broke staging for an hour' — and instead of getting blamed, the team brainstormed how to add better safeguards. That's psychological safety in action. Luna: That's a great example. The vulnerability flow starts at the top. Lucas: It does. And it's not about being soft. It's about being effective. The best leaders I've seen are the ones who can say 'I was wrong' without flinching, and then immediately pivot to 'here's what we do next.' Luna: One question I get from first-time managers is: 'Won't my team lose respect for me if I admit I don't know something?' How would you answer that? Lucas: I'd say that respect earned by pretending to know everything is fragile. It cracks the first time you're wrong. But respect earned by being honest — even when it's uncomfortable — that's durable. People trust you more because they know you'll tell them the truth, even when it's hard. Luna: And there's data on that too. A 2023 study in the Journal of Applied Psychology found that leaders who displayed intellectual humility — acknowledging their own knowledge limits — had teams that were more creative and better at problem-solving. Lucas: Exactly. So if you're a new manager listening, here's my challenge: this week, identify one situation where you could have handled something better. And in your next team interaction — whether it's a one-on-one or a stand-up — just say it. Start with 'I've been thinking about X, and I want to share something I could have done differently.' Luna: Small step, big impact. And if you're not ready to do it in front of the whole team, start with one person you trust. Lucas: That's the way. Build the muscle. The more you do it, the more natural it feels. And the stronger your team becomes.