This article is for you if:
- You’ve sent the frustrated email. Felt the regret. Watched the relationship absorb the residue.
- You’ve held the email. Waited a day. Sent something safer. Wondered if you should have just had the conversation.
- You’ve started suspecting the problem isn’t them. But you don’t have a structure for what comes next.
If any of those three describe you this month, you’re in the right room.
Patrick Lencioni’s The Advantage makes a claim many leaders find inconvenient. Organizational health, he argues, is the single greatest competitive advantage available to any business; and the foundation of organizational health isn’t strategy, vision, or talent. It’s clarity. Specifically, clarity that the leader provides about behaviors, priorities, and what winning looks like in any given role. Without that clarity, even the smartest organizations fail to execute.
Lencioni’s central provocation is that most leaders dramatically underestimate how much clarity their teams actually need. We hear ourselves give an instruction once and assume it landed. The team hears the same instruction, fills in the blanks with their best guess, and we get frustrated when they fill the blanks wrong.
Read that last sentence again. It’s the entire pre-conversation we’re having today.
Most leaders facing an underperforming team member arrive at the same binary thought: coach this person up, or cut this person loose. Both options assume the same thing. They assume the problem is the person. And until that assumption is tested, neither option is actually available to you. What if the question you’ve been asking about that team member has been the wrong question all along?
The binary itself is the problem.
A Story I Can’t Stop Telling
One of the priests I coach told me a story recently that’s been ringing in my head ever since.
He’d asked his parish receptionist, Sophia, to prepare the feast-day invitation letters for the clergy of their region. Routine task. Same letter as last year, just updated dates. He gave her the form letter. He gave her the spreadsheet of clergy addresses. And then he asked one question:
“Do you know how to use the Avery label template?”
She said yes. He knew she did; the parish had paid for her Microsoft Office certification a year earlier. He went back to his office and got to work.
Two and a half hours later he wandered back to her desk. “Are those letters done?”
“I’m just typing out the last few addresses.”
She had been hand-typing every address into the template, one at a time, for two and a half hours.
He exploded.
For a week, he stayed in his frustration. He raised it with the Parish Council. He pulled it into one-on-ones with her. He was already three steps into the performance conversation when something stopped him cold:
“Do you know how to use the Avery label template?” was a closed question with two different answers.
To him, make labels meant mail merge. To her, make labels meant type addresses into a label-shaped template. Both of those answers are technically yes. He’d asked the wrong question, and she’d given the right answer to the question he hadn’t actually asked.
A five-minute task became a two-and-a-half-hour task. Not because of incompetence. Because of an upstream gap that the leader was too frustrated to see.
Three Buckets. One Order.
Most performance problems aren’t people problems. They’re upstream problems. And the framework I use to sort them out is structurally identical to medical triage. Emergency room physicians don’t treat patients in the order they arrived. They sort by severity, ruling out the most dangerous conditions first. Most of us treat performance problems in the order they frustrate us. The Upstream Audit™ forces us to sort by upstream causation instead.
There are three buckets to work through, in this exact order, before any leader has earned the right to a performance conversation.
Bucket 1: Leadership. Has the scoreboard been clearly communicated? Does the team member know what winning looks like in this role in concrete and measurable terms? In Sophia’s case, the leadership gap was a single ambiguous question. Use the label template meant two different things in two different heads. That’s not a Sophia problem. That’s a leadership problem.
Bucket 2: Systems. Does the person have the tools, the access, the visibility, and the workflow they need to deliver? Here’s a fast test: can you find out the status of a project without interrupting the person doing it? If the only way to know the status is to text, email, or call them, you have a systems problem. The status of the work shouldn’t depend on the leader’s willingness to ask.
Bucket 3: Performance. Only after the first two buckets are clean does the third one apply. Has the person been given clarity? Yes. Have they been given systems? Yes. Has the pattern continued anyway? Then, and only then, has the leader earned the right to a performance conversation. And even then, the conversation is a structured one, not an explosion.
Notice something about the order. The first two buckets require the leader to evaluate themselves before evaluating the team member. That’s not soft. It’s not coddling. It’s accurate. And it’s why most performance frustrations dissolve before bucket three is ever reached.
What Clarity Actually Looks Like
When the audit lands you in Bucket 1: Leadership, the next-level question is: what does clarity actually look like in this role? That’s where the 4 R’s™ come in. They’re the diagnostic that turns a vague leadership problem into a fixable one.
Role. What does this position exist to do? Not the title. The job. Administrator doesn’t tell you what someone is supposed to accomplish. Make sure every parishioner who calls the office gets a response within 24 hours does.
Reporting. Who does this person actually answer to? Not the org chart. The actual person. Dual reporting almost always fails; co-leadership is no leadership. One name on the line above the role, or you’ll have a clarity problem before you have anything else.
Responsibilities. What are the tasks, duties, and decisions that belong to this role? And just as important: what doesn’t? A role with twenty-five responsibilities and no boundaries is a role nobody can succeed in.
Results. What’s the scoreboard? How will both of you know whether this role is winning? Without a defined desired result, the role drifts. The person invents their own scoreboard and optimizes for the wrong thing, or they stop keeping score altogether.
Run those four questions on any role in your organization right now. If you can’t answer all four in one sentence each, you have a leadership clarity gap, not a performance gap. What if the role you’re frustrated about has never been written down anywhere?
Don’t Bookmark This
Last month, I wrote a coaching guide for the team coaches who would be leading priests through this framework. Inside the guide, there’s a paragraph I want you to read:
Reading about this framework is not enough to teach it. Each coach and coaching priest must run the Upstream Audit™ on a real situation from your own life before the call. The goal is for both of you to have lived the audit before you teach it. Priests can tell the difference between a framework someone is delivering and a framework someone has been through. The second kind is teachable. The first kind is forgettable.
Replace priests with executives, and the paragraph holds. Your team can tell, too. The frameworks that change behavior are the ones the leader has lived through, not the ones the leader has read about.
Which is why I’m not going to ask you to bookmark this article and circle back to it later. I’m going to ask you to do the audit right now, on a real situation, before the intent passes.
- Pick a person. Staff member, volunteer, team member, or family coordination situation where someone’s execution has frustrated you in the last thirty days.
- Write one paragraph describing the presenting problem the way you’d describe it to a friend.
- Ask the Leadership question. Is the scoreboard clear? If not, stop. You have a Leadership Problem, not a performance problem. Run the 4 R’s™ next.
- If clarity is in place, apply the Systems test. Can you know the status without interrupting the person? If not, you have a Systems Problem.
- Only if both buckets are clean, move to Performance. And if you’re there, the conversation is a structured one, not an explosion.
- Write down what you learned. Where did the audit change your mind?
Two weeks ago, I almost violated my own framework. Working from the Middle East, late at night, frustrated about a 90-day cash flow forecast that wasn’t moving, my first instinct was to fire off a sharp email to the team member responsible. I wrote a different one instead. His reply named three upstream gaps I hadn’t given him: budget numbers I’d never sent, software access I’d never delivered, and a workflow change I’d never communicated clearly. The work got done. The relationship stayed intact. I wrote the whole story up here if you want the longer version.
What if the email you’re about to send is actually a leadership audit you haven’t run on yourself yet?
What if the team member you’re frustrated with is operating in a system you built and forgot to maintain?
What if the binary you’re stuck in, coach them or cut them, has been hiding the actual question all along?
The Leader Edition of the Upstream Audit™ is built for exactly those moments. It walks you through all three buckets with diagnostic questions for each. Run it before the performance conversation you’ve been avoiding. Run it on the role that’s been quietly frustrating you for months.