The one question to ask before you coach anyone.
A manager pulls a rep aside for the third time this month. Same miss, same conversation. "You've got to slow down. Ask more questions. Confirm before you close." The rep nods, tries hard, does better for a week, and then the miss comes back, because the rep was never the problem.
I've watched this happen in every operation I've ever led, and I've been the manager getting it wrong. When something breaks, our instinct is to coach the person standing in front of us. It feels like leadership. It feels like accountability. But if you skip one question, it's neither. It's just pressure applied to the wrong place.
Here's the question: is this a person problem, or a system problem?
Most leaders never ask it. They see a number slip or a behavior miss and they go straight to coaching, because the person is right there and the system isn't. But a person is easy to talk to and hard to change. A system is hard to see and easy to change, once you actually look at it.
The tell is repetition. If one person misses one time, that might be them. But if the same failure keeps showing up, across different people, across shifts, across teams, it isn't a coincidence and it isn't a character flaw shared by a dozen people at once. It's the process. It's the tool. It's the policy. It's the training that never happened, or the knowledge base that went stale, or the incentive that quietly rewards the wrong thing. When a third of your problems trace back to the same gap, that was never a frontline issue.
And coaching a person for a broken system is how you lose good people. Think about what it does to someone: you've told them, over and over, that the problem is them, when they can feel that it isn't. They lose trust in you, because you're not seeing the situation clearly. They lose trust in themselves, because they're trying and it isn't working. Your best people don't quit over hard work. They quit over being held responsible for things outside their control.
I learned this the hard way, and then I learned it the good way. Early in my career I ran a team the way I thought a boss was supposed to. I made the calls, I applied the pressure, and when the numbers didn't move, I coached harder. It didn't work, because I was treating a system problem as a people problem. Years later, overseas, I inherited the worst-performing site in the network. Everything looked like an individual performance problem on paper. It wasn't. The real issue was a culture where people hid what they didn't know to protect their reputation, so mistakes stayed buried and nobody fixed the thing underneath. We didn't coach our way out of that. We changed the system. We made it safe to say "I don't know this yet," and we fixed the gaps together. The performance followed.
So before you coach, run the read.
First, see it straight: look at the actual evidence, not the story in your head about who's slacking. Then find the cause: person, or system? Ask it out loud. If the failure is isolated to one person in one moment, coach the person, meet them where they are, and get them to one clear next step. But if the pattern repeats, stop coaching and clear the path: go change the thing that's producing it. That's not going easy on people. High standards stay high. You're just aiming your standards at the right target.
None of this means people never own their part. They do, and so do you. The first question a leader asks is always "what did I control here?" But accountability without diagnosis is just blame with better posture. The leaders I trust most aren't the ones who coach the hardest. They're the ones who look the longest before they decide who, or what, actually needs to change.
Diagnose before you coach. Your people can tell the difference, and so can your results.