I keep a list of dates about the people I work with: birthdays, work anniversaries, wedding anniversaries, their kids’ birthdays. Whenever one comes up, I send them a short message.

I’d done this haphazardly for several years, but became much more intentional about it after reading David Burkus’ book Friend of a Friend. There’s a very practical reason for why I do this; it gives me a genuine excuse to reach out to someone I might not have talked to in months, without the conversation feeling like it’s building up to an ask. Most of the time, it turns into a real catch-up — what they’re working on now, what’s changed since we last spoke.

The tracking itself is nothing special, just some recurring reminders in my Outlook calendar. But this practice, repeated for years across dozens of people, is the mechanism behind what I’m going to share in this article, a system for staying in a lot of people’s lives a little bit, consistently, for a long time.

Why This Works

Two things happen every time I send one of those messages.

First, it keeps me current. When a site I’ve supported starts slipping back into old habits or a new problem crops up, the site leaders I periodically check in with think of me first. Those check-ins are part of why struggling sites keep referring me to other struggling sites, a pattern I’ve written about before.

Second, it builds goodwill that reads as genuine, because it is. I spent one week last November working alongside a specialized improvement team on a training project. Afterward, I kept in touch with the team’s lead the same way I keep in touch with everyone else on my list. Months later, when I discovered her team was teaching an outdated standard to sites network-wide, she was willing to actually hear that criticism and work with me to fix it, instead of getting defensive or shutting the conversation down. I’ve told the resolution part of that story before, the alignment channel, the forced choice, the six teams, in Building Influence Without Authority. But a key reason it worked as well as it did is because she already trusted me. That trust had been built up over months, long before I needed it.

Congratulating someone with nothing to ask for is exactly why it works. People remember who showed up when there was nothing in it for you.

The Art of Knowing People

None of this works if the dates are the whole relationship. A birthday message to someone you don’t actually know doesn’t do much good. But the tracking matters because it forces a small, repeated act of paying attention: what this person cares about, what’s been hard for them lately, what they’ve mentioned that’s worth remembering. A real relationship is built on specifics, not on the fact that you both happen to work at the same company. The dates give me a reason to show up regularly enough that I learn those specifics over time, instead of losing touch and having to rebuild the relationship from nothing whenever I need it.

I’ve written a full piece on the specific skill of connecting people and teams that wouldn’t otherwise cross paths — see Building Bridges for that. The short version relevant here is that the habit of staying in touch with people across your organization, not just your own department, is what makes you someone who can actually make those connections when they’re needed. You can’t bridge two groups you don’t know anyone in.

The Alumni Network

The people you work with now won’t all stay where they are. Some will move to other companies, other industries, other cities. Most people let those relationships fade the moment the shared workplace disappears, treating the connection as tied to the job rather than the person.

That’s a mistake you need to avoid. Colleagues who’ve moved on are often more useful to know later, not less. They can see your industry from a different vantage point, they’re no longer competing with you for the same opportunities, and they remember who you were to work with before you had anything to gain from staying in touch. I’ve kept several of these relationships going for years past the point where either of us had any organizational reason to. Most of them have been worth it at least once, often when I least expected it.

The same birthday and anniversary habit works here too. It doesn’t stop being relevant just because someone’s badge doesn’t have your company’s name on it anymore.

Summary

None of this is complicated, and that’s the point. If it weren’t simple, I wouldn’t have been able to keep it up as long as I have. A short list of dates and a few minutes a year per person is all it takes. The standards alignment with that improvement team, the string of site referrals, none of them happened because of one good conversation. They happened because the relationship was already there, months or years before the situation existed.

Last week I wrote more specifically about what this compounds into; how people you’ve helped start advocating for you without being asked. That doesn’t happen with people who disappeared from your life the moment you stopped needing anything from each other. The return doesn’t come from any one message. It comes from being the person who’s still there, years after most people would have let the relationship fade.

From Theory to Action

1. Start your own list this week. Five and their birthdays, work anniversaries, or whatever else you already know off the top of your head.

2. Set a recurring calendar reminder for each date, a few days early. Give yourself time to write something real instead of a rushed one-liner on the day itself.

3. When you reach out, ask a specific question about what they’re working on now. The message isn’t complete until there’s something for them to actually respond to.

4. Add one person you haven’t spoken to in over a year, ideally someone who’s since left your company. Reach out with no agenda beyond reconnecting.

5. Resist the urge to make an ask the first time you reconnect with someone. Let the relationship exist for its own sake before you need anything from it.

6. Every month review your list. Add more people and dates, and notice which relationships feel different than they did before you started.

Last year I taught a training class that wasn’t anything special on the surface; just one of many I’ve run. One attendee happened to work at a site that, a few months later, got new equipment installed. He remembered the class and asked if I’d come teach his site’s leaders how to run it.

That wasn’t part of my job. Nobody assigned it to me. I said yes anyway, and it went well enough that word made it back to the team responsible for installing that equipment across the network. They started asking me to run the same training at every site where they upgraded equipment.

Nobody “promoted” me into that role. Nobody wrote a job description for it or conducted interviews. It exists because one person, impressed by something I did for him, told someone else to bring me in, and then that pattern repeated enough times that an entire team built it into their standard rollout process.

The Distinction

A mentor advises you directly. They sit down with you and share what they know. A sponsor spends their own credibility on you, telling someone else you’re worth the risk.

I’ve written before about finding a mentor and the broader shape of mentorship: how to find one, how to build the relationship, how to eventually become one yourself. But I haven’t talked much about sponsorship until now. It’s important to understand that these aren’t the same thing. A mentor teaches you. A sponsor moves you.

Most people picture sponsorship as a single dramatic moment. Someone champions you by name in a promotion meeting, or something similar. That happens, but it’s more the exception than the rule. More often sponsorship looks like the retrofit training story I shared. It’s not one single moment, but more a pattern of people who worked with you deciding to point the next person your way.

Why Mentorship Alone Stalls

Advice compounds slowly, and it doesn’t require any particular rank or company to be useful. Some of the best mentoring I’ve gotten came from same-level peers who were simply the best available person at one specific skill. There have been times I’ve even sought out advice from someone below me on the org chart, because he’s better at a specific skill than anyone else I have easy access to. My current mentor doesn’t even work for the same company as me. He has no path into any room where my next promotion will be discussed, but that’s not the point of the relationship.

A good mentor teaches you skills and sharpens your judgment. They can give useful guidance this way for years and never be in the room where a stretch assignment gets decided, where a name gets suggest for a promotion, or where leadership debates who’s ready for more scope. A mentor’s purpose is to give advice and improve your thinking and decision-making capacities. But no amount of good advice substitutes for someone in that room deciding you’re worth the risk.

This is why mentorship-heavy development plans can stall out. The advice is necessary, the mentor is necessary, but it’s not enough. You need a sponsor.

You Can’t Ask For This

You can ask someone to mentor you, and it can work. I shared some basic scripts in my post on finding a mentor that I’ve used in the past. But advice is something a person can simply decide to give. Asking someone to sponsor you doesn’t work the same way. It puts them on the spot to vouch for something, with their own credibility and reputation as collateral. If they don’t know you well and haven’t worked with you closely, most people will decline rather than stake their credibility on an unproven bet.

The retrofit training program didn’t happen because I asked the installation team to start recommending me. It started because one person’s experience was good enough that recommending me felt like a safe move that he wouldn’t have to defend later.

What Makes Someone Sponsor-Able

Three things make someone worth vouching for:

Work that survives without you there to defend it. In Building Influence Without Authority, I wrote about a site visit where I left the site leadership with a detailed report instead of an opinion. I had recommendations ranked by hours saved, with my reasoning clear enough that anyone could check it. They didn’t have to take my word for anything. That’s what makes the retrofit training repeatable, too: the sites I trained weren’t taking anyone’s word that it worked. They could see it in the numbers within weeks. Doing this kind of verifiable quality work is the foundation. Nothing else will matter if your work doesn’t hold up to scrutiny.

Visibility outside your daily tasks. A sponsor can’t advocate for something they’ve never seen. The retrofit training spread as wide as it did because it happened directly in front of the people who were going to need the same thing next. First this was other sites’ leaders, then eventually the installation team overseeing every rollout across the network. But it has to be visible. It doesn’t matter how good your work is if nobody knows.

Trust that doesn’t require a favor. Nobody who recommended me was doing me a favor. They weren’t recommending me because we were friends or they felt obligated. They were solving their own problem by pointing someone to a known quantity. That’s a much sturdier kind of advocacy than that built on personal loyalty, because it survives long after the original relationship has any reason to still matter.

Recognizing It When It’s Happening

This same pattern has repeated in multiple parts of my job. A struggling site once asked for help. Once things improved, another struggling site called them to ask what they’d done to turn things around. The site’s leadership mentioned mentioned my name and that second site called me the next day. Then a third site called. By the time the last site I wrote about called me in, my name and reputation had already traveled through three other sites.

I didn’t build a reputation campaign to make that happen. I did the same thing each time, the same three things I just outlined above. I showed up, did work that held up on its own, and let the people who’d seen it decide what to do with that information. Twice now, in two different areas of my job, that same mechanism has led to me taking on roles nobody ever officially assigned me, but multiple people and even entire teams depend on.

If you’re looking for this in your own work, don’t look for one dramatic sponsor. Look for the pattern: has anyone you’ve helped gone on to recommend you to someone else, unprompted? Has it happened more than once? That repetition is the signal. One instance is a compliment. But three times? Five times? That’s sponsorship.

Summary

Mentorship and sponsorship solve different problems. A mentor makes you better. A sponsor makes you known to people you don’t have direct interactions with. You need both. Sponsorship happens when the work you do holds up without you there to defend it, enough times, in front of enough people, that recommending you doesn’t feel risky and just becomes the obvious move.

From Theory to Action

1. Identify one piece of work you delivered recently that could survive scrutiny without you there to explain it. If nothing comes to mind, that’s the first gap to close.

2. Look back over the last year for anyone who used your work to recommend you to someone else, unprompted. Write down every instance you can find, even small ones.

3. Pick one piece of current work and ask whether it’s visible to anyone outside your daily circle. If the answer is no, find one low-effort way to make it visible.

4. Track instances of unprompted recommendation in your Growth Documentation System. This pattern is easy to forget once it’s happened a times and started to feel routine.

In The BRIDGE Method for Cross-Functional Meeting Success, I used Apollo 13 as an example of successful cross-functional coordination. Flight controllers, engineers, astronauts, and ground crews all pulled together to bring a crippled space shuttle home. It’s a good example, but it has a key piece that makes it easier is some ways than many other problems you’ll encounter.

Gene Kranz had the final say. Nobody in that room needed to figure out whose call it was. NASA had already answered that question before the shuttle ever took off.

Many cross-functional teams don’t have a Kranz. You can bring together the right people, have a clear purpose, well-structured input, and document your reasoning but still end the meeting without an authoritative decision, because the person with the authority to make one was never in the room. Sometimes that person doesn’t even exist because nobody in the company has ever had to deal with the sort of questions you’re facing now.

The Question BRIDGE Assumes You Can Answer

The second step of my BRIDGE framework is to define decision-making authority before the discussion starts. Will you be making this decision by consensus? Will one specific person make the call, and the rest are there to give their input? Is it a joint decision between two department heads? This step of the framework assumes that you know who has the power to decide the outcome. Most of the time you do, but occasionally you’ll run into situations where it isn’t clear.

This is the same problem we looked at a couple weeks ago in Why No One Owns the Problem Between Departments. Ownership gets drawn around departments, but not necessarily around decisions that span both of them.

The Clean Handoff

In these situations, the best thing to do is name the deadlock explicitly. Make sure everyone involved understands that the decision you’re facing exceeds what anyone present is authorized to make. Then prepare to present it the same way we looked at in last week’s article on Building Influence Without Authority. Put together two or three options with the pros and cons of each and a date by which a decision has to be made..

Then you need to find the actual owner. This does not always mean you’re just looking for a more senior person. It’s whoever has, or should have, authority over both sides of the decision. Sometimes it is as easy as a shared manager. But other times there isn’t anybody, and the best you can do is propose who should own decisions like this going forward.

Bring them the options you came up with, the trade-offs between them, and where everyone in the group stands on the question. You need to give them enough information so that if they weren’t in the meeting they can still make an informed decisions without having to re-litigate the whole discussion.

Always make sure to document who made the decision and why they were the person that made it. When things like this come up and there isn’t clear ownership, it’s rarely a one-off. Chances are that future problems will pop up in the same grey area, and you’ll want to have a clear answer next time about who has authority over that area. Record it so everyone knows moving forward.

From Theory to Action

1. Before your next cross-functional meeting, identify whether anyone involved has authority to decide the thing you’re meeting about.

2. If the answer is no, say so clearly and make sure everyone knows it, rather than letting it fizzle out with a vague “let’s regroup.”

3. Package any stalled decisions as a couple named options with real deadlines.

4. Watch for the difference between a genuine deadlock and a room that just needs one more structured conversation. Not every stall means no one has authority.

5. Track which decisions in the operation keep getting kicked down the road unresolved. That pattern usually indicates a gap where nobody holds clear authority.

Back in May, I learned that two versions of the same standard work were being taught in the network. There was the official written standard, but there was also an alternative approach, born out of a workshop at a site a couple of years ago. A tiger team that focused on correcting and improving processes at struggling sites had been teaching the unofficial version. Meanwhile, my manager training team was teaching managers to follow the written standard. This created a lot of confusion when a manager would attend our training and be taught one way, then go back to their site and be told something totally different by the team that was there to help them improve.

Six different teams touched this process in different capacities: network operations, the specialized improvement team, process engineering, two training teams, and regional leadership. But none of them were talking to each other about it and most of them didn’t know that conflicting versions of the standard even existed. They all thought that the version they were teaching was the correct standard. The org structure never asked them to compare notes with each other. Each team sat inside its own reporting line, with its own priorities, its own definition of ‘good.’ Nobody’s role included checking whether the other teams were working from the same standard.

That’s the exact pattern from my post on Why No One Owns the Problem Between Departments: ownership gets drawn around departments, never around the connections between them. We had six rigid silos and no one assigned to bridge them. Nobody assigned me to coordinate the teams or solve the conflict. But being aware of it put the obligation on me to do something about it.

I’ve written before about the difference between leadership and influence — authority over your own department versus the ability to move things you don’t control. But knowing the difference doesn’t tell you what to say to the person on the other side of a gap who doesn’t report to you. That’s what I want to look at today. In the actual moment, what do you do?

Why the Two Default Moves Fail

Most people default to one of two moves when they find a problem outside their lane. Both tend to fail.

Asking nicely puts the entire decision in someone else’s hands with nothing behind it. You’ve raised a concern. They’ve heard it. Nothing obligates them to act, and if they’re already busy (and they always are) a polite flag gets filed away as something to get to eventually. Eventually rarely comes.

Escalating immediately solves the urgency problem and creates a worse one. Going over someone’s head before you’ve tried working with them directly tends to burn the relationship you’ll need the next time. You might get compliance that once, but you also get a reputation as someone that’s hard to work with.

The problem is that both approaches skip the work that needs to be done. When you’re in this kind of situation, what you need to do is remove the friction that makes saying no the path of least resistance for them.

Frame It As a Gate, Not a Challenge

