A couple of weeks ago, I was offered a new job. It came with a substantial raise, about 30% more than I make now.

It took me nearly a week to decide if I was going to take it or not. I kept flipping back and forth repeatedly. I had fully decided to take it, then just a couple of hours later, just as certain I was turning it down. Three hours after that, I was back to yes. It’s one of the harder decisions I’ve made in a long time.

If the only thing on the table had been the money, this wouldn’t have taken a week. More money is always worth taking seriously, and this job came with an amount that was supposed to make the decision easy. But a job offer is never just one question. There are always at least 4 things you need to consider, the compensation being just one of them. You also need to think about whether you want to spend your days doing the work itself, what it will cost you outside of work (your time, your family, and all the other parts of life that have nothing to do with the job), and the team you’d be doing it alongside. Most people, when an offer like this lands, only really weigh one or two of the four aspects.

In the end, I turned it down. Not because the money wasn’t good. It was, and I wanted it. But weighed against the other things, at this point in my life, it wasn’t worth what it would have cost. Things might look different in a few months. If a similar offer comes up then, I might take it. But right now the answer was no.

Part of what made this so hard is that it wasn’t a job that was easy to turn down. It’s work I’m genuinely interested in. Turning down a job you wouldn’t have liked anyway, even a well-paid one, is a much easier decision. In those situations the downside is obvious and the paycheck doesn’t magically make you like the work. Turning down a job you would have liked, that also pays well, is much harder.

The Trap I See Constantly

I’ve met a lot of people over the years who got into management for the simple reason that it came with a raise. Being a manager was the next rung up if you wanted to make more money. I completely understand when people enter management for this reason. Money is necessary to sustain life and it’s becoming more expensive to be alive every year. Taking a bigger number seriously is the responsible thing to do, not the greedy thing.

But taking it seriously doesn’t always mean take it. These are totally different things. But a lot of people see the number and let it do all the deciding. They don’t always stop to ask what the job actually is: the type of work, what it will ask of your time and attention, how it will affect your family if you take it, etc..

It’s Okay Not to Want This

And that asking these questions brings me to the important part. Not everyone is interested in leadership. Not everyone enjoys managing people, carrying a team’s problems home with them, and having to answer for things that went wrong on someone else’s shift. Some people are just better suited to going deep on a craft than wide across a team. That isn’t a weakness, and it isn’t a failure to seize an opportunity. It’s just what some people want out of their working life. That’s perfectly fine and it deserves as much respect as wanting the opposite.

This is one of the questions a job offer is really asking: does the work itself, the actual nature of the role, fit who you are? A role can be a great fit for leadership in general but be a bad fit for you specifically. Taking a job that goes against the grain of your personality or your interests, purely because the compensation is good, rarely turns out to be worth what it costs the other areas of your life.

What It Costs You Outside of Work

Another question is the one I weighed hardest this time: what the job would require in the rest of my life. This particular role would have come with some difficulties for my family at this point in our lives.

This is the axis people underrate most in my opinion and I think that’s because it’s the hardest one to quantify. A raise is easy to calculate. It’s right there on the offer. But what a job costs your evenings, your weekends, your presence at kid’s events, your spouse, these things are a lot harder to measure. That makes it easy to underestimate the impact a job will have in those areas, or to assume everything will sort itself out once the bigger paycheck starts coming in. Sometimes it does, but usually not, and you don’t find out which until you’re already in it.

There are seasons in life where the money has to win anyway and if that’s the case, it’s a legitimate call. Plenty of people take a harder job for a few years specifically because the family needs the money more than it needs the extra time together in the evening. So I’m not saying that the cost to your personal life should always win. All I’m saying is that this cost has to actually get weighed, on purpose, instead of getting waved off because the number upstream of it looked big enough to settle everything by itself.

The Team You’d Be Joining

The final question gets missed even more often than the first two, especially by younger and newer leaders. Before you take a job, you need to evaluate who you’d actually be working with, and what kind of place you’d be walking into every day.

My brother had been working at a company for three or four years when a competitor offered him more money, and he took it. About six months later we were talking and he told me straight out that it had been a mistake.

The paycheck was bigger, but everything else was worse. The new company ran on a much more dog-eat-dog culture. Everyone was looking out for themselves, there was more office politics, and less willingness to help a coworker who was underwater. At his old company, people genuinely had each other’s backs and they cared about doing right by the customer, not just hitting their own numbers. The new place was colder and more calculating. Six months in, he missed his old team enough that the raise wasn’t coming close to making up for it.

