How to Normalize Mistakes for Team Development

1 in 3 team members admit they’ve stayed silent after spotting a problem. Because speaking up felt riskier. I said that it is a shame when my HR friend mentioned it as feedback from the exit round. And in our pursuit of perfection, we build systems that penalise risk. We teach people to hide. To protect their image, instead of sharing their ideas. 𝗥𝗲𝘀𝘂𝗹𝘁 - They leave places where mistakes are punished harder than silence. Perfection isn’t a standard. It’s a chokehold. It cages creativity. Kills innovation. And creates cultures of high anxiety, not high performance. 🎯 Mistakes aren’t the issue. 𝑴𝒊𝒔𝒕𝒂𝒌𝒆 𝒂𝒗𝒐𝒊𝒅𝒂𝒏𝒄𝒆 𝒊𝒔. Every time you: ❌ Don’t speak up ❌ Don’t experiment ❌ Don’t admit we missed the mark You trade trust for performance theatre. And theatre doesn’t innovate. ✅ Mistakes are attempts in motion ✅ Owning them builds credibility ✅ Learning in public creates trust ✅ And great teams? They screw up. And talk about it. 🔄 So the real KPI: 💡 How fast can you recover, learn, and try again? 📣 Leaders—this starts with you: → Normalise “I got it wrong.” → Reward honesty over image. → Build cultures where mistakes are data, not drama. Because failure isn’t the opposite of success. It’s the compost it grows in. The safest environments are the ones where it’s safe to mess up. What do you think? -------------- I’m Jayant — sharing actionable insights on mental health, growth, and well-being every Mon/Wed/Fri at 5 PM IST. Follow along and tap the 🔔 to stay updated.

Your team watches how you respond when things go wrong. Deflect blame once, and they learn to do the same. Own it completely, and they follow your lead. If you're building a team or aspiring to leadership, this matters more than you think. Your behavior during mistakes creates the culture you'll work in. When leaders throw their teams under the bus, people stop taking risks. They hide problems until it's too late to fix them. They focus on covering themselves instead of solving issues. When leaders own their mistakes completely, the opposite happens. Teams take bigger risks, experiment more, and surface problems early. They know accountability flows up, not just down. That's the environment where great marketing happens. People move faster when they're not worried about blame. Protect your team when things go wrong and watch what they accomplish. The culture you build through accountability determines everything else.

Judgement kills learning faster than you think. Often with the best intentions. A raised eyebrow. A quick correction. A tone that says, "You should know this." Nothing dramatic. But something closes. People stop testing ideas. They stop naming uncertainty. They chase being right over getting better. Safety doesn't mean low standards. It means room to be unfinished. The best teams feel different. Questions are welcomed. Mistakes are examined, not weaponized. Being wrong isn't punished. It's used. That doesn't happen by accident. It's shaped by how leaders show up. What you say matters. How you react matters more. Especially when something goes wrong. 💡 Try this: ↳ Notice your first response to mistakes ↳ Watch who goes quiet over time ↳ Separate accountability from shame ↳ Ask what they learned before what they missed ↳ Model being wrong without defensiveness ❌ This isn't psychological safety: → Being nice all the time → Avoiding hard conversations → Tolerating poor performance ✅ This is: → Mutual respect under pressure → Feedback that builds, not breaks → Mistakes treated as data, not labels People don't need less pressure to grow. They need safer pressure. ♻️ Repost if you believe learning beats fear. 🔔 Follow Richard Goold if you want leadership thinking that doesn't shy away from the hard parts.

Sara Blakely's father asked her one question at dinner every night: "What did you fail at today?" If she had nothing, he was disappointed... That question reframed failure entirely. Not as shame, but as proof she was learning and pushing boundaries. This wasn't just dinner table philosophy. When Sara started Spanx, she built this into her company culture. Early employees remember her asking in team meetings: "What experiment failed this week?" When a product prototype flopped, she'd gather the team to dissect the learning, not assign blame. One failed adhesive test led to their breakthrough backless body shaper design. The failure itself became the innovation catalyst. Most leaders do the opposite. They punish mistakes, avoid risk, and wonder why their teams play it safe. I've watched talented managers freeze when asked to pitch new ideas in companies where one mistake meant being sidelined. They had brilliant solutions but wouldn't risk proposing them. The company lost innovations that could have doubled revenue simply because fear was more powerful than ambition. Here's the truth: if people are afraid to fail, they'll never fully commit. They'll hedge, they'll wait for perfect conditions, they'll do just enough to avoid criticism. Innovation doesn't come from people trying not to mess up. It comes from people willing to experiment, learn fast, and adjust. Leaders who normalize failure unlock that. But most don't know where to start. Try these 3 shifts: First, in 1-on-1s, ask "What did you try this week that didn't work?" and genuinely celebrate the attempt. Second, in team meetings, share a failure of your own from that week and what you learned. Your vulnerability gives others permission. Third, create a "failure board" where people post experiments that flopped but taught something valuable. Make it visible. Make it normal. When failure becomes safe, commitment becomes possible. When commitment becomes possible, real growth happens. If you found this valuable, repost for your network ♻️ Join the 11,000+ leaders who get our weekly email newsletter: https://lnkd.in/en9vxeNk Lead with impact.