The first move in resolving the standards conflict was a direct conversation with the other training team, asking them to pause materials they’d already invested time and effort in.

I didn’t frame it as “you’re building the wrong thing.” I framed it as a quality gate: I let them know that a standards conflict had surfaced, and continuing what they were doing risked codifying something that hadn’t actually been validated. That’s a completely different conversation than telling a team their work is wrong. That just puts them on the defensive. Presenting it as a quality concern gives them a reason to want the pause as much as you do; nobody wants to be the team that shipped an unvalidated standard to the whole network.

Most people will cooperate readily with a gate and resist a challenge, even when the underlying request is identical. A challenge asks someone to admit an error. A gate asks someone to avoid one.

Structure the Ask So It Can’t Stay Vague

Getting the pause bought a few weeks but it didn’t resolve anything. All six teams needed to align on one answer. My biggest concern was that an open-ended conversation among six teams with competing histories and priorities could have run for months. So instead of scheduling a series of meetings, I built a single dedicated Slack channel and pulled in one representative from each team. I was very intentional about the way I presented the problem. I didn’t just say “here’s a problem, let’s discuss this.” I framed the conversation around exactly two options: the current official standard, or the alternative that had come out of the earlier workshop. I gave the pros and cons of each and asked everybody to pick one. I also gave them a clear date they needed to respond by.

Narrowing the frame did most of the work. Vague asks invite vague responses and no urgency. A forced choice between two specific options, with a real deadline attached, gives a group of busy senior people something they can act on. The alignment happened on schedule because the structure didn’t leave room for the conversation to drift. There was still disagreement and conversation about the merits of each approach. But presenting it as two options with a deadline kept the discussion on topic and on time.

Bring Something Instead of Asking For Something

My second story is a different kind of authority problem. In the last example, nobody had asked me to take charge, I’d simply seen a problem and taken ownership of it. In this instance, site leadership had asked for my help. Being invited makes things easier, but I still had no authority over the site, the team, or the managers running it. If you’ve read When A Good Leader Meets Bad Culture, this is the same site from that post. After the events I shared in that post, I reached out to the general manager at the site. He knew there were some problems and requested that I come visit.

I spent a couple days on the floor observing before I said anything about causes. The site was running about 6% behind three comparable locations with identical layouts. The assumption walking in, from the site itself and from the network’s perspective, was that this was a matter of the employees not being as engaged as at other sites. My analysis found otherwise. The site’s individual process rates were actually near the top of its peer group. The real gap was in the execution of the process. Because they had some of their systems set up incorrectly and had some quality shortcomings in a couple places, the site was generating nearly a quarter more touches per package than its peers. Everyone was working hard, they were just doing more work than should have been needed.

When I gave my recommendations to the site lead, I didn’t walk in with a diagnosis and ask them to accept it. I walked in with a finished report: ranked recommendations, each one sized in hours saved per week, with the reasoning shown so it could survive scrutiny from anyone who wanted to check my work. One fix alone was worth well over two hundred hours a week, once I traced it back to containers running underpacked and compounding into congestion everywhere downstream.

Asking a struggling manager to trust your judgment is a big ask. Handing them a diagnosis they can independently verify, with a clear reframe from “your team isn’t working hard enough” to “the work itself was set up wrong,” is a much smaller one. He didn’t have to take my word for anything. The math did that part.

Protect What’s Working Before You Touch What Isn’t

That report had one really important section that mattered as much as the recommendations — a list of everything the site was already doing better than its peers, with an explicit note not to touch any of it.

It would have been easy to skip that section because it didn’t add any hours saved. But a manager who’s just been told, by an outsider, that his site is underperforming, especially coming after a public struggle, is primed to hear the whole visit as criticism. Naming what was already working — clearly, specifically, before getting into what wasn’t — changed what kind of conversation this was. It stopped being “here’s what’s wrong with your site” and became “here’s what’s happening, including the parts you should be proud of.”

This is not a social nicety. It’s how you show them that your visit is not an attack, so they’ll listen when you give them four things worth changing. It’s how you show him that you’re not trying to take apart everything he’s built.

Summary

Exerting influence without authority comes from a small number of repeatable moves: frame a hard ask as protection rather than correction, structure requests so they aren’t vague, bring finished work with data instead of an opinion, and protect what’s already working before you touch what isn’t. These things show that you’re there to help, not to attack. They make it easy for the people involved to say ‘yes.’ None of it requires outranking anyone. They don’t even require someone to give you permission. They just require you to pay attention and be genuinely helpful.

You don’t need to outrank someone to move them. You need to make the right answer easier to reach than the wrong one.

From Theory to Action

1. Name one gap you’ve spotted that isn’t officially yours. Write down which teams touch it and whether any of them are even aware the others are involved.

2. Before you ask anyone to change course, find the “quality gate” framing. Rewrite your ask so it protects the other person from a bad outcome, rather than correcting a mistake they’ve already made.

3. Reduce your next cross-team ask to a forced choice with a deadline. If the request could still be answered with “let’s keep talking about it,” narrow it further.

4. The next time you need someone else’s buy-in, bring a draft, not a question. A finished recommendation someone can push back on moves faster than an open request for their opinion.

5. Before you flag what’s broken, write down three things that are working. Say those first, specifically, before getting into what needs to change.

6. Identify the person in your network most likely to say no to your next ask. Have the conversation with them first, one-on-one, before it happens in a group.

So instead of putting out a new post this week, I wanted to bring an older post back. I published this nearly two years ago, but it’s an important topic worth revisiting. It’s something I still have to remind myself about when things get chaotic: what’s urgent is rarely the same as what’s important.

We’ll be back to the regular schedule next week. Here’s the original post, unchanged:

A quality issue surfaced on night shift. Someone caught it, flagged it the way they’d been trained to, and moved on to the next task, confident the information would reach whoever needed it next.

It didn’t. Day shift’s packing team never saw the alert. It had gone out in an email that wasn’t part of anyone’s start-of-shift routine, and by the time someone noticed, the same defect had already made it into product waiting to ship.

Nobody had done anything wrong. Night shift did their job: they caught the issue and reported it, exactly as trained. Day shift did their job: they ran their standard startup checks, exactly as trained. The alert existed. It just existed in a place neither shift ever checked.

We eventually fixed the communication gap, but the fix isn’t what I want to talk about today. The fix is easy once you’ve found the gap. The interesting part is how the failure even happened. We had two teams, two sets of procedures, both followed correctly, and a problem that fell cleanly into the space between them because nobody’s role covered that space.

That space is where most cross-departmental failures live. Not in negligence, but in the way processes and teams are designed.

Nobody Owns the Seams

Every operation I’ve ever worked in has a clear answer to “who owns this” for almost everything that happens inside a department. Pick owns picking. Pack owns packing. Quality owns quality checks. Maintenance owns the equipment. Ask who’s responsible for a problem inside any one of those lanes, and you’ll get an answer fast.

But if you ask who owns the space between pick and pack, or anywhere that a problem in one department’s output becomes the next department’s problem, you’re likely to get either conflicting answers or just silence.

This is the pattern behind a huge share of the operational failures that get chalked up to “poor communication.” I’ve written before about how much operational information dies at shift changes. The pattern between departments is similar but it gets less attention because a shift change happens on a schedule you can build a process around, while a cross-departmental handoff can happen at any moment, in either direction, without warning.

Org charts are very good at defining ownership inside a box. They are rarely designed to define ownership of the line between two boxes. That line doesn’t show up on anyone’s scorecard, doesn’t appear in anyone’s job description, and doesn’t get raised in anyone’s performance review. It only becomes visible when something falls through it. And even when that happens, the conversation is about damage, not design.

Why This Keeps Happening

If ownership gaps between departments were rare, they wouldn’t be worth an entire article. But they’re not rare, and they’re not random. Three things reliably produce them.

The structural reason: ownership gets drawn around departments, never around the connections between them. Your dashboard measures your department, because it was built to. Pick’s metrics show pick. Pack’s metrics show pack. Nobody’s metrics show the health of the handoff between them, which means a problem in that handoff can get worse for weeks without appearing on either scorecard. The same gap shows up in job descriptions. Nobody was hired to own the transition between pick and pack They were hired to run pick or to run pack.

The behavioral reason: raising it feels like overstepping. This is the most common reason that I see. Most managers I’ve trained aren’t ignoring cross-departmental problems out of laziness, they’re just hesitant to say something about another department’s territory because it can come across as criticism, or as reaching outside their lane. As I’ve written about in my collaborative problem-solving framework, one of the clearest signs a problem needs more than one department’s attention is that it crosses a boundary. But recognizing that a problem needs collaboration doesn’t tell you who’s supposed to be the one who starts it. Politeness causes these sort of issues more often than negligence does.

The reactive reason: the fixes we reach for patch the failure, not the pattern. A ripple check. A communication autopsy. A signature requirement at handoff. These are good, necessary responses. I’d recommend all three, and I’ve used all three myself. But each one only closes the specific gap that just caused a specific failure. Your operation has other gaps that nobody’s watching yet. Fixing one issues won’t fix the underlying pattern that’s causing them.

Ownership Is a Stance, Not a Title

You may have heard the observation that nobody takes a rental car to a car wash. This same idea applies here. It’s not that people are careless. It’s just a fact of human nature that ownership changes behavior. When somebody is responsible for something, they take care of it. But when it’s not yours, you treat it differently. Managers can end up treating the space between departments the same way, cared for by no one, because nobody was ever assigned to care for it.

The leaders who close these gaps aren’t the people with more authority, but a certain mindset. They treat a gap as their responsibility from the moment they first notice it, rather than assuming someone else will take care of it or waiting to confirm it’s officially their responsibility first. This is a mindset that can be learned. All it takes is the next time you spot a gap like this, you decide that saying something is worth the minor discomfort of stepping outside your lane.

From Theory to Action

1. Run a “ghost audit” on one recent miss. Pick a cross-departmental problem from the last few months. Trace backward: who would have had to notice it early, and did their role actually ask them to say something if they did?

2. Ask the ownership question out loud. In your next cross-functional meeting, ask directly: “If this specific handoff breaks, whose job is it to catch it?”

3. Build one lightweight check for your highest-risk seam. Not a full system, just one handoff, one checkpoint, or one person accountable for confirming it happened. Start narrow and prove it works before expanding.

4. Bring one identified gap to a peer manager this week. Decide jointly who owns it going forward. A ten-minute conversation now is cheaper than the reactive fix later.

5. Document the pattern, not just the incident. One ownership gap is an incident. Three similar gaps across different areas is a pattern worth raising with your own leadership.

It’s the end of July.

The year has been busy! A process change in Q1. A promotion on the team in the spring. New equipment that took three weeks longer to install than planned. A quality initiative that’s wrapping up. And somewhere in all of that, seven months have passed.

Most managers I know treat this moment as one to survive — the mid-year review that HR requires, the check-the-box conversation that proves the meeting happened, the paperwork that goes into a file and gets referenced in December when the real review comes around. You do it because you’re supposed to, and then you get back to the floor.

That’s not what this article is about.

I want to talk about something different: the deliberate choice to pause. Before the pace picks back up in Q3, before peak season prep starts consuming everything, before the second half of the year is already happening around you, take a few minutes to reflect and ask a few honest questions about where your team actually is. Not for HR. Not for a file. For yourself, and for the people you’re managing.

Not a formal review. A reset.

The Review vs. The Reset

The formal mid-year review looks backward. It assesses the first six months against goals that were set in January, when you didn’t yet have a full picture of the year ahead, and generates a rating that most people find either demoralizing or meaningless, if not both.

The reset I’m describing looks forward. It uses the first six months as context (what actually happened, what changed, what you learned) to make better decisions about the next six. The first half already occurred. You can’t manage it anymore. The second half is still entirely in front of you.

In sports, halftime isn’t primarily a review of the first half. The coaches aren’t in the locker room dwelling on the score or distributing grades for individual performance. They’re asking two questions: what do we know now that we didn’t know before the game started, and how do we adjust? A mid-year reset asks those same two questions.

The mid-year reset takes an honest look at what the first half taught you—about your team, about your gaps, about what you got right and what you misread—and uses that information to make better decisions about the upcoming months you still have time to shape.

You can’t manage the first half anymore. The only thing the mid-year reset can change is the second half.

Why This Particular Pause Matters

In most warehouse and manufacturing environments, late July sits in a unique spot in the calendar. Q2 is closed. Peak season prep hasn’t fully consumed the schedule yet. The floor is a little quieter than usual, with a relative softness in the pace that won’t appear again until January.

That window is worth using deliberately, because it closes. By September, you’re managing Q3 pressure. By October, you’re in peak preparation. By November, you’re in peak itself. The decisions you make in July—which of your people to develop more aggressively, which gaps to address before they become Q4 problems, which processes to fix while there’s still time to fix them—determine what December looks like.

There’s also a development argument for this specific timing. As I’ve written about before, development takes time, consistency, and progressive challenge. If someone needs to be ready to run their zone independently by November, you need to have started that work in July. Waiting until Q3 review season means you’ve waited too long.

The mid-year reset is when you identify who needs what, while you still have time to provide it.

Start With Yourself

Before any conversation with the people you manage, the reset starts with a self-assessment.

This is the manager’s version of what I described in Start the Year By Understanding Yourself. That post was about using January to set your leadership intentions for the year ahead. The mid-year version of that question is sharper: how has the reality of the first half matched the intentions you set?

There are three questions worth asking yourself before you talk to anyone else:

• What did I get wrong about my team in January that I understand better now? Six months of daily context creates knowledge that no amount of pre-year planning can replicate. The person whose capability you underestimated. The process problem you didn’t yet know existed. The associate who was struggling with something that only became visible gradually. What did the first half reveal that you didn’t expect?

• Where did I invest my development attention, and does that distribution match what I actually needed? This is the question most likely to produce an uncomfortable answer. Who actually got your time, your stretch assignments, your coaching conversations? Does that match the floor you need to build for the second half? Where are the gaps and what will you do differently?

• What conversations have I been postponing? The Conversation You Keep Postponing was about performance specifically. But the question applies more broadly. Are there development conversations that haven’t happened yet? Feedback that someone needs but hasn’t received? Someone who’s been operating in a role they’ve outgrown, waiting for a conversation that would open the next chapter?

The self-assessment doesn’t have to be a long process. An hour of honest reflection, with your notes from one-on-ones and shift reviews, is usually enough to surface the things worth addressing. The hard part is being willing to answer the questions accurately rather than justifying yourself.

The Individual Reset Conversation

Once you’ve done your own assessment, the most valuable thing you can do is have a reset conversation with each person who reports directly to you.

This applies whether you’re managing associates, team leads, or a mix of both. The level doesn’t change the principle—it only changes the vocabulary. A reset conversation with an associate looks different than one with a department manager, but both conversations are asking the same basic questions: where are you, what has the first half been like, and what does the second half need to look like for you?

This is not a formal performance review. No ratings, no documentation for HR, no evaluation that carries weight in December. The reset conversation is designed to create space for honesty that the regular operational rhythm doesn’t always allow.