The difference in culture was making him more miserable than the larger paycheck was able to offset.

Company culture isn’t something that can be easily measured and included on an offer letter. You can’t see it in the compensation numbers and, unless you go looking for it intentionally, it rarely comes up in an interview. But it shapes every day you’ll spend there, in a way your paycheck doesn’t. A great team at a mediocre wage can still make for a good year. A toxic team is rarely redeemed by a bigger direct deposit.

Weighing All Four at Once

This is what made my decision so difficult, and also what eventually made it clear. The role passed the first question easily — it’s work I’d have been glad to do. It was thinking about what it would have cost outside of work that made it hard. If I’d only been weighing the money and my interest in the work, I’d have said yes immediately. It was weighing both of those against the cost to my family situation right now that took a week and a dozen reversals to work through.

None of the questions automatically outweigh the others. A great team can make it easier, but will never fully offset work you genuinely dislike doing every day. A role you’d love doesn’t erase a cost to your family if that cost is real. And no amount of money reliably compensates for either one. My brother’s new paycheck didn’t make up for the culture he’d traded into. A higher level position wouldn’t have made up for what my own offer would have cost at home. The number is never the whole answer. It’s just one input into a decision that should account for all four.

Final Thoughts

The lesson here is not that you should say no to more money. My point is that a job offer always has at least four separate questions you need to answer, and the size of the paycheck can only answer one of them. Know what you’re actually being offered — the work itself, what it will cost you outside of work, and the people you’d be joining — before you let the number make the decision for you.

From Theory to Action

1. Next time you’re considering a new job, ask yourself all four questions: how is the pay, do I want this work, what will it cost me outside of work, and who would I actually be working with. Answer each on its own — don’t let a strong yes on one answer the other three.

2. Write down the real week the new job would create — hours, travel, on-call time, what you’d be giving up at home — not the title, the actual shape of the days.

3. Put the concrete costs on paper next to the number, not just in your head. A raise that looks obvious in the abstract often looks different once its real costs are written down beside it.

4. If you turn something down, write what would have to change for the answer to be yes later. That keeps “not now” from quietly turning into a door you assume is shut forever.

5. If you’re already leading and don’t like it, ask the same questions about the job you’re already in. The fit you chose a few years ago isn’t guaranteed to still be the right one today.

6. Give yourself permission to define success as something other than the next title and the next raise. It’s a legitimate answer, not a lesser one.

Enough people have asked me for career advice over the years that I’ve started to notice a pattern in how those relationships go. Some of them turn into real mentorships that last years. Most fizzle out after one or two conversations. The difference rarely comes down to how smart or capable the person is.

It comes down to what they did with what I told them.

I’ve written before about finding a mentor and the broader role mentorship plays in a leader’s development. Both of those posts are about the first half of the process: how to find someone, how to approach them, how to get the relationship started. Today’s post is about the second half: how to ensure you stay worth that person’s time once they’ve said yes.

The Pattern I Keep Seeing

When a relationship fizzles out, this is usually how it goes. Someone reaches out with a question. I answer it, usually in more detail than they asked for, because I like being helpful. A few weeks later, they’re back with a new question, or several questions at once, often a scattered mix of things that have been bothering them since we last talked. We never circle back to the first thing, they never share any updates with me. We just keep adding new open loops.

After this happens a few times, I stop being as generous with my time. I still answer. I’d never turn someone away. But my responses become less personal and more perfunctory. If I can’t tell whether someone acted on the last thing I told them, whether my last piece of advice did anything, I have no real signal that the next piece will either. Eventually I start treating the conversation as a favor instead of an investment.

Here’s the version I like much more, the version that doesn’t fizzle. Someone reaches out, and before they ask anything new, they tell me what happened with the last thing: “You told me to stop giving my team lead the answer and start asking her what she’d try first. I did that for three weeks. It was slower at first, and then it wasn’t — she handled two escalations on her own that she definitely would have brought to me before.” Then, and only then, do they ask the next question.

That person gets more of my time, even though they ask for it less often. I find myself thinking about their problems between conversations. I start mentioning them to other people. It’s more rewarding for my because I can see that my advice is actually being followed and making a difference.

Why Mentors Say Yes in the First Place

There’s a line I came across a few months ago that’s stuck with me since: a mentor is just someone who answers more than one question.1

That framing is useful because it strips away the formality most people assume mentorship requires. You don’t need a title, a standing meeting, or a signed agreement. You just need someone willing to keep answering your questions.