Mistakes aren’t the problem. It’s how leaders respond to them that sets the tone for everything that follows. Shame shuts people down. Support lifts them up and builds trust that lasts far beyond the moment. If you're leading a team, here are 10 phrases that can turn missteps into momentum: 1) “It’s okay. Mistakes are a natural part of real growth.” 2) “What matters most now is how we respond and learn from it.” 3) “I’ve made similar mistakes. It’s part of becoming better at what we do.” 4) “This moment doesn’t define your value or future in this team.” 5) “We’ll figure this out together. You’re not alone in this.” 6) “Thanks for being honest. That takes courage and accountability.” 7) “Taking responsibility shows maturity and leadership. I respect that.” 8) “Everyone slips sometimes. What matters is how we bounce back.” 9) “Let’s focus on solutions, not blame. We grow through this.” 10) “This is a growth opportunity in disguise. Don’t miss the lesson.” Great teams aren’t built on perfection. They’re built on psychological safety and that starts with the words leaders choose in tough moments. Because when people feel safe to own mistakes, they also feel safe to lead.

The best workplaces aren’t designed. They’re spoken into existence. Words create culture faster than policies ever could. Early in my Stanford tech leadership career, I led with what I thought mattered: → Migration deadlines met → System implementations flawless → Performance metrics green Enterprise technology transformations are unforgiving. But I learned that psychological safety builds better systems than fear ever could. ⸻ The shift started with one simple practice. In our staff meetings, we each shared one mistake we made that week — and what we learned from it. When I made mistakes, I saved them for those meetings too, so the team could see it was okay to talk about them openly. That simple act changed the room. It wasn’t about airing mistakes — it was about normalizing reality. No one is perfect. No project is perfect. What we build is always an imperfect mix of people, process, and priorities. I wanted my team to see that — to focus on amplifying what’s working instead of obsessing over what isn’t. And when mistakes happen (because they always do), I didn’t want them to lose days, energy, or confidence over it. It’s okay. We’ll fix it. We’ll move forward together. ⸻ Then the language started to change. Instead of: “The deployment window is non-negotiable,” I asked: “What do you need to feel confident about this timeline?” Instead of: “Why didn’t testing catch this?” I said: “What can we learn to strengthen our process?” Instead of: “This performance is below standard,” I offered: “Let’s figure out what support you need to succeed.” ⸻ A few weeks before a critical go-live, my team offered to pull an all-nighter. I told them I’d rather delay the launch than burn them out — that I’d take full responsibility with leadership. Their response? “Janet, we’ve got this. We want to see this through.” Not compliance. Commitment. Not fear. Ownership. That’s when I knew culture had shifted. Because when people feel safe, they stop hiding mistakes — and start solving them. They don’t just show up. They lead. If your team trusts you enough to admit mistakes, you’ve already built something rare. That’s the mark of real leadership. ➕ Follow Janet Kim for more stories on leadership and career transformation. ——— How I help leaders I draw on 19 years in Stanford tech to help mid-career and senior professionals: ✅ Clarify their leadership brand ✅ Build confidence and presence in high-stakes rooms ✅ Prepare for promotions and new leadership roles

Mistakes don’t sink teams. Blame culture does. Most techs don’t get in trouble for messing up. They get in trouble for trying to hide it—because they’re afraid of how it’ll be handled. That’s why we’ve made one thing clear in our shop: If you mess up—speak up. We’re not chasing perfection. We’re building a team that owns it, fixes it, and moves forward. Here’s how we create that kind of culture: • 𝗥𝗲𝘀𝗽𝗲𝗰𝘁 𝗼𝘃𝗲𝗿 𝗿𝗲𝗮𝗰𝘁𝗶𝗼𝗻 Mistakes are a chance to teach—not a reason to humiliate. • 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝘁𝗵𝗲 𝗿𝗲𝗰𝗼𝘃𝗲𝗿𝘆 The question isn’t “Why’d you screw up?” It’s “What are we doing to fix it right—and prevent it next time?” • 𝗟𝗲𝗮𝗱 𝗯𝘆 𝗲𝘅𝗮𝗺𝗽𝗹𝗲 If I mess something up, I say it first. That sets the tone. We don’t have room for fear-based leadership in this industry. Techs need to think clearly under pressure—and that starts with knowing they won’t get thrown under the bus for being honest. Accountability makes people better. Blame just makes them quiet. How do you handle mistakes on your team?