I stumbled onto this practice during my transition from Area Manager to Operations Manager. In July of that year, I scheduled reset conversations with each of the team leads I’d inherited. I didn’t know what I’d find, but what I learned changed the entire second half of the year. One had been managing around a process gap since February and hadn’t raised it because their previous manager had dismissed an earlier concern. Another was ready for a significant stretch assignment but had assumed it wasn’t coming. A third was dealing with some things in her personal life that had been affecting her energy since May. None of it would have come up in a regular check-in.

The same kinds of discoveries can happen at every level. The associate who’s been improvising around a training gap for months. The reliable performer who’s ready for more responsibility but hasn’t said so. The person whose home life has been affecting their focus. What you learn depends on what you create space for, and the reset conversation is designed to create that space.

The conversation covers four areas. I’ve found that running through them in roughly this order tends to work well:

Where do they think they are? Open with something like: “If you think back to where you were in January (the things you were working on, what you were trying to get better at, etc.) where do you feel like you are now compared to where you thought you’d be?” Let them answer before you offer your own read. Their self-assessment often reveals things you haven’t noticed.

What’s been harder than expected, and what’s clicked? “What’s taken more out of you than you expected this year? And what’s felt easier or more natural than you thought it would?” The first question surfaces hidden struggles. The second surfaces capability you might not have fully recognized. Both are useful.

What do they want the second half to look like? “When we talk again in December, what would need to have happened for you to feel like this was a good year for you?” This is the most forward-looking question in the conversation, and it often produces the clearest picture of what someone actually wants.

What do they need from you? “What would help from my end? Where could I be more useful to you in the second half of the year?” This question signals that the conversation is genuinely bidirectional. You’re not only assessing them, you’re asking them to assess you. The answers are often small and immediately actionable. They’re also the ones most likely to change the quality of your relationship through the rest of the year.

The whole conversation takes 10-15 minutes at most, but I’ve found it pays outsized dividends.

The Team-Level Reset

Beyond the individual conversations, You should also do a team-level assessment to get a realistic feel for where your team’s collective capability sits relative to what the second half will require.

This isn’t about reviewing individual performance. It’s about three questions:

• What is the operation going to need from this team in the next six months? Peak volume. New equipment. A process change. A staffing transition. Whatever Q3 and Q4 hold, what does your team need to be able to do well by the time those demands arrive?

• What’s the gap between where the team is now and where it needs to be? The Team Capability Mapping post might be helpful here. Go through it with the second half’s demands in mind rather than the first half’s context. You’re not evaluating past performance; you’re identifying future gaps while there’s still time to close them.

• Which gaps can be closed before August and which need the full six months? Some are addressable quickly: a training conversation, a process clarification, a responsibility shift. Others require months of consistent development to close. Knowing which is which tells you where to start this week and what to begin planning for.

The team-level reset often reveals things the individual conversations don’t. The coverage gap that you identify when you think about who can run which area independently. The bench that’s thinner than you realized in a specific function. The process that two people understand fully and nobody else has ever been properly trained on. Recognizing these gaps in July will make November less stressful.

What to Do With What You Find

The reset is only useful if what you find in it changes what you do.

This sounds obvious, but it’s where most mid-year reflections fail. The assessment happens. The conversations happen. The gaps become visible. But then the pace of operations absorbs everything and the insights disappear into the same forward motion that made them invisible in the first place.

The first step is triage. Not every gap the reset surfaces is equally urgent or equally addressable. A quick way to sort them: anything that’s been affecting performance or morale since before June is probably overdue and should be addressed this week. Anything that relates to a Q4 operational demand get planned immediately. Anything developmental that doesn’t have an operational deadline gets scheduled but doesn’t need to happen before September.

From there, two practices keep the reset from evaporating. The first is immediate action on anything quickly addressable. If someone has been managing around a process gap since February, fix it before the week is out. If someone is ready for a stretch assignment and hasn’t been offered one, identify the assignment before the next check-in. These small items have an outsized effect on trust; they demonstrate that the reset conversation led somewhere, which makes the next one more honest.

The second is a written plan for the things that can’t be addressed quickly. It doesn’t need to be an elaborate document. A one-page summary of the three or four most important development investments is all you need. Make a note of who they’re for, what they involve, and what success looks like by December. Actually writing it down is what makes it plannable rather than aspirational.

As I explored in Balancing Short-Term and Long-Term Goals, the investments that produce the most durable results are rarely the ones that feel urgent in the moment. They’re the ones that get planned and protected during the windows when the pace allows for it. This is that window. The plan you make in the next two weeks will either be followed or forgotten, and it depends almost entirely on whether you write it down.

Summary

The mid-year reset isn’t a formal review. It doesn’t produce ratings or go into files. Nobody requires you to do it, and the floor will keep running whether you do or not.

What it produces is a clearer picture of where your team actually is. Not where you assume they are, not where the metrics suggest they are, but where they truly are. From that picture, you get a specific set of decisions about what the next few months need to look like.

The year is half over. The decisions you make in July still have six months to compound. That’s enough time to develop someone from capable to excellent, to close the process gap that’s been generating friction since winter, to build the depth that makes peak season manageable rather than surviving.

From Theory to Action

1. Block an hour this week for your own assessment. Before any conversation with your team, sit down with your notes from the first half—one-on-ones, shift reviews, incident reports, recognition records—and work through the three self-assessment questions in this article. Where did you misread something? Where did your development attention actually go? What conversations are still pending that shouldn’t be? Write the answers down. The act of writing makes the gaps harder to rationalize away.

2. Schedule reset conversations with each of your direct reports before the end of July. Not a regular check-in. A specifically designated reset conversation: ten minutes, clearly framed as a step-back conversation about the second half. When you schedule it, tell them what it’s for: “I want to spend some time talking about where you are and what you want the next six months to look like.” That framing changes the quality of what they bring to the conversation.

3. Run the Team Capability Mapping exercise with Q3 and Q4 demands in mind. Use the Team Capability Mapping guide — but run it forward, not backward. The question isn’t “how did my team perform in Q1?” It’s “what will my team need to do well in Q4, and what’s the gap between that requirement and current capability?” Write down the top three gaps. Those are your development priorities for the second half.

4. Triage what you find before you plan. When the reset surfaces more gaps than you can address at once, sort them into three groups: overdue and urgent, tied to a Q4 operational demand, and developmental with no hard deadline. Address the first group this week. Plan the second group now. Schedule the third group for the second half without letting it crowd out the first two.

5. Address the one thing that should have been fixed already. In almost every reset, something emerges that should have been addressed earlier and wasn’t. Pick the most important one and fix it before the end of this week. The speed of the response signals that the reset produced something real.

6. Write a one-page second-half plan. Three or four development investments, each with a name, a specific goal, and a rough timeline. Not an elaborate document, a page that answers the question: if someone reads this in December, would they know what I was trying to build and whether I built it? Put it in your Growth Documentation System where you’ll see it regularly.

7. Have the conversation with the person who’s ready for more. Every team has someone who’s been performing at or above the ceiling of their current role for months and is waiting for the next step. The reset conversation will surface them if you haven’t already identified them. Don’t wait for an opening to appear. Create one—a stretch assignment, a genuine development conversation, a responsibility shift that signals you’ve noticed where they are and where they could go.

Performance rarely drops randomly.

There’s almost always a trigger — a shift change, a process update, a change in equipment, a change in team composition, a change at home. If you can identify what changed around the time the issue started, you can usually identify what category the problem lives in. The trigger is the clue.

Take Action: Identify when a current performance issue started. Then write down everything that changed in the operation, the team, or the person’s circumstances around that time. The trigger is almost always in that list.

I spent weeks coaching a lighting problem.

In the late summer of 2018, a string of collisions in my trailer yard turned out to have nothing to do with my drivers. The yard lights hadn’t adjusted for earlier sunsets. There was a 15-20 minute window every evening when drivers were parking in near-darkness. New timer settings. Problem solved.

Take Action: Before your next performance conversation, physically walk the area where the issue is occurring. Look at the equipment, the lighting, the setup. Spend ten minutes looking at the environment before you look at the person.

Every system is perfectly designed to get the results it gets.

Deming said this about processes, but it applies directly to performance. If your system is producing an outcome you don’t want, the first question isn’t what’s wrong with the person producing it — it’s what in the system is making that outcome possible. Reframing the question changes everything about what you do next.

Take Action: Choose one recurring performance issue. Ask yourself: what in the setup of this role makes this problem easy to produce? Write one sentence answering that question before your next shift.

The assumption almost always lands on the person.

When performance drops, our instinct is to look at the individual — their effort, their attitude, their engagement. That instinct is understandable. It’s also, more often than not, the wrong place to start. The person is the last place the problem lives.

Take Action: Think of one current performance issue on your team. Before your next conversation about it, write down three things in the environment — equipment, process, scheduling — that could be contributing. Start there.

In the late summer of 2018, I was managing a trailer yard on the 18:00 to 06:00 shift, and we started seeing something I hadn’t encountered before: a string of collisions. Day after day, drivers parking trailers in the yard were clipping the trailers in the spaces next to them. Not dramatically, never any serious damage. But consistently enough that I had to take it seriously.

My first assumption was what most managers’ first assumption would be: something had changed about how my drivers were operating. I started talking to them about being more careful, asking for a spotter when the spacing was tight, looking for spaces with more room before committing to a tight one. I thought I was addressing it.

I wasn’t. The collisions kept happening.

Every shift, I went into the site sync meeting with other department leaders and explained that yes, we’d had another incident. Then another. Then another. By the fourth or fifth incident report in a single week, I had run out of new things to say in that room. Whatever I was doing clearly wasn’t working, and I was out of ideas.

Finally, one of the other department managers asked me a question I hadn’t thought of: what was the lighting like in the yard when the collisions were happening?

That was it. The yard lights were on a timer that had been set earlier in the summer, when the sun went down later. By late summer, the sun was setting earlier—but the lights weren’t coming on until the same time they always had. There was a fifteen to twenty minute window every evening when the yard was genuinely dark and the lights hadn’t kicked on yet. My drivers hadn’t been parking carelessly. They’d been parking in the near-dark.

The facilities team adjusted the light timers. The collisions stopped immediately.

I had been coaching a lighting problem.

The Default Assumption

When someone’s performance drops, the instinct is to look at the person. Are they engaged? Are they putting in the effort? Do they understand the expectations? Is there an attitude issue here?

These are reasonable questions. They’re also, more often than not, the wrong starting point.

W. Edwards Deming, whose influence on manufacturing and operations management has touched almost every warehouse and production floor that takes quality seriously, had a principle that I return to constantly: “Every system is perfectly designed to get the results it gets.”

When I first came across that idea, I read it as being about process improvement. And it is, in part. But the deeper application that I’ve found most useful as a manager is about performance diagnosis. If your system is producing an outcome you don’t want, the first question isn’t what’s wrong with the person producing that outcome. It’s what’s in the system that’s making that outcome possible, or likely, or even inevitable.

This should change everything about how you approach a performance conversation. Instead of starting with the person and working outward to find context, you start with the context and work inward to find the person. You’ll often discover that the person is the last place the problem lives.

Before you decide you have a performance problem, ask yourself whether you might have a system problem, an equipment problem, a training problem, or an environment problem wearing a performance problem’s clothing.

What’s Actually Masquerading as a Performance Problem

These categories aren’t exhaustive, but in my experience they cover the vast majority of situations where a manager is about to have the wrong conversation.

The most literal category is equipment and environment. Yard lighting that doesn’t account for how early the sun sets in autumn. A workstation at the wrong height for someone who isn’t average height. A radio that doesn’t work reliably, forcing someone to make decisions with incomplete information. Background noise at a level that makes it difficult to hear instructions clearly. None of these show up in the data as equipment or environment problems. They show up as collision rates, productivity drops, quality issues, and missed communications. The people experiencing them often don’t connect the dots either or, if they do, aren’t sure whether it’s worth mentioning. And the manager, looking at the numbers, sees a performance pattern and reaches for a coaching conversation.

System and process problems are subtler but just as common. When I wrote about process improvement fundamentals, I mentioned something that bears repeating here: if your system makes the wrong thing easy and the right thing hard, you’ll get the wrong thing, regardless of coaching. A procedure that’s ambiguous at a critical decision point will produce inconsistent results. A handover process that doesn’t transfer key information will produce errors in the shift that inherits the gaps. The diagnostic tell is that the issue follows the process, not the person. When you see the same error type appearing across different associates, or at the same point in a shift regardless of who’s working, you’re almost certainly looking at a system issue. No amount of individual coaching fixes a procedural ambiguity; it just moves the inconsistency around.

Training gaps are particularly common with associates who’ve been in a role for a few months—long past the point where anyone thinks of them as new, but still operating with gaps from an onboarding that covered the standard cases without fully preparing them for the edge cases. They’ve been managing around those gaps and at some point the workaround fails. In last year’s post 7 Early Warning Signs of Performance Issues, I wrote about how performance problems often develop gradually before they become visible. Training gaps follow this pattern too. The associate seemed fine for months because the work was within the range they were prepared for. Then something shifted (volume, complexity, a role change, a new process) and the gap became a liability.

The hardest category to identify from the floor is scheduling and personal factors. A person whose sleep is being disrupted by a shift change they’re struggling to adapt to. Someone whose commute changed and is now arriving with less recovery time than before. A home situation that’s creating sustained background stress. These show up in the performance data as energy drops, attention lapses, and inconsistency that looks, from the outside, like effort. This is also the category where the gap between “this looks like a performance problem” and “this is a person going through something difficult” is most consequential, and where genuine curiosity matters more than any diagnostic framework.

The Diagnostic Shift

In the 5-Why Technique for Warehouse Problem Solving, I wrote about a reframe that changed how I investigate recurring problems: instead of asking “why did this happen?”, ask “why was it possible for this to happen?”

The first question points at the person or the moment. The second question points at the system: the conditions that allowed the error to occur, the gaps that made the outcome possible, the environmental factors that no one thought to examine. It’s a more useful starting point for almost every performance situation, not just operational ones.

Applied to performance, the shift sounds like this: instead of “why isn’t this person hitting rate?”, ask “what would make it difficult for anyone in this position to hit rate?” Instead of “why does this associate keep making this error?”, ask “what in the setup of this role makes this error easy to make?”

Those questions don’t excuse performance issues. They locate them. And locating a problem correctly is the prerequisite for addressing it effectively, something I learned the hard way through a week of embarrassing site sync meetings before a colleague asked me about the lighting in my yard.

Before going into any performance conversation, I now work through four questions:

• What changed around this person around the time the issue started? Performance rarely drops randomly. There’s almost always a trigger. A shift change, a process update, a change in equipment, a change in who they’re working alongside, a change at home. If I can identify what changed, I can usually identify what category the problem lives in.

• Has this person performed well at this role before, under different conditions? If yes (and for most performance issues in people who aren’t new, the answer is yes) the question is what conditions are different now. If no, the question is whether they were set up for success in the first place.

• Have I looked at the environment they’re working in? Literally looked. Have I walked the area, checked the equipment (and the lights), asked whether anything is harder about this position than it should be?

• What does the person themselves say is making it hard? People know things about their own experience that don’t appear anywhere in the data. The person who’s struggling usually has some sense of what’s contributing. They may not have connected all the dots, and they may not have felt it was their place to say anything, but they know things. Ask.

What Changed?

The single most diagnostic question in a performance drop is: what changed?