Most advice about finding a mentor focuses on the first question: how do you get someone to help you once? But a mentor isn’t someone that just helps you out once, it’s someone willing to answer your second, third, and fourth questions. And often, their willingness to do that depends on what you did with the answer to the first one. Mentors aren’t running a help desk. They’re investing attention in watching someone put their advice to use, and that investment only keeps paying out if they can actually see it work.

A mentor is just someone who answers more than one question. The whole relationship depends on staying worth a second answer.

The Protocol: Act, Report, Ask Again

The fix is incredibly simple. Three steps, in this order, every time:

1. Act on what you were told, before you ask anything else.

2. Report back specifically: what you were told, what you did with it, and what happened. Not a generic “it went well,” but the actual result.

3. Ask the next question, now that you’ve earned the right to.

Notice what this protocol does to the conversation. It turns every interaction into evidence instead of a request. A mentor who hears a concrete report doesn’t wonder whether the relationship is working or is worth their time. They can see it. And once they can see it, continuing to invest in you stops being pure generosity and starts being an easy, obvious call.

This also solves the “too many questions” problem on its own, without you having to deliberately ration yourself. If you can’t report back on something yet, you haven’t finished acting on the last round. And if you haven’t finished acting on their last advice, it usually means you’re not ready for more. The protocol paces you automatically.

How to Be a Good Mentee

I wrote a while back about what makes someone worth sponsoring, the three things that make someone’s manager comfortable vouching for them:

1. Work that survives without them there to defend it

2. Visibility outside their daily weeds

3. Trust that doesn’t require a favor to sustain

Being a good mentee follows the exact same pattern.

Work that survives without you there to defend it, as a mentee, is following through on advice without needing to be checked up on. Visibility is following up and telling your mentor what happened, instead of just letting the results sit in your own head. And trust that doesn’t require a favor is a mentor who keeps answering your next question because doing so has consistently been worth their time, not because they feel obligated.

None of this requires impressing anyone. It requires being, in a very literal way, helpable — someone whose problems actually move when you hand them good advice, which makes handing you good advice worth doing again.

Space Is Fine. Disappearing Isn’t.

There’s an important piece here I want to address directly, because it goes counter to what most people believe about mentorship. The relationships that work well aren’t necessarily the ones that meet the most often. You don’t need to have a pre-scheduled monthly meeting. In some of the best mentoring relationships I’ve been part of, we only had a conversation every few months, sometimes closer to once a year. That’s fine. What makes it fine is that every single conversation is substantive — there was real action taken, a real report, a real next question — instead of a vague catch-up.

Relationships that fizzle out are not simply those where you meet infrequently. They’re the ones with no real conversation ever closing the loop on the last one. Silence after giving advice comes across as nothing happened. A bit of space followed by a real report comes across as someone actually doing the work and coming back when there’s something worth discussing. A mentor can feel the difference, even if they can’t explain it.

From Theory to Action

Nobody teaches this because it sounds too obvious to need teaching: act on what you’re told, tell your mentor what happened, then ask the next thing. But almost nobody actually does it, which is why the people who do stand out immediately. Being a good mentee isn’t about asking better questions. It’s about becoming the kind of person whose results make answering those questions worth someone else’s time.

1. Before you ask your mentor anything new, write down what you actually did with the last thing they told you. If the honest answer is “nothing yet,” that should be your next step, not a new question.

2. The next time you reach out, lead with the report, not the request. One or two sentences: what they told you, what you did, what happened. Ask your question after, not before.

3. Cut your question list down to the one or two that actually matter. If you’re showing up with five scattered concerns, you haven’t finished processing the last conversation yet.

4. Pick one piece of advice you got months ago and never closed the loop on. Go back to that person, even if it feels late, and tell them what you did with it, or admit you didn’t do anything. Both are more useful to them than silence.

5. Don’t treat infrequent contact as a sign the relationship is fading. If your last few conversations were substantive, space is a feature, not a problem. Don’t manufacture an unneeded check-in just to stay “active.”

Walk any production floor for ten minutes and you can usually spot the busiest person in the building. Radio going constantly. Moving fast between stations. Voice a little sharp, a little urgent. Everyone around them can feel the intensity.

Keep watching and you’ll probably also find the person having the smoothest shift: calmer, quieter, rarely on the radio unless they actually needs something. Their zone just moves. No drama, no visible effort, no story to tell about it later.

If you had to guess which one was outperforming the other, which would you pick?

The Leader Who Was Always Behind

A newer leader reached out to me a few months ago, looking for advice. She wasn’t just failing. She was drowning. And she couldn’t figure out why, because she felt like she was working harder than anyone else on her shift.

