Break the Cycle of Rework: Tell Them!

It's 11 p.m. on a Tuesday. You're sitting at your kitchen table with an energy drink, staring at a presentation that someone on your team submitted earlier today.

It's not good enough. Loud sigh.

The data is all there, but the story isn't clear. The slides are cluttered. The flow doesn't make sense for this particular client. You have a meeting in nine (overnight) hours, and there's no way you can present this as-is.

So, you do what you've done a dozen times before. You sigh, you crack your knuckles, and you start rebuilding the whole thing from scratch. By 2 a.m., it's done. It's polished. It's exactly what it needs to be. You drag yourself to bed, set three alarms, and show up to the meeting exhausted but prepared. The presentation goes well. The client is happy. Crisis averted.

Except this isn't a one-time crisis, it’s a pattern. And every time you fix someone else's work in the middle of the night, you're not solving the problem. You're feeding it.

Two People, Two Completely Different Experiences

Let's talk about what's actually happening in this scenario, because there are two people involved, and they're living in completely different realities.

Your reality as the manager. You received something that wasn't up to standard. You thought about handing it back, but there wasn't enough time. You fixed it yourself because the work had to get done. Now you're frustrated because this keeps happening and you’re wondering why your team doesn't take more ownership. You're exhausted from constantly saving everyone at the last minute.

Your employee's reality. They submitted a presentation they thought it was decent. Maybe not perfect, but a solid draft. They never heard anything specific about what was wrong with it. Then they showed up to the meeting and saw a completely different presentation. They have no idea what you changed or why. They're wondering why they should even try next time since you're going to redo everything anyway. They're also starting to wonder if you just don't like them.

Same situation but totally different experiences.

The worst part is that neither of you is getting what you need. You're not getting a team that can produce quality work independently and they're not getting the feedback and development that would help them improve.

You're both stuck in a cycle that feels frustrating and pointless. But the cycle won't break on its own.