Not “what changed about the person?” What changed in the situation? The shift pattern. The team composition. The physical setup. The process they’re following. The manager they’re reporting to. The pace of the operation around them. The handover they’re receiving.

My systemic approach to this full root cause process is what I covered in The 5-Why Technique for Warehouse Problem Solving. But you don’t need the full technique every time. The minimum viable version is just the question: what changed, and when did it change relative to when the problem started?

When It Is the Person

None of this is an argument against ever concluding that a performance issue is fundamentally about the individual.

Sometimes it is. Genuine effort issues exist. Genuine attitude issues exist. I wrote about The Conversation You Keep Postponing and the shared the structures in the Difficult Conversations Planner exist because they’re needed. A manager who responds to every performance problem by looking for a system to fix is avoiding individual accountability as surely as a manager who responds to every system problem by looking for a person to coach.

The distinction between the two isn’t always clean. What it requires is diagnosis, a genuine effort to understand the situation before deciding what it is, rather than assumption. The assumption almost always lands on the person. The diagnosis sometimes gets there too. But it arrives there by a route that’s more honest and more useful.

The question that keeps this honest is a simple one: if I put a different person in exactly this situation—same station, same shift, same equipment, same handover—would they produce the same issue? If the answer is probably yes, you have a system problem. If the answer is probably no, you have a person problem. The diagnosis flows from that distinction.

Summary

Most performance problems look, from the outside, like something wrong with the person. The numbers drop. The quality slips. The errors repeat. The data points at the associate, and the instinct is to start there.

The better starting point is the system. The equipment. The environment. The training. The process. What changed around this person, and when? What would make it difficult for anyone in this position to perform at the expected standard? What does the person themselves say is making it hard?

Deming was right: every system is perfectly designed to get the results it gets. Before you decide the result you’re getting is a performance problem, ask whether your system might be producing it for reasons that have nothing to do with the person experiencing it.

From Theory to Action

1. Before your next performance conversation, look at the environment. Physically. Walk the area. Check the equipment and conditions. Ask whether anything about the setup is harder than it should be. You’re looking for the thing that wouldn’t show up in the data: the lighting problem, the equipment problem, the workstation problem. The collisions in my yard didn’t show up as a lighting issue in any report. They showed up as driver errors. Ten minutes of looking at the environment before a coaching conversation is worth more than an hour of coaching a problem you haven’t correctly located.

2. Ask “what changed?” before you ask “what’s wrong?” Think back to when the performance issue started. What changed in the operation, the team, the process, or the person’s circumstances around that time? If you can’t identify a trigger, that’s important information too. But in most cases, performance drops have a starting point and the starting point is a clue.

3. Look for the pattern, not just the person. Is this error type appearing with multiple people? At the same point in the process? On a specific shift? If the problem follows the process rather than the person, you’re looking at a system issue. No individual coaching will solve it; something in the setup needs to change. The 5-Why Technique is the right tool for this investigation.

4. Ask the person what’s making it hard. “I’ve been looking at your numbers and I want to understand what’s getting in the way. What’s making this difficult?” The answer won’t always reveal something environmental. But it will often surface something you didn’t know, something that changes what you do next. People who are struggling usually have some sense of the contributing factors; they may just not have felt it was their place to raise them. My drivers knew the yard was dark, but none of them thought to mention it, and I never thought to ask.

5. Run the substitution test. Before deciding the problem is the person, ask: if I put a reliable, experienced associate in exactly this situation—same station, same shift, same equipment, same handover—would they produce the same issue? If yes, fix the system. If no, you may have an individual performance situation. Either way, the test tells you where to look.

6. Separate the diagnosis from the conversation. The Difficult Conversations Planner and the framework in The Conversation You Keep Postponing are the right tools once you’ve determined the problem is fundamentally about the individual. But run the diagnosis first. The conversation you have after correctly locating the problem is more specific, more fair, and more likely to produce something useful — both for the person and for your operation.

7. Document what you find. Whether the diagnosis leads you to a system fix or a performance conversation, write down what you found and what changed. Your Growth Documentation System is the right place for this. Pattern recognition across multiple situations — seeing that the same station produces problems for multiple people, or that a specific process step keeps generating errors — is only possible if you’ve kept records. The lighting problem in my trailer yard took longer to solve than it should have partly because nobody had documented the fact that the collision rate at that time of evening had been elevated before. The pattern existed. It just wasn’t written down anywhere.

You know the one.

You’ve known about it for a while. It pops in your head during the pre-shift, during the drive home, during the quiet moments of a slow night when there’s nothing else demanding your attention. You’ve rehearsed versions of it. You’ve thought about how she might respond, what you’d say next, whether it would go well or badly. You’ve decided to have it at least three times and then found a reason not to.

It’s not that you don’t care. You do, and that’s precisely why it’s uncomfortable. You care about the person, you care about the outcome, you care about doing it right. But somehow that caring has become the thing that keeps you from starting.

I had one of those conversations once that I waited on for five weeks. Five weeks of watching the same pattern repeat, telling myself it would resolve, adjusting coverage around it, and privately becoming more frustrated with every shift that passed without anything changing. By the time I finally had it, the situation had escalated from something I could have addressed in fifteen minutes to something that required HR involvement and documentation. What could have been a coaching conversation had become a formal performance process.

The person on the other end deserved to have been told sooner. So did my team, who had been compensating for the problem while I waited for the right moment. The right moment, as it turned out, had been five weeks ago.

You Already Know

The most important thing to understand about the conversation you keep postponing is that you already have what you need to have it.

You have the observation. You’ve seen the pattern—the attendance, the quality, the attitude, whatever it is—play out enough times that there’s no longer any doubt about whether it’s real. You have the impact. You know what it’s costing the team, the operation, the standard you’re trying to hold. You even have a general sense of what you want the outcome to be.

The only thing you don’t have is certainty about how it will go. And that uncertainty, the possibility of a defensive reaction, of tears, of denial, of making things worse, is the thing that feels like a reason to wait.

It’s not a reason to wait. It’s the nature of the conversation. The uncertainty doesn’t disappear if you wait another two weeks. It just gets packaged with a larger problem.

Seventeen Reasons to Wait

You probably recognize some of these.

She just came back from leave. This isn’t a good time. The timing never feels ideal, and there will always be a reason that this particular week is slightly worse than next week.

I don’t have enough specific examples yet. You have three from the last month. You’re waiting for a fourth so you feel more prepared. The fourth arrives, and you decide five would be better.

He seemed to be doing better this week. One good shift shouldn’t reset the conversation. You know that. But it gives you permission to wait, and you take it.

I need to give her a chance to turn it around on her own. She’s had that chance. Several of them. The pattern continues because nothing has clearly communicated that it needs to stop.

It’ll create awkwardness on the floor. The awkwardness already exists. It exists in every shift where the standard applies to nine people and doesn’t apply to one. You’re the only one pretending otherwise.

I don’t want to damage the relationship. The relationship is already being damaged by the absence of honesty, by the gap between what’s happening and what’s being said, by the slow erosion of trust your team has in a manager who sees something and says nothing.

Each of these feels like a legitimate reason in the moment. Laid out together, they’re a list of rationalizations that share a single function: they let you wait one more shift, one more week, one more month, without having to acknowledge that you’re waiting.

What the Delay Is Costing

Ten years ago I heard a principle that has stayed with me: “Easy choices, hard life. Hard choices, easy life.” The postponed conversation is the easy choice that makes the longer game harder for everyone involved.

For the person at the center of the conversation: every week you wait is a week they operate without honest information about how they’re being perceived. They may have no idea there’s a problem. Or they may suspect something is wrong but can’t address it because it hasn’t been named. Either way, they’re working in the dark and that’s not fair, however uncomfortable it is to say so.

For the team: they can see what you can see. The associate whose attendance has been inconsistent, the team lead whose quality has been slipping, whatever it is, the people working alongside them know. And what they’re also watching is how you respond to it. Every week you don’t address it is a week they get a data point about what the standard actually is around here, and whose behavior is subject to it.

For your own credibility: the longer you wait, the harder the eventual conversation becomes. By the time you have it, you’re not just addressing a performance issue. You’re accounting for the gap between when you first saw it and when you said something. That gap matters. People notice it. It shapes how they experience the conversation and how much they trust that your management of them is honest.

As I wrote in Creating Accountability Without Constant Oversight, accountability that only lands when a problem is unavoidable isn’t accountability, it’s crisis management. The conversation you keep postponing is a place where that distinction becomes very real, very fast.

The Myths That Keep You Waiting

There are a few deeper beliefs worth examining because they sound more legitimate than “I’m uncomfortable” but are doing the same work.

The first is the evidence myth: I need to have all my evidence ready. You need enough specific, observable examples to make the conversation factual and grounded. You don’t need a case file. Two or three clear instances with dates and impacts is sufficient. The search for more evidence is often a search for a confidence or comfort that the evidence was never going to provide.

Closely related is the composure myth: I should wait until I’m calm. There’s a version of this that’s true. You shouldn’t have the conversation in the immediate heat of frustration. But calm can become indefinitely delayed very quickly. If you’re consistently too frustrated to have the conversation, that’s worth examining as its own issue. Mild discomfort isn’t the same as being too emotional to proceed.

Then there’s the resolution myth: maybe it will resolve itself. Occasionally it does. Mostly it doesn’t. And the version of the problem that resolves itself is almost always smaller than the version you’re currently looking at. If the issue has been present for more than two weeks, waiting for spontaneous resolution is optimism at the team’s expense.

Finally: I’m not sure how to start. This one is actually solvable, and the next section addresses it directly. But notice that this reason usually arrives late in the rationalization process: after the timing, the evidence, and the possibility of self-correction have all been exhausted. Not knowing how to start is a logistics problem. The others are avoidance masquerading as judgment.

What “Ready Enough” Actually Looks Like

Ready enough is:

• You can describe the specific behavior in observable terms: what you’ve seen, how often, with what impact on the operation or the team.

• You have a clear sense of what you want to be different after the conversation. Not a vague hope for improvement, but a specific change that would tell you things had shifted.

• You’ve chosen a time and place where the person has some privacy and the conversation won’t be interrupted mid-sentence by a radio call or a shift handover.

That’s it. That’s ready enough.

You don’t need to have anticipated every possible response. You don’t need to have planned a rebuttal for every objection. You don’t need to have scripted it word for word. Those preparations can be genuinely useful; the Difficult Conversations Planner walks through exactly this kind of structured preparation. But the absence of them isn’t the reason you haven’t had the conversation yet. The reason is the one we’ve been discussing.

Ready enough is almost always available sooner than it feels like it is.

The First Sentence

The hardest part of the conversation is starting it. Once it’s underway, the momentum carries you. The silence before the first sentence is where most of the delay lives.

In my experience, the openings that work best in an operational environment are short, direct, and non-accusatory. They state the purpose without editorializing. Something like:

“I’ve been wanting to talk with you about something I’ve been observing, and I want to do it while I still have a chance to be helpful.”

Or:

“There’s something I’ve been watching over the last few weeks that I want to discuss with you, because I think it’s important and because I respect you enough to say it directly.”

Both of these do something specific: they frame the conversation as one the manager is having because they care, not because they’ve run out of other options. That framing matters. The person on the other side of the conversation picks up on whether they’re the last resort or the first response. After five weeks, I was the last resort. The conversation I should have had in week two would have been the first response — and it would have landed very differently.

From the opening, the conversation follows a structure worth preparing for: what you observed, the impact it had, a genuine question about what’s going on from their side, and a clear picture of what needs to change. All of that is covered in detail in the Difficult Conversations Planner for Manufacturing Leaders, which exists precisely for this purpose.

The article you’re reading is about getting you to the first sentence. The planner will help you with what happens next.

Summary

The conversation you keep postponing probably isn’t as complicated as it feels from a distance. What’s keeping it in the future isn’t a lack of information, a lack of preparation, or a lack of opportunity. It’s your preference for avoiding discomfort and the cost that preference is imposing on everyone else.

The person at the center of it deserves to know. Your team deserves to see you act on what you can see. And your own credibility as a manager depends, in part, on the gap between when you notice something and when you say something being as small as possible.

Ready enough is closer than it feels. The first sentence is shorter than the one you’ve been rehearsing. And the conversation, almost always, goes better than the version you’ve been running in your head.

The right time to have the conversation you’ve been postponing was probably two weeks ago. The second-best time is before the end of this shift.

From Theory to Action

1. Name the conversation you’ve been avoiding. Specifically. Write it down if that helps: who, what pattern, how long. Getting it out of your head and into a sentence is the first step toward having it.

2. Calculate the cost honestly. How long have you been aware of this? What has it cost the team in that time? In coverage, in morale, in the resentment that comes from watching a standard applied inconsistently? What has it cost the person, who has been operating without honest feedback? Write that down too. The discomfort of the conversation usually shrinks when it’s placed next to the cost of postponing it.

3. Set a deadline, not a plan. Don’t decide that you’ll have the conversation when the time feels right. Decide that you’ll have it before the end of the week, or before a specific shift, or before a specific date. A deadline with a consequence creates a different kind of urgency than “soon.”

4. Prepare the first two sentences. Just the first two. Use the opening frameworks from this article or develop your own, but write out how you’ll start. Practice saying them out loud once. The hesitation lives before the first sentence; once you’ve said it out loud, even alone, it becomes a thing you’ve done rather than a thing you’re about to do.

5. Use the Planner. The Difficult Conversations Planner for Manufacturing Leaders is the companion tool to this article. It walks through preparation, framing, listening, and follow-up in detail. Once you’ve committed to having the conversation, the planner gives you the structure for making it productive. Download it, fill in the relevant sections, and take it with you if it helps. Most people find that the preparation process alone, working through the specifics of what they want to say, significantly reduces the anxiety around the conversation before it even begins.

6. Debrief yourself afterward. The conversation will not go exactly as you planned. It never does. When it’s done, give yourself ten minutes to think through what happened: what you said, how they responded, what you’d do differently. That reflection, practiced consistently, is what builds the skill. The first difficult conversation you have will feel harder than the fifth. The fifth will feel harder than the twentieth. They don’t stop being uncomfortable. They stop being paralyzing.

Last week I got a message from a manager that had attended one of my training sessions a couple months ago.

He wanted to catch up. I was excited to hear from him; he’d been one of the sharpest people in the room. He was fresh out of college and new to the industry, but he picked up concepts quickly, asked good questions, and left class energized and ready to apply what he’d learned. Those are the people you remember. Those are the conversations that remind you why you do this work.

The Zoom call didn’t go the way I expected.

He wasn’t calling to share a win. He was calling because he was struggling, badly, and he didn’t know what to do. He walked me through the past eight weeks. His planning approach, his staffing practices, the relationships he was trying to build. It was all textbook. He understood what standard work looked like. He knew what best practices were. He’d taken what we covered in class and was actually trying to implement it, which is more than I can say for a lot of managers I’ve trained.

But it wasn’t working. And it wasn’t because of anything he was doing wrong.

The Call I Wasn’t Prepared For

By the time he had come to my training session, he knew his site had some challenges. What he didn’t fully understand yet was how deep those challenges ran. This was a facility with a long reputation for some of the worst performance numbers in the network. Not a site in a rough stretch—a site with a deeply ingrained culture of underperformance that had calcified over years.