Her days were constant motion: coaching an associate who was struggling, restarting a piece of equipment that had gone down again, pulling records together ahead of an audit, putting out whatever fire had started while she was busy putting out the last one. From the first minute of her shift to the last, she was in constant motion. And still, at the end of most days, she told me when we talked, she felt like she’d missed her most important tasks.

That gap is what I want to talk about today. She wasn’t lazy, and she wasn’t disorganized in the way people usually mean when they say that about themselves. She was reacting to whatever problem was loudest, all day, every day. That might be a reasonable way to survive a single rough shift. But it’s a bad way to lead one, week after week, because it means the day is running you instead of the other way around.

It’s also the answer to a question a lot of people ask themselves: why does that one person — the one who is never frantic, who doesn’t appear to be doing all that much — keep getting the recognition, the stretch project, the promotion, while people visibly working themselves to the bone get passed over? It’s rarely because they’re doing less. It’s because they figured out, earlier than most, that success tracks with effectiveness and output, not with busyness or hours worked. The people still fixated on looking busy are optimizing for the wrong thing, and in the long run it shows up in the results, even when it doesn’t show up on the floor in the moment.

What “Busy” Actually Measures

Busy measures motion. Productive measures output. They overlap often enough that sometimes we stop checking whether they’re actually the same thing and just assume that they are. On a floor where activity is loud and visible and output takes a report to see, motion wins the perception contest every time.

This isn’t a character flaw in the people who look busy. Most of it is completely genuine. The leader I mentioned earlier wasn’t faking anything. She really was handling real problems, really was moving fast, really was stretched thin. The issue was not that her effort was fake. It’s that effort and output aren’t the same thing, and a leader who can’t tell them apart (about her own day or anyone else’s) will consistently chase the wrong thing.

As I wrote in The Art of Prioritization: “Don’t confuse being busy for being effective.” I didn’t go too far into it then, but confusing these things and mistaking one for the other is one of the most common and most expensive mistakes a new leader makes. Not just about their own time, but about how they see everyone else’s.

Being busy is easy to see. Being productive often isn’t. The difference matters more than nearly anything else for success.

The Bricklayer Who Slowed Down to Speed Up

In the early 1900s, an engineer named Frank Gilbreth turned his attention to something nobody had bothered to study closely before: how bricklayers actually laid bricks.1

Watching experienced masons at work, Gilbreth noticed they were constantly in motion: bending down for each brick, adjusting their stance, reaching, shifting, correcting. It looked like hard, busy work, because it was. Nobody was standing around. Every motion had a reason.

Gilbreth counted the motions anyway, and found that a bricklayer was using around 18 distinct movements to lay a single brick. Then he redesigned the job itself — an adjustable scaffold that kept the work at the right height, bricks and mortar staged within easy reach, a more efficient stroke — and got that number down to about 5 motions per brick. The bricklayers weren’t working any less hard, but they produced roughly double the output using less than a third of the motion.

The masons before Gilbreth arrived weren’t lazy, and they weren’t doing anything wrong by the standard of the day. They were simply busy in a way nobody had ever questioned, because busy was the only thing anyone had ever measured.

That’s the same gap the leader I mentioned earlier was standing in, a hundred years later in a different industry. Constant motion isn’t evidence of the right motion.

Why the Floor Rewards Looking Busy

If motion and output aren’t the same thing, why do so many operations, and so many managers, keep rewarding motion?

This happens because motion is easy to see and output usually isn’t, at least not in the moment. You can watch someone move fast. You can’t watch throughput per labor hour happen; you have to go pull a report to check it. One is free and instantaneous. The other takes a report and a spreadsheet.

I wrote about a version of this same gap in Developing Your Leadership Brand. The difference between a manager who’s seen as a strong executor and one who’s seen as a strategic partner often comes down to what other people notice, not just what actually gets done. The same distortion happens one level down, between an associate or team lead who looks like they’re carrying the floor and one who’s actually outperforming the rest. Visibility has a gravitational pull on our judgment that has nothing to do with results, and it takes deliberate effort to resist it.

There’s also a reinforcing loop that’s important to watch out for: the busiest-looking people often get positive attention for exactly the behavior that isn’t working. If you praise the visible hustle enough times, you teach your team that hustle is what you’re measuring. Meanwhile, the people that are quiet but more efficient don’t get any recognition at all, because nothing about their day looked notable.

An Ounce of Prevention

