How to Give Clear Feedback on Work That Needs Revision

Point to the work that needs to change, explain why it matters, and agree on how you’ll know the revision is ready. Start with what you can both see, read, or verify.

Describe what you noticed

When a handoff checklist leaves out a step, name the omission and explain what happens downstream.

“The checklist skips the refund approval. Support can’t tell who signs off, so could you add the owner and the escalation step?”

Agree on a target and a checkpoint

Say which part matters most and give the person a chance to raise constraints or propose a better solution.

“The approval step is the priority. Could you send a draft by Wednesday afternoon so we can test it together?”

Handle a disagreement about the work

If they say the original brief called for something else, look at the brief together. Agree on the change before assigning it as a correction.

“Let’s look at the version we both used. If the requirement changed, I’ll update the brief before you revise the checklist.”

What to do next

Follow up by checking the same criteria you agreed on. If the work meets them, name the change that solved the problem.

Related reading: Respond to a negative performance review

Illustrated example for How to Give Clear Feedback on Work That Needs Revision
LEXICA Discussion

Join the Discussion

Sign in with your Google account to leave a comment under this article.

Comment with Google Use your Google/Gmail account through Blogger's native comment system.

Comments