His peers had been operating a certain way for a long time, and they had no interest in changing. When he pointed to standard work, they dismissed it. “This is how we’ve always done it.” When he flagged that a particular practice contradicted established policy, senior leaders shrugged it off. “That’s more of a suggestion than a requirement.” There was always an excuse, always a reason why the rules that applied everywhere else somehow didn’t apply here.

He had moved across the country for this job. He’d expected to build skills, make an impact, grow. Instead, he felt like he was banging his head against a wall built by people who had decided a long time ago that the wall wasn’t moving.

By the time we talked, he was near tears.

He asked me what he was supposed to do. And I sat there, on the other side of a Zoom screen, struggling to find the right answer.

I’ve been thinking about that conversation ever since. I want to give him (and anyone else in a similar position) the response he deserved.

A Wall Built Over Years

This is what happens at facilities with long-running performance problems. The dysfunction stops feeling like dysfunction and starts feeling normal. People aren’t defending bad practices because they’re lazy or malicious. They’re defending them because those practices are the culture, and the culture is the only operational reality they’ve ever known.

I wrote about this in The Culture You’re Building Without Knowing It. Culture isn’t a set of values on a poster. It’s the accumulation of what leaders have rewarded, tolerated, and modeled—day after day, shift after shift—until those patterns become invisible. When you arrive and say “this isn’t how it’s supposed to work,” you’re not just challenging a process. You’re challenging people’s identity and sense of competence.

That’s why the resistance he’s encountering is so fierce. It isn’t really about the standard work. It’s about what acknowledging the need for change would mean for everyone who’s spent years doing it differently. Competence is threatening when incompetence has become comfortable.

One other factor that makes his situation especially hard is that he’s new. He has no formal authority over his peers. He has no relational equity built with senior leaders. He has knowledge and enthusiasm, but in a dysfunctional culture, those can actually work against you.

You Can’t Push a Culture Sideways

Early in my career, I worked at a site that had pockets of serious dysfunction. Not site-wide the way his site is, but deep enough in certain departments to feel like quicksand. I remember trying to implement a process improvement in one area and encountering the exact same wall: “We’ve tried that before.” “That doesn’t work here.” “You don’t understand how this place operates.”

I had more tenure at the time than this young manager, and I still couldn’t move the needle on my own. What I eventually learned is that you cannot change a culture from the side. Culture changes from the top or it doesn’t change at all.

This is a hard truth, and I wish I’d said it more clearly on that Zoom call.

A new manager, no matter how talented, no matter how right, cannot single-handedly transform a facility culture that has been building for years. That’s not a failure of leadership ability. That’s just reality. As I’ve written before, the boundaries of what any individual manager can control are real, and understanding those boundaries is part of becoming a leader who lasts.

What you can do is decide how you operate within that environment and what you do next.

The Things That Are Still Yours to Control

When the organization above you and around you is working against you, you’re left with a smaller, but still meaningful, set of choices.

Control your own department. You may not be able to change how the site operates, but you can control how your team operates. Set and maintain clear standards within your four walls. Be consistent. Be fair. Be present. Over time, a well-run department becomes visible. It becomes a contrast that other people notice—and that senior leaders eventually have to acknowledge.

Document everything. When a senior leader tells you to do something that contradicts standard work, write it down. Note the date, who told you, and what they said. This isn’t about building a case against anyone. It’s about protecting yourself, understanding patterns, and having a clear record of what you were asked to do and by whom. If something goes wrong, you want to be able to show that you raised concerns.

Build relationships before you fight battles. One of the mistakes new managers make in resistant cultures is leading with confrontation. They’re right about the standards, but they haven’t yet built the relationships that give them credibility. Spend time understanding why people do things the way they do. Ask questions before making arguments. You’re more likely to move people who feel understood than people who feel attacked.

Find an ally. In almost every dysfunctional environment, there is at least one person who sees what you see and is quietly frustrated by it. Find that person. Build that relationship. Two voices are harder to dismiss than one, and an ally reminds you that you’re not crazy when everything around you is telling you otherwise.

Holding the Line Without Picking Every Fight

There’s a version of “standing your ground” that destroys your credibility and a version that builds it. The difference is mostly in how you do it.

You don’t have to be combative to be principled. When someone tells you “that’s how we’ve always done it,” you don’t have to argue. You can simply say: “I understand that’s been the approach here. My intention is to follow standard work in my area, and I want to understand if there’s a reason I shouldn’t.” That’s not weakness. That’s someone who knows what they stand for and isn’t apologizing for it, but also isn’t picking a fight they can’t win.

If you’re being pressured to do something that directly violates policy, you have a harder decision. There’s no universal right answer, but the question I’d encourage you to ask is: If this decision were audited, could I defend it? If the answer is no, you probably already know what you need to do.

The goal isn’t to win every argument. The goal is to maintain your integrity and your professional reputation in an environment that may not value either. That reputation is portable. It goes with you when you eventually leave.

The Question of Whether to Stay

This is the part I wish I’d said more directly on that call.

Some environments are not fixable from the inside, especially not by one person, especially not quickly. If you are being actively directed to violate policy, if the dysfunction is affecting your ability to operate ethically, or if the cost to your own development and wellbeing is too high, staying is not automatically the right choice.

Sometimes the best thing a struggling facility can teach you is that you deserve to be somewhere better.

That’s an uncomfortable thing to say, because we tend to treat quitting as failure. But there’s also a trap in the other direction: treating leaving as the obvious answer just because things are hard.

They’re not the same thing. Difficulty is often exactly where real development happens. Some of the most important growth of your career will come from situations that felt, right in the middle of them, completely fruitless. The standards you held when no one was supporting you. The calls you made correctly when the pressure was to make them wrong. Those experiences build something that easier environments simply can’t.

Leaving may be the right call. If you’re being asked to compromise your ethics, if the environment is actively preventing your development with no sign of movement — those are real reasons to go. But it shouldn’t be the automatic answer just because it’s hard, or because you can’t yet see the impact you’re having. Sometimes things push back right up until the moment they change. You won’t know if you leave before that moment arrives.

Ask the question honestly. Just don’t assume you already know the answer.

What I Wish I’d Said

When he asked me what he was supposed to do, I didn’t have a clean answer on that call. I still don’t, entirely. But I’ve had more time to think about it since, and here’s where I’ve landed.

He isn’t failing. The environment is failing him. Those are different things, and I hope he understands the difference. An environment like that has a way of making you feel like the problem is you. It isn’t. Knowing policy and standard work, trying to apply it, and running into a wall of people who’ve decided the rules don’t apply to them is not a reflection of his ability. It’s a reflection of the culture he walked into.

What I’d tell him now: protect your integrity above everything else. Run your department the right way. Document what you’re being told to do when it conflicts with policy. Find the one person on that site who sees what you see. And be honest with yourself about whether this is a place where you’re growing—or just surviving.

Whatever he decides about staying, I’d want to tell him one more thing: don’t let this experience make you cynical. There are operations out there led by people who are genuinely trying to do things right. The fact that he cares this much—that he teared up on a Zoom call because he wanted to do the job well and couldn’t get the space to do it—tells me he’ll be the kind of leader those places are looking for.

From Theory to Action

If you’re a new manager navigating a resistant or dysfunctional culture, these steps won’t fix everything — but they’ll help you hold your ground with your integrity intact.

1. Separate the culture from your competence. When the environment works against you despite your best efforts, that reflects the environment, not your ability. Don’t let a broken culture write your self-assessment.

2. Run your area by the book, consistently. You may not be able to change the site, but you can control your department. A well-run area becomes visible over time, and visibility becomes leverage.

3. Document directives that conflict with policy. Keep a private log: date, person, what was said. You’re not building a case against anyone. You’re building a record that protects you if something goes wrong.

4. Lead with curiosity, not confrontation. When you hit resistance, try “Help me understand why we do it this way” before “that’s not standard work.” You’ll build more goodwill and learn more about what you’re actually dealing with.

5. Find one ally. Almost every struggling site has at least one person quietly frustrated by the dysfunction. That relationship reduces isolation and makes your voice harder to dismiss.

6. Create upward visibility. Find appropriate ways to let leaders above your immediate chain know you’re running things the right way, without throwing anyone under the bus. That reputation travels.

7. Ask the hard question regularly. Every month or two: Am I developing here, or just enduring this? Growth is the reason you took the job. If the environment is actively preventing it, staying is a choice, not an obligation.

8. Remember that your reputation is portable. Whatever you do in your current role, make sure it’s something you’d be proud to take somewhere else. An environment that pressures you to compromise your standards is borrowing against your future. Don’t let it.

If this post resonated with you, or if you know a new manager navigating a situation like this, share it with them. Sometimes the most important thing we can offer someone who’s struggling is the reminder that what they’re feeling makes sense.

About fourteen months into my role as a department manager, I noticed something in our near-miss reporting data that I initially read as good news.

The numbers were dropping. Fewer near-misses being reported week over week. My first instinct was to feel good about it; the floor was running better, people were being more careful, the safety culture was improving.

A more experienced operations manager (one of the best I’ve ever worked with) set me straight. He looked at the data and said something I’ve never forgotten: “When near-miss reports go down, it usually means one of two things. Either your floor got dramatically safer, or your people stopped feeling safe enough to report. Which one do you think it is?”

I knew the honest answer. We hadn’t changed anything operationally that would explain a dramatic safety improvement. What had changed was that I’d responded to a couple of recent reports with more visible frustration than I’d intended. Not at the reporters, but at the situations they’d described. But that distinction, from my team’s perspective, was invisible. The signal that had landed was: reporting problems creates a reaction from the manager that feels unpleasant. So people started reporting fewer problems.

That’s when I understood what psychological safety actually costs when it’s missing. Not just engagement. Not just morale. Near-miss reports. The early warning system that stands between a manageable situation and something that puts someone in the hospital.

What the Term Actually Means Here

“Psychological safety” has become one of those phrases that gets used so frequently in management writing that it starts to lose its edges. In office environments, it often gets translated as: people feel comfortable sharing ideas in meetings, giving honest feedback upward, and taking creative risks without fear of ridicule.

That’s real and it matters. But on a production floor, the stakes are different and the translation has to be more specific.

On the floor, psychological safety means one concrete thing: your team brings you problems before they become crises.

The associate who notices something wrong with the equipment at the start of shift and says something rather than assuming it’ll be fine and not wanting to slow the line. The team lead who flags a quality concern even though it might delay shipment, rather than hoping the next shift catches it. The new hire who admits she doesn’t understand a procedure rather than guessing and potentially creating a safety issue because asking doesn’t cost her anything.

Psychological safety on the floor isn’t about feelings. It’s about whether problems surface before they become crises.

None of those moments require a particularly brave person. They require an environment where speaking up doesn’t carry a cost. Where the manager’s response to a problem being surfaced is curiosity and action, not frustration. Where the last person who raised a concern isn’t being talked about in ways that discourage the next person from doing the same.

When that environment exists, your floor becomes what I describe in Leading From the Floor as an early warning system. Problems get addressed during planned downtime rather than becoming emergency shutdowns. Quality concerns get investigated before defects reach customers. Near-misses get documented and fixed before they become incidents.

When it doesn’t, problems go underground. They keep happening. They just do it quietly.

How It Gets Destroyed (Usually Accidentally)

Most psychological safety damage on the floor isn’t caused by managers who berate people or create genuinely hostile environments. It’s caused by managers who respond to problems in ways that make problems feel slightly costly to surface. Not dramatically, not obviously, just enough that the calculation shifts over time.

A team lead reports an issue and the manager’s first response is “why didn’t you catch this earlier?” A near-miss gets documented and the manager spends the debrief focused on what went wrong rather than on what was learned. An associate raises a concern during a pre-shift and the manager moves past it quickly, visibly preoccupied with something else.

None of these responses is villainous, but all of them send a signal. And that signal, compounded over dozens of interactions, builds a floor culture where people have learned that raising problems is more trouble than it’s worth.

I wrote about this in The Culture You’re Building Without Knowing It. Culture isn’t what you intend, it’s what you consistently do and allow. The same mechanism that builds a culture of development or accountability builds or erodes psychological safety, one small response at a time.

The other common mechanism is what happened to an associate I inherited when I took over another team. His previous supervisor had publicly criticized a decision he’d made—a decision that turned out to be correct, but had an unexpected outcome he hadn’t anticipated. This associate was competent, experienced, and well-regarded by his peers. But he was consistently escalating quality decisions to me that he had the authority and judgment to make himself, because the cost of independent judgment, in his recent experience, was being publicly wrong in front of his team even when he was right.

No amount of reassurance fixed it immediately. What rebuilt it was a deliberate pattern of small, low-risk moments where I explicitly supported his judgment regardless of outcome, debriefed what went right rather than what could have gone better, and made it clear through repeated behavior—not just words—that his judgment was trusted here.

The High-Confidence Problem

There’s a version of psychological safety damage that doesn’t come from the manager at all. It comes from the floor itself. Specifically, from the highest-confidence voices on it.

In When Your Best Player Makes Your Team Worse, I wrote about the ways star performers can unintentionally block the development of the people around them. The same dynamic operates here. When the most experienced, most confident person on the floor reacts to a newer associate’s concern with visible impatience,“That’s not an issue, we’ve always done it this way,” she may not be wrong about the specific situation. But the signal that lands isn’t about the specific situation. It’s about whether raising concerns is worth the social cost.

Your highest-confidence team members are some of the biggest determinants of psychological safety on your floor but most managers don’t treat them that way. How they respond when someone surfaces a problem in front of them matters enormously. Whether they ask questions or dismiss them, model curiosity or signal boredom, encourage or roll their eyes.

This is one reason the conversation I described in the previous article, about reframing what excellence looks like for your star performers, has direct psychological safety implications. A team lead who understands that her job includes creating conditions where people around her feel safe to speak up is doing something qualitatively different from one whose standard is simply handling everything herself.

What Building It Actually Looks Like

It’s built the same way culture is built: through small, repeated, consistent behaviors that accumulate into a pattern your team can rely on.

The most important habit is how you respond to bad news first. Before you ask what went wrong or who missed something, get in the habit of acknowledging the act of surfacing it. Saying “I’m glad you told me” (and meaning it) is the single most powerful sentence you can say in response to a problem being raised. It’s not about being soft on standards. It’s about separating the act of speaking up from the content of what was spoken. People need to know that surfacing a problem is always the right call, even when the problem itself reflects a mistake.

Closely related is what happens after someone raises something and turns out to be wrong. This is the test most managers fail without realizing it. If an associate raises a concern and it turns out not to be an actual problem, how do you respond? If the response—even subtly—communicates that she wasted your time or should have figured it out himself before saying anything, you’ve just made the next concern marginally less likely to surface. The right response to a false alarm is: “Good catch. Better to check and find nothing than to miss something.” The behavior gets reinforced regardless of the outcome.

Follow-through matters just as much as the initial response. People track what happens to the concerns they raise, even when they don’t discuss it. When something gets surfaced and nothing visibly happens with it, the implicit message is that raising it didn’t matter. You don’t need to give a status update on every minor report. But for anything significant, closing the loop tells the floor that surfacing problems leads somewhere. That knowledge is what sustains the reporting behavior over time.