Let’s go back to the leader I mentioned earlier. Almost everything that kept her running — the equipment restart, the problem on the floor, the scramble before the audit — was cure-work. Something had already broken, and she was the one who showed up to fix it. None of it was wrong to do. Somebody has to restart the equipment.

But almost none of her day went to the other kind of work: the small, unglamorous, preventive kind that keeps the equipment breakdown from happening, the fire from starting, or the audit from turning into a scramble in the first place. You may have heard the saying that an ounce of prevention is worth a pound of cure. This is true in many aspects of life; certainly in operations. The leaders who do well tend to be the ones who’ve learned to spot the small, simple things that need to be fixed before they turn into the big, expensive things that eat a whole shift.

This is exactly what Gilbreth did to bricklaying. He didn’t find a way to fix bad bricklaying faster. He removed most of the reasons a mason needed to bend, reach, and adjust in the first place. The cure disappeared because the cause did.

Measure the Thing, Not the Motion

None of this means visible urgency is always wrong, or that a calm floor is automatically a productive one. Some situations genuinely call for speed and intensity, and some quiet zones are quiet because standards have slipped, not because they’re running well. The point isn’t that busy is bad. It’s that busy isn’t information, on its own, about anything.

The fix isn’t complicated, even if it takes discipline to apply consistently: stop evaluating performance by how a shift felt and start checking what it actually produced. In Metrics that Matter, I wrote about the “Big 5” — a small set of safety, quality, and productivity indicators, including throughput per labor hour, that cut straight through this exact kind of noise. Identify the handful of things that truly matter, whatever they might be for your team, and focus on measuring those things specifically. Everything else is just noise.

Breaking Your Own Busy Habit

This applies to your own day just as much as it applies to how you read your team. If you’re the manager whose radio never stops, who’s proud of how little downtime you have, it’s worth asking yourself the same question that I asked the manager who came to me for help: is the motion producing something, or is it just motion?

In The Power of Focused Work, I wrote about the illusion that juggling more tasks at once makes you more productive, when it usually just makes you slower and more error-prone at all of them. The busy-versus-productive gap and the multitasking-versus-focus gap are close cousins. Both mistake activity for progress. Both feel, from the inside, exactly like hard work.

Here’s the uncomfortable version of this question: if someone pulled your actual output for the week — the decisions you made, the problems you actually closed, real progress you made on the things that matter — would it match how busy you felt? For a lot of us, the honest answer is no. A couple years ago I started keeping a calendar. It’s my practice that at the end of the day I write down the single most important thing I did that day. At the end of the month I look back at my calendar and ask myself whether those things actually mattered in the big picture.

Emergencies will happen. Things come up that you couldn’t have predicted or prepared for. Some of your time will go toward these sort of things. But each day, strive to accomplish at least one thing that truly matters in the long run. This helps put you in the mindset of thinking big picture and preventing fires instead of just putting them out.

Final Thoughts

Business is easy to spot and easy to reward, because it’s loud and visible and immediate. Productive is quieter, and it usually requires you to go look at a report. Left unchecked, this difference in visibility will consistently pull your attention (and your recognition) toward motion instead of results, whether you’re evaluating your team or yourself.

Gilbreth didn’t make bricklayers work harder. He made their effort actually count for something, by looking beyond how busy the job looked and studying what the job actually required. That’s the same change available to any leader willing to check the numbers instead of trusting the noise.

The busiest person on your floor might be your best performer. Or they might just be the one you’ve noticed the most. The only way to know the difference is to go check.

From Theory to Action

1. Pick two people on your team whose performance you’d rank from memory, then go pull their actual numbers. Throughput, quality, whatever’s relevant to their role. See if the ranking survives contact with the data. If it doesn’t, that gap is worth sitting with.

2. Track your own radio and interruption volume for one shift. Notice how much of your day is genuinely necessary motion versus habitual motion. Most people are surprised by the ratio.

3. Notice who you praise, and for what. For one week, jot down who you gave positive feedback to and what specifically prompted it. If most of it is “you were really on top of things today” rather than a specific result, you may be reinforcing visibility over output without meaning to.

4. Ask a quiet high performer how they see their own week. They may not describe their work as impressive, because nothing about it feels dramatic to them. That’s useful information about how invisible good process can be, even to the person doing it well.

5. Build one Gilbreth-style question into your process reviews: “What’s the minimum motion this task actually requires?” Use this information to find the version of the job that requires less wasted effort for the same result.

6. Pick one recurring task in your own week and count your own motions. Emails, check-ins, walking the floor — wherever you suspect you’re busier than you need to be. Look for one genuine Gilbreth-style redesign: fewer steps, same or better outcome.

