The Debrief That Builds Leaders

Turning experience into knowledge

Your team lead just handled a quality exception at the pack stations. It took longer than you would have liked. The solution she landed on wasn't exactly the one you'd have chosen. But she worked through it—start to finish—without you.

That was the goal. The shift is moving again. Your radio is already buzzing with the next thing.

Here's the question nobody tells new managers to ask themselves: What happens next?

For most managers, the answer is nothing. You move on. The shift moves on. You make a mental note that she handled it, file it under "good," and go put out the next fire.

That's precisely where the opportunity disappears.

In my post on When to Step In and When to Step Back, I wrote about the real-time judgment call that plays out constantly on the floor: the moment your hand reaches for the radio and you have to decide whether to intervene or hold back. Stepping back is the harder choice, and making it deliberately is what separates managers who build strong teams from those who accidentally prevent them from growing.

But stepping back is only half the equation.

The other half is what you do with what just happened. And most managers skip it entirely.

The debrief—a brief, focused conversation with your team lead after they've handled something without you—is where the real development happens. Not during the incident. Afterward, when there's space to think. Done well, it's the most powerful development tool you have. Done poorly, it's indistinguishable from a critique. And not done at all, it's a missed opportunity that compounds over time into a team that handles situations but never truly grows from them.

The Conversation Most Managers Skip

There's a reason the debrief is so easy to skip: it doesn't feel urgent.

The situation is resolved. Your team lead got there. The shift is back on track. Everything that needed to happen, happened—so why stop to talk about it?

This is the same logic that causes managers to move on from near-misses without investigating, to file away what just happened without ever processing it. The urgency of operations always wins over the importance of reflection.

But here's the cost of skipping: your team lead just had a real, unscripted experience that built something in her—either clarity and confidence, or confusion and luck. The debrief is what determines which one sticks.

Without a conversation, she doesn't know what she did well. She doesn't know what you noticed. She doesn't know whether she'd make the same call again, or whether she should. She just knows it worked out—this time.

That's a thin foundation to build on.

Why the Debrief Matters More Than the Outcome

Here's something I had to learn during a stretch at Amazon when I was managing more team leads than I should have been: the outcome of any given situation tells you almost nothing about the quality of the decision that produced it.

A team lead can make a poor call and still get a good result. She can make an excellent call and still get a messy outcome. The floor is complicated enough that both happen all the time. If you only evaluate outcomes, you're inadvertently teaching your team leads to care about luck as much as judgment.

The debrief shifts the focus from what happened to how they thought. That's the whole difference.

It also gives you a window into something you can't observe from across the warehouse: how your team lead is actually developing. Not whether she can handle today's problem, but whether she's building the judgment to handle tomorrow's harder one.

The US Army figured this out decades ago. Beginning in the 1970s, the Army developed what they called the After Action Review: a structured debrief conducted after any significant operation or training exercise. It wasn't designed to assign blame. It was designed to accelerate learning. Four questions drove every AAR: What was supposed to happen? What actually happened? Why was there a difference? What do we do differently next time?

What made the AAR effective was that it became embedded in culture. Rank didn't protect anyone from honest review, and the process was explicitly about improvement, not evaluation. Units that embraced it consistently outperformed those that treated every exercise as just another thing to get through and move on from.

You don't need anything as elaborate as a military AAR to debrief your team leads. But the underlying principle applies directly to the production floor: experience without structured reflection produces repetition, not growth.

The Difference Between a Debrief and a Critique

Most "debriefs" that managers actually conduct are critiques in disguise.

The critique starts from the manager's perspective and works backward. It sounds like this: *"I noticed you pulled someone from station three pretty late—you could have made that call earlier. And next time you might want to check the packing specs before you decide..."*

The team lead nods. She hears the feedback. She makes a mental note. And over time, she learns to replicate your decisions rather than develop her own.

A real debrief starts from her perspective and works forward. It sounds like this: "Walk me through what you were thinking when that exception came in. What options were you looking at? What made you go the direction you did?"

Notice what that does. It requires her to articulate her reasoning out loud—to you and to herself. It shows you how she processed the situation: what she weighed, what she missed, what she considered and rejected. And it gives you the information you actually need to develop her: not what she did, but how she thinks.

This connects to something I've written about in the context of feedback in high-pressure environments; the most effective developmental conversations in operational settings are the ones that put the thinking process on the table, not just the outcome. The debrief is where that principle becomes a concrete daily practice.

A critique starts from the manager's perspective and works backward. A debrief starts from the team lead's perspective and works forward.