Changing your mind, admitting being wrong, that isn’t weakness, it is respect for reality. Early in my career I thought certainty was leadership. But there’s a difference between moving fast and learning fast. Speed without correction is just drift, and not the "Fast and Furious" kind. The better analogy is a pro team mid-season. You review film, adjust the scheme, toss a play that keeps failing, and install something that fits the reality in front of you. No one calls it weakness when a coach changes a game plan at halftime. We call it competence. In IT, the pattern is simple. An outage, a performance miss, a cost run-up. The weak response is spin. The strong response is a facts-first reset. Here is how we run that in practice, and it works whether you build software or manage a stadium. Write the decision before implementing the decision. List options, assumptions, and owners. Include the date you will revisit and define success vs failure. If the data shows failure is possible, change course. Get really good at your incident management. Review what signal did we miss, what safeguard failed, what standard do we tighten. Everything has a follow up and an owner. Assign a person to argue the most likely failure mode and require alternatives in writing. Your team has one of these mindset people already, I 100% promise it. Keep a reversal log so changing direction is normal, not personal. Normalize change language. “Here’s what I missed, here’s how it landed, here’s what I’m changing.” This is not about being soft. It is about being sound. Strong teams protect truth over pride because the scoreboard eventually exposes both. The tradeoff is real. Openness can slow the first meeting and bruise an ego or two. But it speeds the second and third meeting because you are not dragging denial across the calendar. Trust compounds. Talent stays. Risk declines. My test as a leader is simple. If a team member can show me evidence that contradicts my plan, and I still push the plan, I am protecting my image, not our outcome. The opposite posture is the one I want modeled across our org and in my own house with four kids watching. Admit it, fix it, learn it. Strong leadership is not being right on day one. It is making it safe to be more right on day two.

If your team’s not speaking up… you’ve already lost. Not ideas. Not productivity. Trust. And once trust is gone? Innovation stalls. Collaboration dies. People check out—or walk out. The fix? Not another tool. Not another policy. But something far more powerful: Psychological safety. It’s not a “nice to have.” It’s the hidden engine behind every high-performing team. Here’s how you build it—one conversation, one decision, one moment at a time 👇🏼 1. Lead with curiosity, not judgment. ↳ “Help me understand…” beats “Why’d you do that?” 2. Admit your own mistakes. ↳ Model the safety you want others to feel. 3. Give credit generously. ↳ Shine the light on others—often and publicly. 4. Respond, don’t react. ↳ Let people tell the truth without fear of fallout. 5. Invite pushback. ↳ Ask: “What am I missing?” 6. Remove silent punishments. ↳ Reward honesty, not just agreement. 7. Normalize “I don’t know.” ↳ That’s how real learning starts. 8. Make feedback feel safe. ↳ Correct with care. Aim for growth, not shame. 9. Start meetings with check-ins. ↳ Connection before conversation. 10. Celebrate courage, not just results. ↳ Applaud the voice, not just the victory. Because when people feel safe, they don’t hold back. They contribute. They challenge. They soar. If you want your team to rise—safety comes first. Which one of these 10 will you lead with this week? ♻️ Share this with your network if it resonates. ☝️ And follow Stuart Andrews for more insights like this.

Mary was hired for her voice… but the culture taught her silence. She was smart, experienced, deeply committed to the team’s success. But after a few team meetings where her ideas were ignored, one slack message from her manager that felt like a dismissal, and watching another teammate get publicly blamed for a mistake… she shut down. She still showed up. Still did her job. But she stopped challenging ideas. Stopped flagging concerns. Stopped contributing anything that felt too risky. And just like that, the team lost one of its most valuable minds. This is what happens when psychological safety is missing. People don’t speak up. They don’t ask for help. They don’t disagree when they should. They don’t say the thing that could have changed everything. Psychological safety isn’t about being nice. It’s about feeling safe enough to take interpersonal risks to raise your hand, challenge the group, admit a mistake, or try something new, without fear of humiliation or punishment. When it’s there: → Teams learn faster → Decisions get better → Engagement goes up → Accountability increases (yes — not decreases!) When it’s missing: → People play small → Teams avoid hard conversations → Mistakes get hidden → Growth slows I’ve worked with dozens of teams who thought performance would come from processes, dashboards, or incentives. But performance at scale starts with safety. 💡 How do you build psychological safety? 1/ Normalize and role model vulnerability. Leaders, start with you. Admit mistakes. Ask for feedback. Say “I don’t know” when you don’t. 2/ Encourage healthy dissent. Instead of “Any questions?” ask “What’s one thing you would challenge in this plan?” 3/ Respond to bad news with curiosity, not blame. If someone raises an issue, thank them. If someone flags a risk, reward them. Your response sets the tone. 4/ Close the loop. If someone makes a suggestion, even if it’s not feasible, acknowledge it. Silence kills initiative. 5/ Create safe spaces. Dedicated time in meetings for people to reflect, share concerns, or speak about what’s not working, without immediate judgment or debate. It’s not complicated. But it takes intention. And consistency. Because psychological safety is earned in the way we show up, every day. -- I’m Anne Caron, I help leaders build people-first, high-performance cultures as they scale. Follow me for more on People Strategy, Conscious Leadership & Organisational Design. #PeopleStrategy #PsychologicalSafety #LeadershipTips #WorkplaceCulture #TrustAndSafety