7. Name the one or two “fires” that eat the most of your week, and for each one, ask what small, repeatable action — done earlier and consistently — would prevent it instead of requiring you to keep fighting it. That’s your ounce of prevention.

It’s 6:50 AM. You’re walking to your pre-shift planning meeting, rehearsing a few points you want to make, when one of your associates steps into your path.

“Hey, do you have a minute?”

She isn’t quite looking at you. She tells you things have been rough at home, she hasn’t slept, and she’s not sure she should be on equipment today.

Your meeting starts in six minutes. This conversation isn’t on your daily agenda. You didn’t rehearse it. But she’s waiting for you to say something.

Some of the moments that shape how your team sees you won’t be on a calendar. They show up mid-walk, mid-shift, mid-sentence. An injury. A tearful associate. A senior leader asking why a line is down. A peer challenging your call in front of your team.

In The Conversation You Keep Postponing, I wrote about the hard conversations you can see coming, the ones where you have time to plan your approach. This post is about the other kind: the ones that surprise you.

The spark for this was Josh Anderson’s piece, “You Can’t Script an Unscripted Moment,” at The Leadership Lighthouse. Josh argues that the moments that most define a leader never get scheduled, and that the steadiness to handle them grows out of earlier moments when you aren’t steady at all. I wanted to look at what that means for someone in their first year of leading a team.

My take? You can’t script an unscripted moment. But you can prepare yourself for when they inevitably arise.

The Script Was Never the Point

When we talk about “scripting” a conversation, we usually mean predicting it: guessing what will be said and lining up a reply. That works for the conversations you know are coming. It can’t work for those you don’t see coming, for obvious reasons.

Beside which, even when you do have the right answer somewhere in your head, surprise and pressure can make it hard to remember. Stress narrows your thinking. I learned that firsthand.

Early in my time as an Area Manager, one of my most tenured team leads stopped me in the middle of a pre-shift huddle and challenged a staffing call I’d just made, in front of the entire team.

He wasn’t wrong to ask. But I hadn’t prepared for being publicly challenged in that setting. I was caught off guard and my first instinct was to defend the decision point by point, right there, in front of everyone. I didn’t want to look like I didn’t know what I was doing in front of my entire team, so I floundered around for a half-baked answer. I was flustered and everyone could tell.

I didn’t yet have an instinct for how to keep my cool and respond in public, under pressure, without notice.

The information wasn’t the gap. I had a reason for the decision I’d made. But his challenge caught me by surprise and I responded poorly. That surprise is exactly the space an unscripted moment opens up.

If you’ve fumbled a situation like this, you’re not alone. Everyone goes through it. You can’t get better without being bad first.

What the Fire Commander Couldn’t Explain

In 1985, research psychologist Gary Klein set out to study how experienced fireground commanders make decisions under pressure.1 His team interviewed 26 commanders averaging 23 years of service and examined 156 decision points. They expected commanders to narrow their options down to a few, but in over 80% of those decisions, the commanders didn’t compare options at all. They recognized the situation and acted.

One incident from that research has stayed with me. A crew was fighting what looked like a routine kitchen fire, but the fire wasn’t behaving the way it should. The living room was hotter than expected and strangely quiet. The commander ordered everyone out, and moments later the floor they’d been standing on collapsed. The fire’s base was in the basement beneath them, which explained both the heat and the muffled sound.

The commander credited a sixth sense, even ESP. Klein was too much of a rationalist to accept that, and found instead that the commander’s expectations had been broken by cues so subtle he wasn’t consciously aware of them.

That’s the whole “secret,” and there’s nothing mystical about it. Experienced people decide faster because the situation matches something they’ve encountered before. That was the difference between me and the tenured team lead that challenged me. He’d absorbed years of exactly this kind of pressure. I hadn’t yet.

It also means the reason you feel slower than the veterans on your team isn’t because you aren’t capable. You just haven’t had the repetitions yet. You can’t skip them, and you can’t wait ten years for them either. But you can prepare in ways that help, and you can build your own pattern library faster than time alone otherwise would.

Prepare the Leader, Not the Script

There are three major things you can settle ahead of time, so that when a moment like this comes up, you’re at least partly prepared.

Your non-negotiables. Decide now what holds no matter how the moment unfolds. Safety comes before production. You tell the truth even when it’s uncomfortable. You don’t promise what you can’t deliver. You don’t make a permanent decision in a temporary state, unless safety is on the line. These aren’t scripts. They don’t tell you exactly what to say or how to respond. But having these guardrails clear now means that you don’t have to come up with them while under stress.