There's also something the debrief does for the relationship that a critique never can. When you ask someone to walk you through their reasoning instead of telling them what you would have done, you signal something meaningful: I'm curious about how you think. That curiosity—genuine, not performed—is what turns a transactional relationship between a manager and a team lead into a developmental one.

What a Real Debrief Sounds Like

You don't need a framework or a checklist. You need four genuine questions and the discipline to actually listen to the answers.

"Walk me through what you saw." Let her describe the situation from her perspective before you offer yours. You may find she had information you didn't.

"What options were you weighing?" This is the most valuable question in the debrief. If she can name only one option, that's your development target. If she named three, evaluated them, and chose wisely, she's further along than you might have assumed.

"What would you do differently?" Not what did you do wrong—what would she change, and why? This keeps the locus of evaluation with her rather than with you.

"What did you learn that you'll carry forward?" This converts the experience into something durable. Without it, the incident stays a story. With it, it becomes a principle she can apply next time.

The whole conversation can take five minutes. It doesn't require a conference room or a scheduled block of time. It can happen at the end of the shift, standing in the aisle near the pack stations. What it requires is that you make it a consistent practice, a habit that follows any meaningful moment where your team lead operated independently.

Making It a Habit

The trap is doing this only when things go wrong.

If the first time your team lead hears the words "walk me through your thinking" is after she made a mistake, the debrief will feel like an investigation. The emotional association will be negative, and you'll have made the most important version of this conversation harder to have.

The debrief becomes genuinely developmental when it's a routine that follows both successes and struggles. When your team lead handles a complicated situation well, that's worth debriefing too—because understanding why something worked is just as valuable as understanding why something didn't.

I'd recommend folding light-touch debriefs into your end-of-shift wrap-up conversations, or into your regular one-on-one meetings when a notable moment occurs during the week. It doesn't need to be formalized. It just needs to be consistent enough that your team leads start to expect it—and eventually, start doing it themselves with the associates they're developing.

That's when you know it's working. When the behavior you've been modeling starts replicating one level down, you've shifted from managing a team to building a leadership culture. That's a very different thing.

A quick note on timing: the debrief works best when it happens close to the event, but not in the middle of it. In the moment, your team lead is still in operational mode—focused on execution, not reflection. Give it some space. End of shift, beginning of the next one, or a quiet moment when the floor has stabilized. The debrief needs her full attention, and she needs the situation to be fully resolved before she can think clearly about it.

Summary

Stepping back and letting your team lead work through a situation is an act of trust. But trust without follow-through isn't development—it's just absence.

The debrief is what turns experience into growth. It's the five-minute conversation that tells your team lead what you noticed, what you're curious about and, most importantly, that you're paying attention to how she thinks, not just what she produces.

Done consistently, the debrief becomes the engine of your team's development. Your team leads start debriefing their own people. Problems get analyzed more thoroughly. Judgment improves faster than experience alone would ever produce.

The manager who steps back and then debriefs is building something. The one who just steps back is hoping.

From Theory to Action

1. Identify your next debrief opportunity right now. Think about a moment from the past week when a team lead handled something independently: a quality issue, a staffing gap, a process decision. If you haven't talked through it yet, schedule five minutes with them before your next shift ends. Don't let another week pass.

2. Memorize four questions. Write them on an index card if you need to: What did you see? What options were you weighing? What would you do differently? What will you carry forward? These four questions will carry you through almost any debrief conversation.

3. Commit to speaking second. Before your next developmental conversation, make one rule for yourself: you don't speak first. Let your team lead describe the situation, the decision, and the reasoning before you offer anything. Then ask a follow-up question. Just one. And listen again.

4. Debrief wins, not just problems. This week, find one situation where your team lead handled something well and debrief it the same way you'd debrief a struggle. Ask what they saw, what they chose, what they'd repeat. Make it clear that their good thinking is worth examining as closely as their mistakes.

5. Notice who can name their options. As you conduct debriefs over the next month, pay attention to how many options your team leads can articulate before they made a decision. One option means they weren't yet deliberating. Two or three means they were. This single data point tells you more about developmental readiness than almost any performance metric.

6. Add it to your one-on-ones. Use your regular one-on-one meetings to debrief any significant independent decision that happened during the week. The question "walk me through one decision you made this week without coming to me" is worth asking every single week, not as an evaluation but as a development conversation.

7. Watch for the moment they start doing it themselves. The debrief habit has truly taken root when your team leads start asking their associates the same questions you've been asking them. When you see that happening, you'll know the culture has started to shift. That's the real goal: not just team leads who handle situations, but team leads who develop people.

---

This post builds directly on When to Step In and When to Step Back, which covers the moment of decision on the floor. The debrief is what you do with that moment afterward. Next week: Creating Accountability Without Constant Oversight