You Made a Mistake in Front of Your Team. Here's What to Do Next.
It’s 10:30 on a Thursday morning. You made a call two hours ago—a staffing move, a process change, a decision you were confident about—and it has very clearly not worked out. The evidence is visible on the floor. Your team knows it. A few of them have already exchanged the kind of glance that tells you they’re waiting to see what you do next.
You’re the manager. Everyone is watching.
What happens in the next few minutes will teach your team more about who you are than anything you’ve said in a meeting or written in an email. And if you handle it wrong, in either direction, the damage can take weeks to undo.
This is the moment nobody prepares you for.
The Instinct That Makes It Worse
When we make mistakes as managers, there’s a predictable set of instincts that kick in. We want to explain the context. We want to list the constraints we were working under. We want to note what we didn’t know at the time, or how it would have worked if one thing had gone differently. We want to minimize the impact.
Or, if we’re wired differently, we swing the other direction and beat ourselves up so visibly that the team ends up reassuring us instead of the other way around.
Both of these responses have the same problem: they center you.
The over-explanation says I need you to understand why this wasn’t really my fault. The excessive self-criticism says please tell me I’m not a terrible manager. Neither of them actually addresses the situation, and neither gives your team what they need in that moment, which is clarity and a path forward.
I’ve seen this play out in both directions over my career. The manager who launches into a five-minute explanation of why their decision made sense given what they knew. The manager who apologizes so many times the team stops paying attention to the actual issue. In both cases, the mistake becomes a distraction. The manager becomes the subject. And the team learns that mistakes around here are complicated, loaded events—not something that gets acknowledged cleanly and fixed.
What I Learned From My Most Expensive Mistake
Early in my management career, I was responsible for the pick department at a fulfillment center. We were falling behind on a specific category of large items that moved through a process called Box on Demand. The fix seemed obvious: add more pickers to that area. So I did.
What I didn’t do was tell anyone in the pack department, who received everything we picked and processed those large items through a single, slow, manual machine that maxed out at 60 units per hour.
Within an hour, pack was overwhelmed. The backlog swelled past 300 units. With our carts now tied up in BOD, other pick processes across the floor stalled out. People stood around with nothing to move product into. The whole operation essentially ground to a halt and hundreds of customer shipments were late as a result. It remains one of the most expensive operational mistakes I’ve made in 13 years at Amazon.
I wrote about the details of that situation a couple years ago in my post The Cost of Silence, because the core lesson was about cross-departmental communication. But the part of that story I didn’t tell was what happened immediately after—specifically, how my manager coached me through the moment of standing in front of a disrupted operation knowing it was my call that caused it.
My first instinct was to explain. I had a whole account ready: what I’d seen, what I’d been trying to solve, why the logic had made sense when I made the decision.
My manager stopped me before I could get started.
“Everyone can already see what happened. They don’t need a replay. They need to see how you handle it.”
He was right. And what he taught me shaped how I’ve handled every mistake since.
What Owning It Actually Sounds Like
There’s a version of accountability that’s performative and a version that’s real. Your team can tell the difference immediately, and the gap between them is usually one word: “but.”
Performative accountability: “I made the wrong call here, and I take full responsibility—but I want to give you some context about what I was seeing at the time...”
The “but” undoes everything before it. Your team hears the explanation. They don’t hear the accountability.
Real accountability is shorter. It has three parts: what happened, what you’re doing about it now, and what changes going forward. In practice, on the floor, it sounds something like this:
“I added people to BOD without looping in pack. That created the backlog you’re dealing with right now. Here’s what we’re doing to clear it. Going forward, any staffing change that touches another department gets a conversation with that department first.”
That’s it. No performance. No lengthy justification. No apology tour.
The brevity isn’t coldness—it’s respect. It tells your team that you understand what they need and that you’re not going to make them sit through your discomfort to get it. It also models something enormously valuable: that mistakes can be acknowledged cleanly, without the world ending.
If you’re a newer manager and the words don’t come naturally yet, here’s a simple template to work from:
“I made a mistake. Here’s what I got wrong: [specific error]. Here’s what I’m doing right now to address it: [concrete action]. Here’s what I’m changing so it doesn’t happen again: [specific commitment].”
Write it on a notecard and keep it in your pocket if you need to. Seriously. The ability to say those three things without flinching is one of the most powerful things you can develop as a leader.
The Difference Between a Mistake and a Character Failure
One of the most important distinctions I’ve come to over years of managing (and now coaching and teaching) is this: a mistake is not evidence of who you are. It’s data about a specific situation.
What is evidence of who you are is how you respond to it.
During one particularly rough patch—multiple equipment failures, missed customer targets, a stretch of weeks where nothing seemed to break in our favor—I found myself questioning whether I was cut out for this job. My manager noticed, and what she said has stayed with me.
“You’re letting the failures define you instead of looking at how you’re responding to them. The incidents aren’t the story. Your response is.”
That reframe is the difference between a manager who grows from hard experience and one who just accumulates scar tissue.
I’ve also made mistakes of judgment, not just execution. I pushed hard for a personnel decision once, a promotion I believed in, over the objections of my own manager. I was wrong, and the cost was real for the team and for the person I promoted. I’ve written about that experience in Leading From the Floor in more detail than I’ll go into here. What I’ll say is this: the mistake taught me more about the difference between technical capability and people leadership than any success I’d had. Carrying that lesson forward is how you honor what the mistake cost.
How Mistakes Build Trust — When Handled Right
Here’s the counterintuitive part: a mistake handled well can strengthen your team’s trust in you more than a stretch of smooth operations.
When everything is going fine, your team doesn’t have much information about who you really are under pressure. They see competence. They see normalcy. But they don’t yet know what you’re made of when things go sideways.
A visible mistake is a test, and your team is watching to see whether you pass it. When you acknowledge it cleanly, address the impact, follow through on what you committed to—without drama or deflection—you demonstrate something more valuable than getting it right the first time. You demonstrate that you can be trusted to tell the truth even when it costs you something.
As I’ve explored in the self-awareness series, the leaders who handle mistakes with grace are almost always the ones who have learned to separate their identity from their outcomes. They know the difference between their value as a person and the result of a specific decision. That separation is what lets them own a mistake without crumbling—and move forward without dragging it behind them.
Your team is also learning from how you model this. In my post on building a feedback culture, I wrote about how the norms you set as a leader become the norms your team operates by. If you treat your own mistakes as catastrophic events that require careful management, your team will treat their mistakes the same way—hiding them, minimizing them, covering them up until they become something much bigger. If you treat mistakes as information to be acknowledged and learned from, your team will follow suit.
That shift, from a team that hides problems to a team that surfaces them early, is one of the highest-leverage things you can build as a leader. And it starts with how you handle your own mistakes on a Thursday morning in front of everyone.
From Theory to Action
1. Create a three-sentence template and keep it accessible. Write out your version of the accountability formula—what happened, what I’m doing about it, what I’m changing—and put it somewhere you can actually reference it under pressure. In your phone, on a notecard in your back pocket, taped inside your clipboard. You don’t need to read it verbatim; you need to know the structure so it’s available when your instinct is to explain.
2. Acknowledge within the same shift. When you’ve made a mistake that affected your team, don’t let the shift end without acknowledging it. The longer you wait, the more weight it accumulates. A brief, clean acknowledgment at the next team huddle or during your floor walk is almost always better than waiting for the “right moment” that never quite arrives.
3. Address impact before cause. When you’re talking to the people your mistake affected, start with what it cost them—their time, their effort, their ability to do their job—before you say anything about your own reasoning. “The backlog I created put you behind on your targets” lands differently than “I made a decision that unfortunately resulted in a backlog.” Same information, different order. The first one shows you’re thinking about them.
4. Make one specific, verifiable commitment and write it in your failure log that same day. Not “I’ll communicate better” but “before I make any staffing change that affects another department, I will have a conversation with that department first.” Then open your failure log—your phone notes, a notebook you keep on the floor, whatever tool you use and write down the mistake, the lesson, and the commitment. This is how the mistake becomes useful instead of just painful. If you don’t have a failure log yet, I wrote about how to build one here.
5. Follow through where your team can see it. The next time a situation arises where your stated change applies, apply it—and do it visibly enough that the team notices. If you committed to looping in pack before moving people, do it in front of someone who was there when the original mistake happened. This is the step that actually restores credibility. The acknowledgment opens the account. The follow-through makes the deposit.
6. Check your language in the days after. Notice if you’re still bringing up the mistake repeatedly, still apologizing, still trying to explain the context to different people. One acknowledgment is leadership. Multiple repeat apologies start to feel like you’re asking your team to manage your emotions about it. Say it once, mean it fully, then move on.
7. Look for the pattern, not just the incident. At the end of the week, spend five minutes reviewing your failure log entry. Ask yourself: is this an isolated error, or is it the third time in two months that a communication gap caused a downstream problem? Isolated mistakes get addressed with specific changes. Patterns get addressed with system changes. You can’t see the difference without the log.
8. Watch your team’s behavior in the following two weeks. This is your feedback signal. If you handled the mistake well, you’ll notice people surfacing smaller problems sooner, escalating issues before they become crises, being more honest with you about what’s actually happening on the floor. That shift is the return on the investment you made by handling your mistake with integrity.
Mistakes are not the opposite of good leadership. Handled well, they’re part of it.
The leader your team needs isn’t someone who never gets it wrong. It’s someone who tells the truth about it when they do—and then does the work to be better.