I had an experience about 3 years ago that stood out to me. At the time, I had two team leads running nearly identical zones — same layout, same volume, same equipment. One had been in the role for about eighteen months. The other just six weeks.
Over the course of a week, both zones had similar problems. It started with the same faint symptom: a slight hitch in the pace, nothing that would trip an alarm or show up on a dashboard yet. The first time it appeared, it was in the veteran’s zone. She caught it within a few minutes, walked her line, and rerouted the work around a developing bottleneck before it cost anything. A couple days later, the same signs started showing up in the newer lead’s zone. He didn’t catch it until it had already backed up the better part of an hour of work.
Both of my team leads cared. Both of them were smart. The newer lead wasn’t lacking in effort or intelligence. He was missing reps, the accumulated exposure that lets you recognize a problem before it announces itself.
I’ve written before about this kind of recognition is. It’s not instinct or a sixth sense, but pattern matching built from experience, the same mechanism Gary Klein found in the fire ground commander who sensed a floor about to collapse without being able to explain how he knew. In Leading When You’re Caught Off Guard, I wrote about building a pattern library like this in yourself. Today I want to look at the other half of the job: building it in the people you lead, deliberately, instead of waiting for them to accumulate it the slow way.
Borrowed, Not Bought
First, a quick recap for anyone who hasn’t read the research. Klein studied fire ground commanders making decisions under real pressure and found that in the large majority of cases, they didn’t compare options at all. They recognized the situation and acted. That speed wasn’t talent. It was the product of years of reps, enough of them that the current moment matched something already filed away.
That’s the same gap that existed between my two team leads. The veteran wasn’t smarter. She’d simply seen the early signs of a backup often enough that the pattern had been ingrained in her and her responses become nearly automatic. The newer lead will get there too, eventually, the same way everyone does — by living through enough shifts that the patterns start to repeat.
The problem is “eventually.” Most leaders treat that accumulation as something that just happens, a side effect of time served, but not something they can influence. You post people to a zone, you cover for them while they’re new, and you wait. Some people get there in a year. Some take three. A few, if they never get exposed to the right range of situations, never really get there at all. This isn’t because they lack the capacity, but because they never experience the reps that would have built it.
The Reps You’re Leaving to Chance
The problem is that every month a newer lead doesn’t have their own pattern library yet is a month you’re the backstop. It’s you who has to notice what she doesn’t, you who makes up for the slow catches and gets the escalations that didn’t need to happen.
It’s important to understand that the speed of someone’s development is, partly, a function of what you expose them to, not just who they are. Two people with equal ability can end up years apart in judgment, purely because one of them got a wider range of situations early and the other got a narrower one. If your newer lead spends six weeks in a calm, well-run zone, they won’t build the same pattern library as someone who gets thrown into three different kinds of chaos in the same stretch.
This is the same idea I wrote about in How to Raise the Floor, Not Just the Ceiling: development attention has a gravity to it and, unless you’re intentional about it, it drifts toward whoever’s already closest to ready. The people who most need deliberate reps are usually the ones least likely to get them, because nobody’s rerouting those opportunities toward them on purpose.
The speed of someone’s development is a function of what you expose them to.
Give Them the Call, Not Just the Explanation
The first real lever is the most uncomfortable one: you have to hand over decisions before you’re fully confident they’re ready.
In my experience, most leaders do the opposite. They explain their own reasoning, narrate what they’d do, and make the call themselves until the person has “proven” they’re ready for it. That feels responsible, but it means the person never gets the thing that actually builds the pattern library: the experience of deciding, with something real on the line, and living with what happens next.
Watching someone else decide and deciding yourself are not the same thing. Watching someone else make a decision doesn’t build your reps or your pattern library. You can explain your reasoning to a team lead a hundred times and they still won’t have the pattern in their head the way they will after making the call once, under real pressure, and seeing it play out.
This doesn’t mean you should hand over decisions with no net underneath them. You need to be explicit about the scope: here’s a category of call that’s yours now, here’s what you should still bring to me first, and here’s how I’ll back you up if it goes sideways. Small and bounded, but real. The goal isn’t to throw someone into something they can’t handle. It’s to stop being the one who makes every call just because you’re faster at it. Being faster right now is exactly the gap you’re trying to close.
Make the Thinking Visible
The second lever is narrower but just as important: the reasoning behind a fast call is almost always invisible unless you deliberately surface it.
This is the same purpose behind a debrief, which I wrote about in The Debrief That Builds Leaders. These conversations turn an experience into a lesson instead of just a story about something that happened. The same concept applies here, pointed in the other direction. It’s not enough for your veteran team lead to make the right call. If nobody ever asks them to explain what they noticed and when they noticed it, that knowledge stays locked inside their head, and everyone else has to rediscover it the slow way.
Ask your best people to narrate their thinking out loud, specifically, after the fact: what did you notice first? What told you this wasn’t going to resolve on its own? What would it have looked like if you’d been wrong? Most experienced people have never had to put this into words, because nobody’s ever asked. The answer is usually more specific and more teachable than you might expect: a slight change in the sound of a conveyor, a particular kind of silence, a queue that’s growing in a spot that’s usually self-clearing.
This conversation does two things at once. First, it gives everyone else on the team a shortcut to a pattern that took your veteran months or years to build on her own. And second, it often sharpens the veteran’s own judgment, because articulating something out loud forces them to notice what they’re actually relying on.
Manufacture the Reps
The third lever is one I’ve talked about for individual development previously, but scaled up into something you run deliberately across your whole team: you don’t have to wait for real situations to generate the reps. You can manufacture them.
Take five minutes during shift and ask your team a “what if” question. What would you do if this line started backing up the way it did last month? What if an associate told you they didn’t feel safe on this equipment? What if a senior leader walked up right now and asked why we were down? Let the newest person answer first, every time, even when it’s slower and less polished than what you’d say yourself. The rep is in the answering, in thinking through it and focusing on it in their mind, not in hearing the right answer delivered to them.
Rotation works the same way. If someone’s only ever run one area, they’ve only ever built pattern recognition for that area’s particular failure modes. Deliberately moving people through different situations — a messier area, a different shift, a stretch covering someone else’s responsibilities — isn’t just a development nicety. It’s how you deliberately widen the range of patterns someone has access to, instead of leaving it to chance.
None of this replaces real experience, but it compresses the time it takes to get there, sometimes significantly, by making sure the reps that do happen are varied, examined, and actually theirs — instead of accidental, narrow, and absorbed by you instead.
You can’t hand someone years of experience. But you don’t have to leave it to chance, either.
From Theory to Action
Identify one decision you’re still making that a capable team member could be making instead. Define its scope explicitly — what’s theirs now, what still comes to you, how you’ll back them up — and hand it over this week.
Ask your most experienced team member to narrate a recent fast call, in detail. What did they notice first? What told them it wouldn’t resolve on its own?
Run a five-minute “what if” drill at the end of your next shift. Pick a realistic scenario and let a newer team member answer first, before you offer your own read.
Design one deliberate rotation this month specifically to widen someone’s range of exposure, not just to cover a gap.
Debrief your next near-miss, not just your next mistake. Ask what was noticed, when, and what it would have looked like if the read had been wrong.
Notice who you’re protecting from having to make hard calls, and ask yourself honestly whether that’s kindness or whether it’s slowing down the development you say you want for them.