Finally, watch your visible reaction to near-misses specifically. Near-miss reporting rate is one of the most useful indirect measures of psychological safety on a floor. When it drops without a corresponding operational change, it almost always means people have learned that reporting isn’t cost-free. Review it deliberately. Not as a target to manage, but as a diagnostic. If the number is trending the wrong way, the question to ask isn’t “how do we get more reports?” It’s “what has happened recently that made reporting feel less safe?”

These aren’t complex interventions. They’re habits. And like the accountability habits I covered in Creating Accountability Without Constant Oversight and the recognition habits in Why Positive Feedback Comes First, they work through consistency rather than intensity. One good response to bad news doesn’t build psychological safety. Fifty of them, over months, does.

The Operational Payoff

Psychological safety is often discussed in ways that make it sound like a culture amenity; nice to have, important for morale, relevant when you have space for it. It isn’t.

When near-miss reporting is healthy, safety incidents go down. Not because people are being more careful in some abstract sense, but because the floor’s early warning system is working and small problems get addressed before they become large ones. In my time tracking the correlation between near-miss reporting rates and incident rates, the relationship was consistent: healthy reporting, fewer incidents. The causation runs directly through psychological safety.

Quality works the same way. A team that feels safe to flag concerns catches defects at the source. One that doesn’t ships them downstream. The customer complaint, the return, the re-work; these aren’t quality system failures in the first instance. They’re psychological safety failures that look like quality system failures by the time anyone traces them back.

The cost of a floor where problems go underground isn’t visible in the daily metrics until suddenly it is, in a way that’s hard to ignore. The near-miss that wasn’t reported. The quality concern that nobody raised. The equipment issue that turned into a shutdown because nobody wanted to be the one to slow the line.

Building psychological safety is operational risk management, not just people management. The managers who treat it as the former build floors that are genuinely safer, genuinely higher quality, and genuinely more resilient because their team is working for them, not around them.

From Theory to Action

1. Pull your near-miss reporting data for the last three months. Is it trending up, flat, or down? If it’s down and nothing operationally explains why the floor became dramatically safer, that’s a culture signal worth investigating. Don’t try to reverse-engineer the cause from the data. Ask. A direct, genuinely curious question to a team lead you trust (”Have you noticed any change in how people feel about reporting issues?”) will tell you more than the numbers will.

2. Audit your last five responses to bad news. Not your intended responses—your actual ones. Think back to the last five times a team lead or associate surfaced a problem. What was your first reaction, and what signal did it send about the act of surfacing it versus the content of what was raised? If you can’t remember, that’s useful information too.

3. Practice “I’m glad you told me” this week. Not as a script, as a genuine reframe. The next time someone brings you a problem, before you do anything else, acknowledge that they brought it. Then address the problem. The order matters. The problem gets addressed either way; the acknowledgement is what shapes the next decision about whether to surface something.

4. Watch how your highest-confidence team members respond to concerns. Your stars set the social norms on your floor as much as you do. If your most respected team lead visibly dismisses concerns from newer associates, that behavior is doing more damage to your early warning system than your management responses are building. Address it directly, as a development conversation, not a performance one.

5. Close the loop on something that was raised. Pick one concern from the past two weeks that someone surfaced, formally or informally, and go back to that person with a brief update on what happened with it. Not because one update changes the culture, but because the habit of closing loops, practiced consistently, tells your floor that raising concerns leads somewhere. That knowledge accumulates.

6. Protect the person who’s wrong. The next time someone raises a concern that turns out to be unfounded, pay attention to how you respond and how the people nearby respond. Reinforce the behavior publicly and specifically: “That was the right call. Better to check and be wrong than to stay quiet and miss something.” That sentence, said genuinely in front of the team, does more to protect future reporting than a month of safety training.

7. Use your one-on-ones to surface what you can’t see from the floor. The concerns that never make it to a report almost always exist somewhere in your team leads’ awareness. A direct question like “What are people hesitant to raise with me?” when asked in a context that feels genuinely safe, will surface things you’d never find another way. The fact that you asked is itself a psychological safety signal.

This post concludes the Building High-Performance Teams arc, which began with The Culture You’re Building Without Knowing It, continued through How to Raise the Floor, Not Just the Ceiling and When Your Best Player Makes Your Team Worse, and ends here.

Next: The Conversation You Keep Postponing. This will be the first article in the Performance Management arc, looking at the feeling of knowing you need to have a difficult conversation and finding seventeen reasons to wait.

Elena was the kind of employee every manager wants.

Fast, sharp, completely unflappable under pressure. When equipment went down, Elena had already called maintenance before I got the radio call. When a new associate couldn’t find her footing in the second week, Elena had quietly paired her with someone who could show her the ropes. When a quality exception surfaced mid-shift, Elena had flagged it, documented it, and started the corrective action before anyone else had fully registered there was a problem.

The team ran beautifully. I attributed it to good culture, consistent training, and the systems we’d built. What I hadn’t noticed—not clearly, not yet—was how much of it was Elena.

Then Elena got promoted. Rightly so, deservedly so, a move I’d advocated for. But over the following two weeks, something became apparent that I hadn’t seen coming.

Nobody else knew how to do half of what Elena had been doing.

Not because they were incompetent. They’d been working alongside Elena for months. They’d watched everything. They just hadn’t done it, because Elena was always there first, answering the question before anyone else had time to think, solving the problem before anyone else had to work through it, making the judgment call before the situation had a chance to develop anyone else’s judgment.

Elena hadn’t been building a team. Elena had been running the team. And I had let it happen, because the results looked so good.

This Isn’t a Performance Problem

The first thing to understand about this dynamic is that it’s nobody’s fault in the conventional sense.

Elena wasn’t undermining the team’s development on purpose. Elena was doing exactly what a high performer does: stepping up, taking responsibility, solving problems as fast as possible. Every individual decision was correct. The cumulative effect—a team that had learned to route everything through Elena rather than develop its own capacity—was a management problem, not an Elena problem.

That distinction matters enormously when it comes to what you do about it.

This isn’t a conversation about asking your best performer to do less. It isn’t about punishing excellence or engineering mediocrity. It’s about a specific management failure: allowing a star’s individual performance to become a substitute for your team’s collective development. Those are different things, and conflating them leads to the wrong solutions.

Individual excellence and team capability are not the same thing. A team with one exceptional performer and nine people who’ve learned to defer to her is less capable, less resilient, and less developable than a team where the excellence is more evenly distributed, even if it looks better in the daily numbers.

A star’s individual performance is not a substitute for your team’s collective capability. The first can mask the absence of the second for a long time.

Three Ways Stars Unintentionally Block Development

The mechanism is different in each case, which means the management response has to be different too.

The Answer Machine

Your most experienced associate is the first person everyone asks when something comes up. She knows the process cold. Her answers are always right. When a new associate has a question, she responds before the team lead has a chance to. When a problem surfaces, she names the solution in thirty seconds.

The natural result is the team stops thinking. Not lazily—rationally. If the answer is always available in thirty seconds from the same source, investing effort in developing your own judgment has no payoff. Over time, the team’s problem-solving capacity doesn’t just stall, it atrophies. The associates who would have developed strong operational judgment instead develop the habit of asking Elena, and Elena becomes the answer to every question whether she intends to be or not.

The Pacer

Your fastest sorter sets a pace nobody else can match. She isn’t trying to demoralize anyone; she’s just doing her job at the level she’s capable of. But the gap between her output and everyone else’s is visible, constant, and demoralizing in a way that doesn’t show up in your metrics. Associates who might otherwise push their own pace stop trying, because the comparison is always unfavorable. The implicit standard on the floor becomes “as fast as the fastest person,” which is a standard most people have concluded they can’t meet.

The paradox here is that your fastest associate’s performance may be holding your floor’s average down. As I explored in How to Raise the Floor, Not Just the Ceiling, your throughput is set by your average, not your best. If your best performer’s visible excellence is causing your middle to disengage from the effort to improve, you have a net negative—and it started with your star.

The Shield

Your best team lead handles problems so completely that the associates working under her never have to develop the capacity to handle those problems themselves. She doesn’t mean to shield them; she’s being thorough, responsible, doing her job well. But her competence creates a protected environment where no one else has to struggle through difficulty, and struggle is exactly what develops capability.

This is the version I encountered with Elena. It’s subtler than the first two because the star’s behavior looks like strong leadership. The team lead who handles everything seamlessly is easy to praise and hard to critique—until she’s promoted and the seam shows.

The Research Behind the Pattern

This isn’t just a floor-level observation. Research published in Personnel Psychology by Elizabeth Campbell at the University of Minnesota found that high performers positively influence their non-star teammates—up to a point. Above that point, the returns don’t just diminish, they reverse.

Campbell’s team found that the optimal team composition sits around 25% star performers and 75% non-stars. Spread out, stars lift the people around them; newer employees especially benefit from working alongside someone exceptional. But stack too many stars on one team, and the dynamic shifts. The positive influence flips negative, and collective performance drops below what you’d expect given the talent in the room.

The implication for floor-level management isn’t about team composition so much as about what concentration of excellence in one person does to everyone around them. When one performer is so far ahead of the rest that the gap feels uncrossable, the motivational lift disappears and something closer to learned helplessness can settle in. Your star stops being an example and starts being a ceiling.

What to Do About It

The goal isn’t to restrain your star. It’s to channel her differently.

The most important move is giving Elena a development mandate alongside her performance mandate. She could have been doing exactly what she was doing—but with a specific expectation attached: her job isn’t just to solve problems, it’s to develop the people around her by letting them work through problems first. That’s a genuinely different job description. Elena couldn’t have made that shift without being told it was the expectation, and that conversation is the manager’s job to initiate.

This connects directly to the Strategic Delegation framework—the most powerful development tool you have is assigning the right responsibility to the right person with the right support structure. For a star performer, that sometimes means assigning them the responsibility of not doing something, because their restraint creates the space others need to develop.

From there, protecting space for struggle is the practical application. When Elena is on shift, make it explicit that associates should attempt to work through problems before going to her—and that Elena should let them. Not letting problems compound unaddressed, but building a ten-minute window where the person with the question tries to reason through it before the answer appears. That ten-minute window is where development happens.

It also means separating Elena’s performance from the team’s performance in your own thinking. Look at what your floor produces without her present. That picture, the honest one, is the team you’ve actually built. If there’s a significant gap, the development work isn’t finished regardless of what the daily numbers say while she’s there.

The pacing problem has its own lever. When a star’s visible pace is demoralizing rather than inspiring, the answer isn’t to slow her down, it’s to build recognition around rate of improvement rather than absolute performance. An associate who moves from 85% to 95% productivity has done something worth recognizing, even if the person next to her is running at 110%. As I explored in Why Positive Feedback Comes First, recognition shapes what people believe they’re capable of. Calibrating it to growth rather than comparison is the management move that fixes the pacing problem without penalizing the star.

The Conversation You Need to Have

At some point, all of this requires a direct conversation with your star.

Not a critique—she hasn’t done anything wrong. A reframe of what excellence at her level actually looks like.

The conversation I wish I’d had with Elena earlier sounds something like this: “You’re doing everything right. The floor runs well because of what you’ve built. What I want to talk about is what the next level of impact looks like for you—and I think it’s in what you create in the people around you, not just what you do yourself. The question I want us to think about together is: what would this floor look like if everyone around you was developing at the rate you developed?”

That conversation does several things at once. It frames development as part of Elena’s job, not a limitation on it. It positions restraint and coaching as advanced skills rather than reduced contribution. And it ties Elena’s success to a metric (the capability of the people around her) that didn’t exist before.

Stars who are ready for the next level respond well to this framing. It gives their excellence somewhere to go. The ones who resist it are often telling you something important about whether they’re ready for more responsibility, or whether they’ve confused individual performance with leadership.

This is a thread I’ll pull further in the next article in this series, which looks at what psychological safety actually means in an operational environment and why the behavior of your highest-confidence performers is one of its biggest determinants.

Summary

Your best performer isn’t a problem. But the way you’re deploying them might be.

When a star’s excellence becomes the answer to every question, the pace everyone else is measured against, or the shield that keeps the rest of the team from having to work through difficulty—individual performance has become a substitute for collective capability. That substitution looks fine in the daily numbers and shows up clearly the moment the star is gone.

The highest expression of individual excellence in an operational leader isn’t what she produces. It’s what she makes possible in everyone around her.

The management move isn’t to restrain excellence. It’s to channel it: give your star a development mandate alongside her performance mandate, protect space for the team to struggle productively, and have the conversation that reframes her impact in terms of what she creates in others, not just what she produces herself.

From Theory to Action

1. Run the Elena test. Think about your strongest performer right now. If she were promoted or transferred tomorrow, what would the team be able to handle? What would stall? Be specific. The gap between those two lists is where your development work needs to go.

2. Watch for the Answer Machine pattern this week. Pay attention to who fields questions on your floor and how quickly. When your star answers before anyone else has had five seconds to think, that’s a data point. It’s not a problem yet, but it will be if the pattern holds for months. What would it look like to build a five-minute “try it first” norm before the answer becomes available?

3. Check your recognition for comparison traps. Pull your last two weeks of recognition moments. Were any of them framed in a way that implicitly benchmarked others against your star? “Great job! That’s the standard I want everyone at” sounds positive, but it sets a ceiling in the same breath. Recognition that focuses on individual improvement doesn’t carry that cost.

4. Have the development conversation with your star. Not as a critique , but as a reframe. What would it look like if her job included developing the capability of the people around her, not just performing at a high individual level? What would she need from you to make that shift? Listen to the answer carefully. It tells you a lot about where she is in her own development.

5. Build in structured struggle. Pick one category of problem that your star currently handles by default and explicitly hand it to someone else for the next month. Your star is available as a resource if things go sideways, but the first attempt belongs to someone else.

6. Look at your floor’s performance distribution. The research from the University of Minnesota points to 25% stars as the rough optimal. You probably can’t engineer that number precisely, but the direction matters: are your stars concentrated on one shift or spread across the operation? Concentrated star power tends to create a dependent floor. Distributed star power tends to lift the average.

7. Revisit this conversation quarterly. The “let me develop the people around me” mandate isn’t a one-time reframe—it’s a new part of your star’s job description that needs to be tracked and recognised. In your one-on-ones, ask what she’s specifically done to develop someone else’s capability this month. The question signals that it counts. Signals are how culture gets built.

This post is part of the Building High-Performance Teams arc, following How to Raise the Floor, Not Just the Ceiling and The Culture You’re Building Without Knowing It.

Next: Psychological Safety on the Production Floor—what it actually means in a warehouse environment, and why your highest-confidence performers are one of its biggest determinants.

Megan was the best sorter I’d ever had.

Consistent, fast, almost never wrong. On nights when the volume came in heavy and the floor was stretched, Megan could carry the outbound sort in a way that made the whole thing look more manageable than it was. New managers who shadowed me would watch her work and ask who she was. Senior managers would notice her numbers in the daily report and ask what we were doing right over there.

What we were doing right was Megan.

Then Megan went on maternity leave for six weeks.

The floor didn’t collapse. We managed. But I watched something instructive happen in those six weeks: the shift’s true capability revealed itself. Without Megan absorbing the hard volume and compensating for the slower pacing around her, every gap in the team’s middle became visible. Decisions that Megan had been quietly mopping up now stalled. Quality holds that Megan’s pace had been masking started showing up in the data.

