Agree on Quality Checks After Preventable Rework

Preventable rework costs more than the hour it takes to redo the work. It costs the trust in the next handoff, the extra time you spend rechecking things you used to take on faith, and the confidence the employee needs to keep working independently. When something has to be corrected before it reaches a customer or a partner, you get two conversations in one. The first is about the specific error. The second, more useful one, is about the review step that would have caught it. Managers who skip the second conversation end up repeating the first one every few weeks with the same employee, on the same kind of task, at the same cost.

Why This Conversation Goes Wrong

You usually walk into this conversation right after you finished fixing the error yourself, which is the worst possible moment to have it. You are frustrated, behind on your own work, and eager for a fast promise that it will not happen again. So you tell the employee to be more careful or to double check next time. That instruction feels like guidance, but it gives the employee nothing to actually do differently. Care is not a process. It does not tell someone what to look at, in what order, or what counts as done.

The opposite failure is just as common. You build a long checklist on your own, hand it to the employee, and call the conversation finished. The employee did not help design it, so they do not fully understand which step matters most, and a checklist with fifteen items buries the one check that would have caught this specific error. Both failures share the same root cause. You are treating this as a conversation about the employee's attitude rather than a conversation about a missing step in the work itself.

How to Prepare

Before you sit down with the employee, get your facts straight. Know exactly what went wrong, when it went wrong, and what it cost, in time, money, or the relationship with whoever received the bad work. Do not walk in with a theory about why it happened. You do not know yet whether the employee skipped a step, misread a source, or inherited a process that was already broken. State the fact of the error and let the employee describe what happened before you draw any conclusion about the cause. The approach behind Record an Employee's Words Without Adopting Their Conclusion applies here as much as it does to any other fact finding conversation. Write down what the employee tells you in their own words, then test whether it matches the timeline you already have, instead of filing their explanation under a label like careless or rushed.

Also prepare to hear that part of the problem sits with you. Maybe you handed off the task late, or the source data changes on a schedule nobody documented, or you never told the team which version of a file counts as current. A manager who cannot hear that kind of feedback without getting defensive gets a watered down version of the truth every time after that. The same discipline that helps you Receive Critical Feedback About Your Own Manager Behavior applies directly here, since asking an employee to help design a fix only works if they believe you will actually consider changes on your own end too.

What to Say

Omar pulls Lena aside after he corrects a supplier update that went out with two delivery dates pulled from an old tracker. He says, "The update went out with dates that changed last Tuesday, and I spent an hour fixing it with procurement before the vendor called asking which date was real. Walk me through where the review stopped."

Lena says she checked the narrative and the totals, but she trusted the spreadsheet she had open first, the one she always uses for this update, without checking whether procurement had refreshed it that week.

Omar says, "That explains it. So what would catch that before the next update goes out?"

Lena proposes two checks. She will confirm the tracker file carries a current timestamp before she starts drafting, and she will compare every delivery date in the draft against the procurement list line by line instead of skimming the narrative for anything that looks off.

Omar says, "Good. Put both of those in the handoff note, the timestamp check and the line by line comparison, so I can see they happened before the update reaches the vendor."

This exchange works for a few reasons. Omar names the specific cost of the error instead of a general complaint. He asks a direct question about where the review stopped instead of asking why Lena made a mistake. He lets Lena propose the fix instead of handing her one, which means she understands why each check matters and is more likely to actually run it under deadline pressure. And he asks for evidence, the handoff note, so the check becomes something he can see rather than a verbal promise he has to take on faith.

Mistakes to Avoid

Do not let the conversation turn into a performance review. This is about one preventable error and the process around it, not a summary of the employee's overall output. If a pattern of unrelated problems exists, handle that separately and say so directly instead of folding it into this conversation.

Do not design the check alone and announce it afterward. A rule you hand down gets followed loosely. A rule the employee built gets followed because they understand the reason behind it.

Do not accept a fix that is really just a restated version of be more careful. A useful check names a specific thing to look at, a specific comparison to make, or a specific question to ask when something looks off. If the employee proposes something vague, ask them to make it concrete before you end the conversation.

Do not skip the follow up. Agreeing on a check and never looking at it again teaches the employee that the check does not really matter. Set a specific point where you will review the evidence, and say plainly what happens if the same error shows up anyway.

How to Practice and Score It

This conversation is easy to get wrong live, because the instinct to lecture is strongest right after you have just spent an hour cleaning up someone else's mistake. Rehearsing it first helps you catch that instinct before it shows up in front of the employee. DealSpeak's HR and Leadership practice conversations let you run this exact scenario against an AI counterpart that plays a defensive or a cooperative employee, so you can test whether your opening line invites a real answer or shuts one down.

Score your own attempt against a short set of questions. Did you name the specific error and its cost without generalizing to the employee's character. Did you ask an open question about the process before offering your own theory. Did the employee leave the conversation owning at least one concrete check, described in their own words rather than yours. Did you agree on a piece of evidence you will actually look at, and a date you will look at it.

Run the conversation again if the answer to any of those is no. The version where you talk less and ask more is almost always the one that produces a check the employee actually uses.

Preventable rework rarely repeats because people are careless. It repeats because nobody replaced the missing step with a real one. Fix the step, agree on the evidence, and check back on the date you promised.