How the Cycle Starts (and Why It's Hard to Stop)

Nobody sets out to become the person who fixes everything at 2 AM. It usually starts innocently enough.

Maybe the first time it happened, you really were in a time crunch. The deadline was tight, the stakes were high, and teaching someone how to do it better would have taken longer than just doing it yourself. So, you fixed it.

But then it happened again. And again. And somewhere along the way, "just this once" became "just how things work around here."

The pattern becomes self-reinforcing. You fix things silently, so your team never learns what needs to change. They keep producing work at the same level, so you keep having to fix it. You get more frustrated, they get more confused, and everyone gets more tired.

I've talked to leaders who have been stuck in this cycle for years. They're running on fumes and they resent their teams. They fantasize about hiring someone who "just gets it" and doesn't need so much handholding.

I’ve learned that the issue usually isn't that their team can't do the work. The issue is that no one has ever clearly explained what "good" looks like. The team is operating with incomplete information, and the leader is operating with unexpressed expectations.

The Fix Starts with Saying the Thing

At PCG, we have a philosophy that guides our work with clients. We call it "Tell Them."

The idea is simple: Most people problems at work are actually communication problems. Not bad employees, lazy teams, or incompetent hires. Just unclear expectations, avoided conversations, and leaders quietly fixing things instead of teaching people how to do it.

Tell Them means saying the thing out loud. Not hinting. Not assuming. Not hoping people will figure it out through osmosis. We say Tell Them needs 4 things to work: Say it now, say it with specifics, say why it matters, and then say it again if needed.

Instead of vague feedback like "this needs to be more polished," you get specific about what's actually not working.

Instead of assuming they should already know what you want, you explain why it matters and what the client needs to see.

It takes more time in the moment. But it saves you countless hours of rework in the future.

A Different Way Through

Let me walk you through what this could look like in practice. Same scenario, different approach.

Your employee submits a presentation. You review it and immediately see problems. The instinct to just fix it yourself is strong. But instead, you send a quick message. "Hey, I looked through the presentation. I have some thoughts. Can we chat for 15 minutes this afternoon?"

When you sit down together, you don't just tell them what to change. You explain your thinking. "The data here is strong. You clearly did the research, and that's great. But I'm having trouble following the story. Right now, it feels like a list of facts. What we need is a clear narrative that helps the client understand the business impact. Let me show you what I mean."

Then you walk through it together. You point to specific slides. You explain what this particular client cares about. You show them how you would restructure the flow to make the main points land faster.

"This client makes decisions quickly. They don't want to sit through 30 slides of background. They want to know the bottom line up front, and then they want the supporting evidence. So let's move this conclusion slide to the beginning and use the rest to back it up."

Now your employee understands something they didn't understand before. They're learning how to read this client. They're seeing how structure affects impact. They're getting insight into your decision-making process.

Will the next presentation be perfect? Probably not. But it will be better. And the one after that will be better still. That's how capability gets built, in real-time examples and coaching.

Why "Be Specific" Changes Everything

One of the biggest reasons feedback fails is that it's too vague.

"This isn't polished enough."

"I need this to be more strategic."

"Can you make it tighter?"

These statements feel meaningful to the person saying them. But to the person receiving them, they're almost useless. Polished compared to what? Strategic in what way? Tighter how?

Vague feedback creates a guessing game. Your employee goes back to their desk and tries to figure out what you meant. They make some changes based on their best guess. They resubmit. You're still not happy. They're still confused. The cycle continues.

Specific feedback creates clarity.

Instead of "this isn't polished enough," try "the formatting is inconsistent across these slides, and the text is too dense. Can you standardize the fonts and cut each bullet point down to one line?"

Instead of "I need this to be more strategic," try "right now, this reads like a status update. What I need is a recommendation. What should the client do, and why?"

Instead of "make it tighter," try "we have 15 minutes for this presentation, and right now it would take 30. Let's cut the background section in half and remove slides 7 through 10 entirely."

Specific feedback takes more thought. You have to identify what the problem is instead of just feeling that something is off. But it's also far more actionable. Your employee knows exactly what to do. They can fix it and learn something in the process.

Why It Matters (and Why You Need to Say So)

The other thing that often gets left out of feedback is the "why."

We tell people what to change. We sometimes even tell them how to change it. But we rarely tell them why it matters. And the "why" is where real understanding happens.

"This client needs presentations to be concise because they're extremely time-pressed. They'll tune out after 10 minutes if we haven't gotten to the point."

"The reason I want the recommendation up front is that our goal is to position ourselves as strategic advisors, not just vendors reporting data."

"I'm asking you to simplify the visuals because this audience includes people who aren't technical. If the slides are too complex, we'll lose them."

When people understand why something matters, they can apply that thinking to future situations. They're not just memorizing a set of rules for this one presentation, they're developing judgment that transfers.

Next time, they might think, "This client seems similar to that other one who was really time-pressed. I should keep this tight." Or, "I remember that we want to lead with recommendations. Let me structure this differently."

That's the shift from following instructions to thinking strategically, and it only happens when you take the time to explain the reasoning, not just the fix.

Saying It Again (Without Losing Your Mind)

Here's the part that requires some patience. You probably won't only have to say it once.

People don't always absorb things the first time. They might be nervous, or distracted, or just not ready to fully process the feedback. They might understand it intellectually, but struggle to apply it in practice. They might nail it once and then forget it the next time. This is normal. This is how learning works.

The good news is that "saying it again" doesn't mean starting from zero every time. It means building on what you've already taught.

"Remember how we talked about leading with the recommendation? I noticed this deck starts with background again. What was your thinking there?"

"Last time, we worked on making the slides less text-heavy. I'm seeing some of the same density here. Let's look at which bullets we can cut."

"You're getting better at reading what the client needs. This section is great. Now let's apply that same thinking to the opening."

Each conversation gets a little shorter and each round of feedback gets a little more focused. Over time, you're not teaching them the fundamentals anymore, you're refining and fine-tuning.

And eventually, you're not fixing their presentations at all. You're reviewing them, nodding, and saying, "This is good. Send it."

That's the goal. That's what you're building toward.

What If It Never Gets Better?

I want to address something that might be running through your mind right now, which is, "what if I do all this and they still don't improve?"

It's a fair question. Not everyone develops at the same pace. Not everyone has the capacity or motivation to reach the level you need.

But here's what I'd encourage you to consider. Have you actually given them the chance to improve? Have you been specific? Have you explained the "why"? Have you been patient enough to let them practice?

In my experience, the majority of underperformance stems from communication issues, not from capability issues. Most people want to do good work. Most people can learn and grow. They just need clearer information and more intentional support than they've been getting.

If you've genuinely done all of that and someone still isn't improving, then you have a different conversation to have. A conversation about fit, about expectations, about whether this role is right for them.

But you can't have that conversation until you've first done your part, until you've told them clearly what you need and given them a real chance to deliver it. Otherwise, you're not managing performance. You're just frustrated, working until 2 a.m. in silence.

The Time Investment Myth

The biggest objection I hear to this approach is time. "I don't have time to sit down with someone for 20 minutes. It's faster to just do it myself."

And in the short term, that's true. Fixing something yourself tonight is faster than teaching someone to do it better over the next few weeks.

But zoom out: How much time have you spent over the past year fixing work that someone else should have been able to do? How many late nights? Weekends? How many hours of rework could have been prevented if the person had just understood what you needed from the start?

The time you spend teaching pays dividends. Every conversation that helps someone understand your expectations is a conversation you won't have to have again (or at least not about that same issue). Every skill they develop is a skill you don't have to compensate for.

The investment is front-loaded, but the return compounds. A year from now, you could still be fixing presentations at 2 a.m., or you could have a team that produces work you're proud of, that requires minimal revision, that frees you up to focus on higher-level priorities.

The choice is yours. And it starts with the next conversation you have.

Your Move

Here's my challenge for you.

The next time someone submits work that doesn't meet your standards, resist the urge to silently fix it. Instead, do this.

1. Be specific. Point to concrete things, not vague impressions.

2. Explain the why. Help them understand the reasoning behind your feedback.

3. Do it now. Don't wait for the perfect moment. Don't put it off until after the deadline.

4. Plan to say it again. Assume this is the beginning of a learning process, not a one-time fix.

It will feel slower at first. It might even feel inefficient. But you're building something. You're breaking the cycle! You're creating a team that can eventually do this without you.

And maybe, just maybe, you'll get to bed before midnight.

This post is part of the "Tell Them" series from Patterson Consulting Group, where we explore how clear, direct communication can transform the way teams work.