The team hadn’t gotten worse. They’d always been that team. I just hadn’t been seeing it clearly, because I’d been watching Megan.

That six-week absence gave me a more honest picture of what I’d actually built—and what I hadn’t.

Why We Invest in Stars Without Meaning To

It’s not a calculated decision. It’s gravity.

Your top performers produce moments worth noticing. When something goes well, they’re usually involved. When you need to fill a capability gap, they’re the first names that come to mind. When you have a stretch assignment to give, they’re the obvious choice, partly because they’ll succeed and partly because you trust them with something that matters.

This feels like good management. It is, in the immediate sense; putting your best people on your hardest problems produces the best immediate outcomes. But over time, it also means your investment in people is concentrated in the performers who are already performing well, which has a specific effect that most managers don’t connect to this cause.

Your best performers are already close to their ceiling. The upside of investing in someone who’s already at 90% of their potential is real but limited. The upside of investing in someone at 65% is considerably larger. Not because that person is more talented, but because there’s more room to grow.

Meanwhile, your middle performers—solid, reliable, not failing visibly—drift. Not because they’re not capable of developing. Because nobody is specifically investing in them.

Your Floor Runs at Your Average, Not Your Best

If you’ve spent any time in operations, you’ve probably encountered Eliyahu Goldratt’s Theory of Constraints. The idea at the heart of his book The Goal is that the throughput of any system is determined by its bottleneck, not by its fastest component.

He illustrated it with an analogy that’s stuck with generations of operations managers: a hiking troop moving through the woods. The speed of the troop isn’t determined by the fastest hiker at the front. It’s determined by the slowest hiker in the middle. The fast hikers reach camp early, but the troop doesn’t arrive until the last person does. To speed up the troop, you don’t make the fast hikers faster. You close the gap between the fastest and the slowest.

The application to a warehouse or production floor is direct. Your best performer’s rate isn’t the rate your floor delivers. Your average performer’s rate—your floor, not your ceiling—is what determines your actual throughput. When your middle is stuck, the whole operation is stuck, regardless of how fast your Megan is sorting.

This reframes the question that managers usually ask. Most managers ask: how do I get more out of my best people? The question with more leverage is: how do I raise what my average people can do?

Your floor runs at its average, not its best. Raising what average looks like on your team is the highest-leverage development work most managers aren’t doing.

The People Who Never Ask for Development

The challenge with investing in your middle performers is that they don’t ask for it.

Your stars create pull. They achieve things, they get noticed, they get offered opportunities partly because they’ve demonstrated they can handle them. Your struggling performers create urgency. They need conversations, intervention, attention. Both groups are visible to you in active ways.

Your middle performers are visible mostly through their absence from your attention. They show up. They hit the numbers. They don’t cause problems. And because they don’t cause problems, they don’t register on the radar in the same way.

What’s actually happening in that group, underneath the acceptable performance, is often more interesting than the surface suggests. In my experience, the middle of most teams contains people who are capable of significantly more, but haven’t been given a clear signal that more is possible or expected. They’ve calibrated to what gets rewarded here, and what gets rewarded here is hitting the standard. So they hit the standard.

The associate who’s consistently at 100% productivity but never initiates anything isn’t necessarily someone without initiative. She might be someone who tried once, got no response, and filed the experience away. The team lead who handles his zone competently but never expands his thinking beyond it might not have a limited ceiling; he might have never been asked what’s beyond it.

I wrote in The Culture You’re Building Without Knowing It about how recognition patterns teach your team what gets noticed here. The same principle operates in development: who you invest in teaches your team who development is for. When development consistently goes to the same high-profile performers, your middle performers learn (accurately) that development on this floor isn’t something they need to expect.

What Developing the Middle Actually Looks Like

This isn’t the same conversation you’d have with a high performer. Your stars often need challenge and visibility; they’re already engaged and looking for the next thing. Your middle performers often need something different: a signal that you’ve noticed them specifically, a question about where they want to go, and a concrete next thing that’s slightly beyond what they currently do.

The signal matters more than most managers realize. The associate who has been competently doing the same job for eighteen months without a developmental conversation has learned a specific thing: this is the ceiling for people like me here. The first time you sit down with her and ask where she wants to develop—not as a performance conversation, not tied to a problem, just as a genuine question about what she wants—you’re interrupting that belief. That interruption is often what unlocks the engagement that was already there but had no channel.

From there, the mechanics are similar to what I explored in From Average to Excellent: a stretch assignment that’s slightly beyond the current comfort zone, specific feedback on what you’re observing, and consistency over time. The piece that’s different with middle performers is the patience required. Where a high performer might take on a stretch assignment and run with it immediately, a middle performer often needs more time to trust that the invitation is real, that raising her hand won’t just create more scrutiny or more work without any corresponding recognition or development.

Two practical things that tend to work well with this group:

Invisible contribution, made visible. Most middle performers are doing things quietly that nobody has named. The team lead who catches quality issues before they escalate. The associate who shows up early and orients the new hire without being asked. These behaviors matter, and the act of naming them specifically is itself a development conversation. It tells the person what good looks like from your vantage point, which is information they often genuinely don’t have.

Small scope, real responsibility. A stretch assignment doesn’t need to be large. Asking a solid team lead to own a specific process improvement for thirty days—something bounded, something with a clear success metric, something she’ll present the outcome of—gives her a development experience without overextending her. The key is that the responsibility is genuine, not cosmetic. People can tell when they’ve been given a task versus given an opportunity.

What Changes When the Average Goes Up

The most obvious thing: throughput improves. Not because your stars got better, but because the work that was previously sitting on their shoulders—compensating for the slower pace around them, absorbing the quality gaps, carrying the decisions that stalled—gets more evenly distributed. When your middle performers are more capable, your best performers stop being load-bearing walls.

Your delegation options expand too. If you’ve read the Strategic Delegation series, you’ll know that one of the real constraints on effective delegation is having people ready to receive what you’re trying to hand off. A team where development has concentrated at the top has a very thin bench beneath it. A team where you’ve deliberately invested across the middle has multiple people ready for the next responsibility. That breadth is what makes genuine delegation, not just task assignment, possible.

And then there’s the cultural signal, which takes longest to show up but matters most. When middle performers start receiving development attention, two things happen. The people receiving it become more engaged; they’re being seen, invested in, asked about their future. And the people around them observe that development on this floor isn’t reserved for the same two names. That signal, over time, changes who sees themselves as having a future here.

I watched this play out during my time as a pack manager in Reno. The team I inherited was quietly segmented: a handful of visible high performers and a larger group who kept their heads down and hit their numbers. Once I got intentional about where my development conversations were going, things started to shift. Slowly, nothing dramatic in the first few months. But by the time I’d been there nine months, the team had a depth it hadn’t had before. More people could run more things. The stars were still stars, but they were stars on a team, not islands surrounded by average.

Summary

Your floor runs at its average. The question to ask isn’t how to get more from your best performers. They’re already delivering. The question is what’s holding your average performers at the level they’re at, and what it would take to move it.

Most of the time, the answer isn’t skill. It’s investment. The signal that someone specific is expected to grow, delivered consistently, through genuine development conversations and real stretch assignments, with patience for the time it takes to trust that the invitation is real.

That’s the work. It’s less visible than developing a star. The returns take longer to appear. But the floor you’re building, the one where your operation runs at a genuinely higher average, is a more durable thing than the floor where everything depends on who showed up today.

You can build a team with a few exceptional performers and a mediocre average, or you can build a team where exceptional is what the average looks like. Only one of those travels without you.

From Theory to Action

1. Do the Megan exercise. Think about the one or two people on your floor who are quietly compensating for gaps in everyone around them. Now ask: what does the shift look like in their absence? That picture is a more honest read of your team’s true capability than the daily numbers while they’re present. Start there.

2. Map where your development attention actually went last quarter. Not where you intended it to go. Where it actually went. Which team leads got stretch assignments? Who had genuine developmental conversations in their one-on-ones? If the list skews toward the top of your performance distribution, that’s not a failure of intention. It’s gravity. The question is whether you’re going to counteract it deliberately.

3. Pick two middle performers and have a non-performance conversation with each of them this month. Not a feedback session. Not a review. A genuine question: “I’ve been thinking about where I’m investing development time, and I want to ask—where do you want to go? What do you want to be able to do that you can’t yet?” Then listen. What you hear will probably surprise you.

4. Name one invisible contribution, specifically and publicly. This week, catch someone in your middle doing something quietly good, something that prevents a problem rather than solving one visibly, and name it out loud in front of the team. Not generically (”good work today”) but specifically (”I noticed you flagged that equipment noise before the shift started, That’s exactly the kind of thing that prevents us from losing two hours mid-shift”). One specific recognition tells that person more about what you value than a year of vague positive feedback.

5. Design one genuine stretch assignment for a middle performer. Not a task. An opportunity. Something with a real outcome, a defined scope, and a clear moment where she’ll present what she learned. Use the Team Capability Mapping process to identify the right person and the right stretch. Build in a debrief using the framework from The Debrief That Builds Leaders when it’s done.

6. Watch what happens to your stars when your average goes up. As your middle improves, pay attention to your best performers. When they stop quietly compensating for the gaps around them, something changes. Some of them relax and start performing better. Some of them, unexpectedly, start stretching into new responsibilities now that the old ones don’t need them as much. That shift—when your stars start growing because your floor finally gave them room to—is the return on the investment you made in your middle.

This post builds on The Culture You’re Building Without Knowing It and connects directly to last year’s article From Average to Excellent and the Strategic Delegation series.

Next in this arc: When Your Best Player Makes Your Team Worse — the counterintuitive problem of high performers who unintentionally prevent the people around them from developing.

About a year into managing my own area at Amazon, I walked back from a shift managers’ meeting and noticed something I hadn’t seen before.

Two of my team leads were standing near the sort station, and one of them was coaching an associate through a process question. Not directing—actually coaching. Asking what the associate thought the issue was, letting him work through it, only stepping in to redirect when he stalled. It was, almost exactly, the way I’d been trying to run my own debrief conversations with her for months.

I stood there for a moment longer than I needed to. Because what I was watching wasn’t something I had assigned, or rolled out in a team meeting, or put in a development plan. She had just started doing it—and now she was doing it one level down from me, with her own people.

That was the first time I understood what culture actually is. Not a values statement on a wall. Not a set of norms you announce in an onboarding. It’s the accumulation of signals you’ve been sending—through what you’ve rewarded, what you’ve tolerated, and what you’ve modeled—until those signals become the way people behave when you’re not in the room.

The encouraging version of that realization is what I saw that day: good habits replicating downward, development becoming the way the floor operated rather than a thing I was personally trying to do.

But the same mechanism works in the other direction, too. And most managers encounter that version first.

The Culture That Was Already There

Every team you take over comes with a culture already running. It’s been shaped by everyone who managed that team before you: their habits, their tolerances, their shortcuts and their standards. Some of it is visible, such as the way people talk to each other, the pace they work at, the amount of noise around near-misses. Most of it isn’t. It lives in unspoken agreements about what gets addressed and what gets quietly ignored, about how problems get surfaced and by whom, about whether the people on this floor believe anyone is genuinely paying attention.

When you arrive, that culture doesn’t pause to let you get oriented. It evaluates you from the first shift. And what it’s watching—what your team is watching—has very little to do with what you say about your management philosophy or your expectations or the kind of leader you want to be.

They’re watching what you do when someone cuts a corner and you notice. Whether you follow through when you say you’ll look into something. Which problems get your energy and which ones quietly disappear. How you talk about the people above you when they make decisions you disagree with. Whether the standards you enforce on Tuesday still apply on Friday afternoon when the shift production is behind.

Culture is built from that material. The speeches don’t touch it.

Nobody Announced It

The thing you need to understand about culture is that it’s almost never deliberately designed. It accumulates.

The manager who lets the fastest associate skip safety documentation because the shift is behind hasn’t made a cultural decision in any conscious sense. But the team saw it. And next week, when someone else is behind, they have data about what actually matters when things get tight. That data compounds, and two months later the manager is confused about why safety compliance feels like a constant battle, not understanding that they resolved the question themselves weeks ago.

This is true in both directions. The manager who consistently takes ten minutes after a difficult situation to ask her team leads what they were thinking—not criticizing, just curious—isn’t usually thinking “I am building a culture of reflection.” She’s just doing what she does. But her team leads start doing the same thing. And eventually you end up with what I saw at the sort station that afternoon: a coaching behavior that nobody programmed, replicating naturally because it had become the floor’s normal.

Culture isn’t what you intend. It’s what you repeatedly do and, more importantly, what you repeatedly allow.

What You Reward Teaches More Than What You Say

Every time you give recognition, you’re teaching your team what matters. The question is whether you’re teaching them what you think you’re teaching.

Recognition that lands on the same two or three people—the ones who are loud, or fast, or who happen to be standing near you when something goes well—teaches a very specific lesson: visibility and proximity to the manager matter. Effort that happens quietly, in areas you don’t walk past as often, doesn’t register the same way. Over time, people adjust. Not cynically, just practically. They figure out how recognition works here and they act accordingly.

The same is true of assignments. Which team leads get the high-visibility problem to own? Who gets pulled into the planning conversation for the new process rollout? Who gets the stretch task when capacity allows? Every one of those choices is a signal about what kind of performance and what kind of person you value. Your team is reading those signals constantly, in more detail than you probably realize.

There’s an easy way to audit this honestly: look at who got your visible recognition and your development assignments over the last two months, and ask whether that list reflects your stated values. Or was it just whoever happened to be in front of you when something good happened? The gap between those two things is a culture gap.

What You Tolerate Is Also a Policy

The things you don’t address are just as powerful as the things you do.

I wrote in Creating Accountability Without Constant Oversight about how vague expectations become invisible ones; how “handle problems that come up” means different things to different people depending on what they’ve seen happen when they did or didn’t handle something. The same principle applies here, but at the level of culture rather than operations.

If a team lead is consistently slow to respond to quality issues and you’ve had a conversation about it but nothing has changed and you haven’t gone further, that’s now a data point about how seriously quality standards are held on your team. The team lead whose performance is slipping knows it. So does everyone who works alongside her.

If the loudest, most confident voice in every problem-solving conversation is always right regardless of whether the reasoning is sound, and you haven’t noticed or addressed it, you’re building a culture where volume matters more than analysis.

If the standard you enforce when things are calm gets quietly suspended when the shift is behind, the standard that’s actually in effect isn’t the one you wrote down. It’s the one people can observe being applied consistently.

None of these gaps require bad intentions. They mostly require a manager who’s too busy to address everything, which describes every manager. But the things that go unaddressed don’t disappear from the culture. They become its baseline.

What You Model Is the Loudest Signal of All

Your team watches how you operate, and what they see becomes a template.

Not because they’re trying to emulate you (though some of them are, especially your team leads). Because watching the person who runs the floor is the most reliable way to figure out how this place actually works. What does the manager do when something goes wrong? Does she stay calm and ask questions, or does she get loud and fix things herself? Does she follow through when she says she’s going to do something? Does she know who’s been struggling and act on it, or does she wait for problems to come to her?