Your bridge phrases. A bridge phrase is a sentence that’s true no matter what just happened and buys you time to think. “Thank you for telling me.” “Give me a second to think about that.” “Here’s what I know, and here’s what I don’t.” “I don’t want to guess. Let me look into it and I’ll have an answer for you by end of shift.” These work upward too. When a senior leader asks why a line is down and you don’t know, “I don’t know yet, but I’ll follow up today” beats a confident guess every time.

Your bench. Every new leader is surrounded by people who have seen what they haven’t. Know ahead of time who you can call for equipment problems, who for people problems, who for safety, and who for “I don’t even know what I’m looking at.” Your own team belongs on that list. As I wrote in You’re the New Manager. They’ve Been Here for Years. Now What?, your veterans are watching to see who you are when things get hard. Learning to ask “What does your experience tell you?” before launching into your own analysis is one of the fastest upgrades a new leader can make.

The First Ten Seconds

When the moment arrives, you don’t need a speech. You just need about ten seconds and three moves.

Safe. Is anyone at physical or emotional risk right now? If yes, that comes first and everything else waits.

Slow. Your body goes first: one breath, a lower voice, stop rushing. As I wrote in You Set the Weather, your team reads your emotional state before they process your words, and when you’re surprised it’s especially important to stay calm.

Say the next true thing. Not the whole answer. Just what you heard, what you’re going to do next, and when.

Back to the associate from the opening example. Safe: you ask whether she’s okay around equipment right now. She isn’t sure, so she’s not operating today. Slow: you step out of the traffic flow and lower your voice. Say the next true thing: “Thank you for telling me. I’m glad you did. Let’s get you on something safe for now, and after huddle I’ll come find you so we can talk about what you need.”

Notice what you shouldn’t do. You don’t try to solve her life in six minutes. You can’t promise to keep everything between the two of you. If something has to go to HR or your own manager, tell her that up front. And you now owe her a conversation after huddle, because a bridge phrase is a promise. Pick ones you can keep.

Building Your Pattern Library Faster

You can’t skip the reps, but you can get more out of each one.

Debrief every surprise, however small. Within a day, ask yourself three questions: What did I notice? What did I do? What would I do next time? Two minutes in a notebook counts. The Debrief That Builds Leaders covers the team-lead version, and the same questions work on yourself.

Practice with “what ifs.” Practitioners who train decision-makers in high-pressure fields argue that pattern recognition is built through realistic scenarios, not by studying theory. So take five minutes at the end of a shift and ask a team lead: What would you do if a forklift hit a rack right now? If someone told you they didn’t feel safe on equipment? If the GM asked why we were down? Let them answer first.

Collect other people’s moments. Ask a veteran to tell you about the worst surprise they ever handled. This is one of my favorite questions to ask when I meet someone new. You get to borrow years of pattern library in a ten-minute story.

Steadiness under pressure doesn’t develop on it’s own. It gets built out of earlier moments - as long as you actually learn from them.

After the Moment

You’re going to handle some of these badly. Everyone does. What separates good leaders isn’t a clean record, it’s whether they go back.

If you were short with someone, missed something, or made a call you’d like back, return within a day. “I’ve been thinking about yesterday. Here’s what I got wrong, and here’s what I’m going to do.” Short. No over-explaining, no beating yourself up. You Made a Mistake in Front of Your Team covers how to do this without turning it into a performance about you.

The follow-through on what you promised in the moment matters just as much. People forget your exact words. They remember whether you came back.

You can’t script the moments that test you as a new leader. But you can decide ahead of time what you stand for, keep a few phrases in your back pocket, and know who to call. In the moment, be safe, slow, and say the next true thing. Afterward, learn from it, and go back if you need to.

From Theory to Action

1. Write your non-negotiables. Take ten minutes and write three to five lines that hold no matter what happens. Safety before production. Tell the truth. No promises you can’t keep. No permanent decisions in a temporary state. Put them somewhere you’ll see them.

2. Choose three bridge phrases and say them out loud. Pick sentences that are true in any situation, like “Thank you for telling me” or “I don’t know yet, and I’ll follow up by end of shift.” Say them aloud a few times so they live in your mouth, not just your notes.

3. Build your bench. List who you’d call for equipment issues, people issues, safety questions, and “I don’t know what I’m looking at.” Introduce yourself to anyone on the list you haven’t met.

4. Ask “What does your experience tell you?” this week. Try it with a tenured team lead on a real, low-stakes question, before you offer your own analysis. Notice what they see that you don’t.

5. Run one “what if” a week. Five minutes at the end of a shift with a team lead. Rotate scenarios: an injury, an upset associate, an unexpected question from a senior leader. Let them answer first.

6. Debrief your next surprise within 24 hours. What did I notice? What did I do? What would I do next time? Write it down. Over a few months, that notebook becomes your own pattern library.

7. Go back. If you promised a follow-up, deliver it on time. If you handled something badly, return within a day and say so plainly.

My book, Leading From the Floor, didn’t start as a book. It started as notes.

In 2022, a young leader I was mentoring, who was just starting to think seriously about a management career, began coming to me with problems as they came up: a conflict with a peer, a decision she wasn’t sure how to make, a moment where she doubted herself in front of her team. I answered each one as it came, in whatever order her week happened to raise them.

After a while, I noticed something. Most of what she was struggling with, I’d struggled with myself a few years earlier. So I started writing down what we talked about, and eventually reorganizing it — not in the order the problems came up, but in the order that would make the most sense to someone reading it from the start. That reorganized version became the book.

What Mentoring Her Gave Me

Most advice about becoming a mentor focuses on what it gives the other person: guidance, encouragement, a sounding board. That’s true, but it undersells what it does for the mentor.

Trying to help her forced me to be more intentional about my own leadership than I’d previously been. Explaining a principle clearly enough for someone else to use it meant I couldn’t just operate on instinct anymore. I had to know what I was doing and why, well enough to teach it. And once I’d said something out loud as advice, I had to actually live it.

I found that out directly. I’d told her to stay focused on what was truly important during a shift, and to delegate or ignore the minor annoyances that show up in the middle of one. A couple of days later, I caught myself deep in a problem any one of my direct reports could have handled, while the bigger picture I was ultimately responsible for wasn’t being monitored. There wasn’t a dramatic moment where someone called it out. It just hit me, out of nowhere, that I was doing exactly what I’d told her not to do. I handed the problem off and went back to watching what mattered.

That pressure to consistently practice what I was teaching is what prepared me for the role I’m in now, teaching hundreds of new managers how to do their jobs well, instead of running one team directly. It wasn’t the notes themselves, and it wasn’t the book that eventually came from them. What made the difference was the deliberate, focused thought I had to put into my own actions, because I was accountable to someone else’s growth. This intentionalality made me a better leader in so many ways. I don’t think I’d have been ready for my current role without that pressure forcing the change first.

The Relationship Doesn’t Stay Fixed

Those conversations started in 2022. Four years later, she’s gone from an entry-level employee to managing a department, and now runs employee training for her site. I’ve gone from supervising 3-4 department managers and a team of roughly 120 people, to teaching new managers across 70 sites how to do the job well — trading direct oversight of one team for influence over how dozens of teams get led. Neither of us is where we were when this started, and neither of us needs the same thing from the other that we did back then.

But the relationship didn’t end when the original need did. We still check in periodically, and it’s not one-directional anymore; she’s helped me think through things just as often as I’ve helped her, especially anything closer to her current expertise than mine. Most advice about mentorship describes it as a role you occupy. You’re the mentor, they’re the mentee, and the relationship exists to close that gap. That’s true at the start but it doesn’t have to stay true, and treating the roles as fixed is a good way to let a valuable relationship fizzle out the moment the original gap closes.

Final Thoughts

Becoming a mentor isn’t a status you earn once and hold. It’s noticing when you have something worth organizing and sharing with someone else, and doing it. Be willing to let the relationship change shape with time, instead of assuming it has to run in the same direction forever. Sometimes that means a mentee becomes someone who helps you back years later, in ways neither of you expected when it started.

The mentee I started taking notes for in 2022 didn’t just get a mentor. She got a more intentional leader than I would have become without her — and four years later we’ve both benefited from the relationship.

From Theory to Action

1. Write down one piece of advice you’ve given informally more than once. Organize it into something you can quickly and easily hand someone the next time the question comes up.

2. Notice whether explaining something out loud changes how you think about it yourself. If it does, that pressure is worth using deliberately, not just noticing by accident.

3. Revisit one mentoring relationship you’ve assumed has a fixed direction. Consider whether the other person has something to teach you now, even if that wasn’t true when the relationship started.

4. Stop waiting to feel qualified before you start organizing what you already know for someone else. The organizing is often what makes you qualified, not the other way around.

For the mechanics of finding a mentor for yourself, see Find a Mentor and The Role of Mentorship. For what this compounds into over time, see Mentors Advise. Sponsors Advocate. and Leadership Capital.

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.