I’ve seen this play out in very specific ways. In The Debrief That Builds Leaders, I wrote about the moment when a team lead starts asking her associates the same questions you’ve been asking her, the debrief habit replicating downward without anyone telling it to. That’s culture being built through modeling. But the same thing happens with cutting corners, with blaming other departments for problems, with responding to pressure by dropping standards. Whatever you do consistently is what your floor learns to do.

This is the part that many managers find uncomfortable: you’re modeling when you don’t intend to. How you handle the moment when your own manager overrules you in front of your team. How you talk about a struggling associate when you’re venting to a colleague and someone is within earshot. How present you actually are during a pre-shift versus going through the motions. Those moments teach at least as much as the intentional ones.

As I explored in Ethics in Leadership and Creating a Culture of Openness and Honesty, your team doesn’t just watch what you do with big decisions. They watch the small ones. That’s where character is actually visible—and character, compounded across hundreds of small decisions, is what culture is built from.

Reading the Culture You’ve Actually Built

The most useful thing you can do with the ideas in this post isn’t to start designing your culture. It’s to start reading the one you already have.

A few places to look:

How do problems surface? Do your team leads bring issues to you early, when they’re still manageable? Or do things tend to appear fully formed and already serious? Teams where problems surface late are usually teams where surfacing problems early has carried some cost in the past—frustration, dismissal, extra scrutiny. That’s a cultural signal.

What do people do when no one is obviously watching? The standard that holds during the middle of the shift when you’re occupied with something else is closer to the real standard than the one that holds when you’re standing right there. Walk past something you didn’t know you’d pass. See what you find.

What are the unspoken rules about bad news? Does your team know you want to hear about problems fast? More importantly—do they believe it? The stated preference for early escalation and the actual experience of having escalated early don’t always match, and your team knows which one is real.

Who gets the credit and who gets the blame? Watch what happens when something goes well versus when something goes sideways. Where does the credit flow? Where does the accountability land? Those patterns, applied consistently over months, define the culture your team is working inside.

You can’t see all of this clearly from inside it—which is one of the reasons I’ve written at length about self-awareness as a leader and why the one-on-one conversation is such a valuable diagnostic tool. Your team leads, asked directly and with genuine curiosity about what they observe, will tell you things about your culture that your own vantage point can’t show you.

Summary

The culture on your floor isn’t something that happens to you. It’s the sum of what you’ve been doing: the recognition you’ve given and withheld, the gaps you’ve addressed and the ones you’ve let slide, the behavior you’ve modeled under pressure and under calm. It’s been building since your first shift, whether or not you were thinking about it.

The good news is that the same mechanism that builds culture accidentally can build it intentionally. Not through announcements or value statements, but through the same small daily decisions made more consciously, with a clearer picture of what you’re actually communicating.

Start there. Read the culture you have. Then decide what you want to build.

From Theory to Action

1. Do the recognition audit. Pull up the last two months and list everyone you’ve visibly recognized—in team meetings, on the floor, in a conversation others could hear. Does that list reflect your stated priorities, or just the people who happened to be visible? The people who didn’t make the list aren’t invisible. They noticed too.

2. Name one thing you’ve been tolerating. Not to beat yourself up about it; just to be honest. One pattern of behavior or performance on your floor that you’ve addressed less than the situation probably warranted. Decide this week whether you’re going to address it properly or whether you’ve made a conscious choice to let it go for now. Either is a real answer. Drifting is the one that shapes culture without your input.

3. Ask your team leads what the unwritten rules are. Not in a formal culture conversation. Just slip it into a one-on-one: “What do you think people here believe about how problems get handled? What’s the actual expectation versus the stated one?” Listen without correcting. What they think the rules are is the culture, regardless of what you intended.

4. Watch how your team behaves when you’re distracted. Pick a shift this week and spend thirty minutes occupied with something real: paperwork, a call, a conversation at the dock. Then walk the floor without making a show of it. What changed while your direct attention was elsewhere? That delta is a culture reading.

5. Trace one behavior back to its origin. Choose something your team does consistently, whether good or bad. A habit, a norm, a default response to a certain kind of situation. Walk it back: where did it come from? If you look honestly, you can usually find the manager, the incident, or the repeated pattern that planted it. That exercise tells you more about how culture forms on your floor than most frameworks will.

6. Choose one behavior you want to build and commit to modeling it for thirty days. Not announcing it. Not putting it in a memo. Just doing it consistently enough that your team leads start to notice, and eventually start doing it themselves. The debrief habit is a good one if you’re working through this series. But it could be anything: the way you handle a near-miss, the questions you ask when something goes wrong, how you recognize effort that happened out of your line of sight. Choose deliberately, model consistently, and watch what replicates.

This post is the fourth in the current series, building on When to Step In and When to Step Back, The Debrief That Builds Leaders, and Creating Accountability Without Constant Oversight.

Next: How to Raise the Floor, Not Just the Ceiling—why developing your middle performers matters more than investing in your best ones.

You get called into an unplanned meeting. You're there for forty-five minutes. When you come back, what has happened on the floor?

That question has two very different answers, and which one you get depends almost entirely on what you built before you walked out the door.

I know both versions firsthand. In my early years at Amazon, I came back from an unexpected absence one afternoon to find my packing team lead standing near the conveyor with a quality problem, waiting. She'd been standing there for nearly twenty minutes. Not because she didn't know what to do, she probably did. But nobody had ever told her whether that decision was hers to make, so she did what made sense to her: she waited for me. Behind her, a small backlog had formed. A decision that should have taken two minutes had been on hold for twenty because I was the only one who knew where the authority line was.

The second version came after I'd done the work to build something different. Peak season, a few years later—I got pulled into a meeting about a major customer escalation and was gone for close to an hour. When I walked back onto the floor, my team lead met me near the entrance and gave me a status update: equipment had gone down on the loading dock and was back up, a quality issue had been flagged and corrected, and he'd pulled two people from pack line six to help cover a staffing gap on the inbound side. Three things had happened. Zero radio calls.

That wasn't luck. And it wasn't that my team was suddenly more capable than the one from years earlier. The difference was in what I'd built around them.

In When to Step In and When to Step Back, I wrote about the judgment call on the floor—the moment you decide not to intervene when your instinct says to. In The Debrief That Builds Leaders, I covered what to do with those moments afterward. But both of those skills depend on something more foundational: a set of systems that function when you're not there to enforce them. Without that, stepping back is just absence. With it, stepping back becomes development.

This week’s post is about building those systems.

The Test You're Already Taking

Here's something worth sitting with: your team is already being tested on what they can handle without you. Every time you're in a meeting, doing a walk in a different area, at lunch, or dealing with something else, your floor is making decisions. The question isn't whether those decisions are being made. It's whether your team has what they need to make good ones.

Most managers find out the hard way that they haven't set this up right. The pile-ups, the escalations that could have been handled two hours earlier, the team lead who made a reasonable call but had no idea whether it was within her authority—these aren't signs of a weak team. They're signs of a team that was never set up to operate independently.

Accountability without oversight isn't magic. It's built from three things that have to work together: clear expectations, visible performance, and defined ownership. Each one sounds obvious. Each one is routinely done badly.

Presence-Based vs. Systems-Based Accountability

Presence-based accountability works like this: people perform because you're watching, because they might get asked, because the manager is somewhere nearby. It produces compliance in the short term and fragility in the long term. The moment you're unavailable, it starts to degrade.

Systems-based accountability works differently. People know what's expected. They can see how they're performing against those expectations without asking anyone. And there's always a named person responsible — whether you're there or not.

The shift from one to the other is less about management philosophy and more about three concrete things you either build or don't. Let's take them in order.

Vague Instructions Need You. Specific Ones Don't.

The most common accountability failure I see isn't that managers don't set expectations—it's that the expectations they set aren't specific enough to mean anything without interpretation.

"Keep quality up." "Make sure the line moves." "Handle problems that come up." These aren't expectations. They're intentions. And they need your presence to translate into behavior, because the moment a gray-area situation arises, your team lead has no way to know whether it falls inside "keep quality up" or outside it. So she calls you. Or she waits.

Expectations that work without you need to answer three questions before you leave the floor:

What does good look like, specifically? Not "hit your targets." What number, by what time, measured how? Not "address quality issues." Which issues get held, which get flagged, which get released with documentation? The more specific you are, the less your team needs to find you to make a call.

Where does her authority end? This is the piece most managers skip. Your team lead needs to know not just what to do in the standard case, but what's hers to decide and what isn't. What can she handle on her own? What needs a call to you? What gets escalated even if you're unreachable? These boundaries aren't about distrust, they're about confidence. A team lead who knows exactly where her authority ends can act within it without hesitation. One who doesn't will always hedge.

What's the default when something doesn't fit the standard? Edge cases are where things break down. Build in a fallback: when in doubt, here's what you do, here's who you contact, here's what gets documented. A clear default for ambiguous situations is worth more than a detailed procedure for normal ones.

The best place to work through all three is your one-on-one meetings. Not as a policy review, but as a conversation: "Walk me through what you'd do if X happened while I was in a meeting." The gaps in her answer are your development targets.

When the Floor Can See Itself

The second way accountability breaks down is invisible performance—a floor where only the manager knows how things are trending, which means all the information flows in one direction: up to you.

Early in my time as an Area Manager, I watched a senior ops manager do something that stuck with me. At the start of every shift, he took a whiteboard and wrote three numbers: the target, where the floor currently sat, and the gap. He updated it every hour. He didn't need to chase people down for status. He didn't need to be standing at every station. The board told the story, and his team could see it as clearly as he could.

That visibility changed something. When the number slipped, everyone saw it at the same time. The conversation about why became a team conversation, not a manager-asking-associate conversation. Problems surfaced faster because people weren't waiting to be asked; they were already looking at the same information and talking about it themselves.

Toyota understood this principle at a fundamental level. In the 1950s, they introduced the Andon cord, a physical cord running the length of the assembly line that any worker could pull the moment they spotted a defect or a problem. Not a supervisor. The worker closest to the work. Accountability was wired directly into the line rather than residing with whoever happened to be walking past.

The results were counterintuitive. Stopping the line more often led to better overall output, not worse, because problems got caught and corrected at their source rather than compounding downstream. Toyota's quality edge didn't come from more attentive supervisors. It came from designing a production system where the people doing the work could see problems in real time and act on them immediately.

That's the same problem you're solving, scaled down to your floor. You can't be watching every zone every minute. So the question is: can the people working those zones see what's happening without waiting for you to notice first? A whiteboard updated hourly, a simple metric visible at the relevant stations, a color-coded status board anyone can read in thirty seconds, these all serve the same function. Not surveillance. Shared awareness. When everyone sees the same picture, accountability stops requiring a manager in the room to function.

Named, Not Assumed

Clear expectations and visible performance are two-thirds of the equation. The third piece is ownership, and it's the one that most often gets left to chance.

Even with specific expectations and fully visible performance, things fall apart when nobody is clearly responsible. Shared responsibility without a named person becomes no responsibility. "Someone should deal with that" is the sentence that explains most of the problems waiting for you when you walk back in from a meeting.

What makes it stick is naming someone: for every significant responsibility on your floor, there is always a specific person who owns it during a given shift. Not "the team." Not "whoever's around." A person, named before the shift starts, who knows they're the point of contact if something happens in that area.

This is different from job assignments. It's accountability assignments. Your team lead at pack isn't just working pack — she's accountable for pack. If there's a quality issue, a staffing gap, or an equipment problem in that zone, it's her responsibility to address it or escalate it. She doesn't wait for you. She acts, and then she brings you the outcome.

Building this into your pre-shift routine is the most practical way to make it stick. Before the shift, five minutes: who owns what today, what are the expectations for each zone, what's the escalation path if something falls outside normal bounds. It sounds like overhead. It pays for itself the first time you get pulled out of the building unexpectedly and the floor handles it before you get back.

The Peer Accountability Problem

One thing worth addressing directly: as you build these systems, you'll notice something. When performance is visible and ownership is clear, team members start noticing when their peers aren't pulling their weight. This can go two ways.

Done well, it becomes the kind of peer accountability that makes teams genuinely high-performing—people holding each other to shared standards because they understand that one person's lag creates problems for everyone else. Done badly, it becomes a watching culture where people tattle on each other and trust erodes.

The difference is almost entirely in how you respond when someone brings you information about a peer. If you treat those observations as complaint-filing and act immediately on what you hear, you've incentivized tattling. If you treat them as data points to investigate and validate on your own, you build a culture where people feel responsible for outcomes without becoming each other's monitors.

The framing that works best, in my experience, is collective ownership: we're all accountable for this shift, not just for our individual zones. When people see themselves as co-owners of a shared outcome rather than guardians of their own performance, peer accountability starts to feel supportive rather than punitive. That shift in framing is one of the things I'll dig into in the next article in this series — because it's one of the main ways team culture actually forms, quietly and without anyone announcing it.

Summary

Accountability without constant oversight isn't about trust, or letting go, or any of the other things leadership books tend to make it about. It's built from three specific things: expectations specific enough that your team lead doesn't need you to interpret them, performance visible enough that nobody has to ask how the shift is going, and ownership clear enough that someone is always responsible whether you're there or not.

When those three things are in place, your absence stops being a vulnerability. It becomes something closer to a routine—a forty-five-minute meeting, a trip to a different building, a day of training—that your floor handles the way it handles everything else: without waiting for you.

From Theory to Action

1. Run the absence audit. Think about the last time you were unexpectedly pulled away from your floor for thirty minutes or more. What piled up? What got handled? What got decided wrong? That picture tells you exactly where your systems are weakest. Start there, not with the parts that are already working.

2. Take your three most important expectations and make them specific enough to survive without you. Write them down. If you can't define what "good" looks like in two sentences—the number, the threshold, the line—you don't have an expectation yet. You have a hope.

3. Have the authority conversation before something forces it. This week, sit down with each team lead and go through it out loud: what's hers to decide, what needs a flag to you, what gets escalated even if you're unreachable. Write it down somewhere both of you can see it. The conversation itself is half the value—it surfaces the gray areas you didn't know existed until you said them out loud.

4. Pick one thing to make visible on your floor and put it up this week. Not a dashboard. One number—your most important shift metric—somewhere the whole team can see it without asking. A whiteboard updated hourly is enough to start. Build the habit before you build the system.

5. Before your next shift, name the person responsible for each zone. "Michael owns sort today, which means if something goes sideways over there, he's the first call, not me." Say it in the pre-shift, so everyone hears it including him. That distinction, stated clearly, changes how people carry themselves through a shift.

6. Test your systems on purpose. Once things are taking shape, deliberately create a thirty-minute window where you're genuinely unavailable: a floor walk in a different part of the building, a meeting you actually attend instead of monitoring your radio from. Then debrief with your team leads when you're back. Use the same questions from last week's debrief framework: what did you see, what options were you weighing, what would you do differently? What they needed you for that shift tells you exactly what to work on next.

7. Watch for the moment your team stops routing problems through you. Peer-to-peer problem solving, two team leads working something out between themselves before it ever reaches your radio, is the clearest sign that your systems are doing what they're supposed to. When you see it, say something. Name it. People build more of what they know you've noticed.

This is the third post in the current series, building on When to Step In and When to Step Back and The Debrief That Builds Leaders.

Next week: The Culture You're Building Without Knowing It — how the daily behaviors in this series add up to something larger than any individual practice.

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.

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