How to Tell Your Team Their Work Isn’t Good Enough

Mar 10, 2015
5 Min Read

Every manager knows the feeling: Someone turns in a piece of work you assigned, and when you look at it, it’s not the quality you wanted. How do you tell a staff member that work isn’t good enough and needs to be better?

If this isn’t a regular occurrence and is just a one-time happening, you should simply be direct about how your vision for the piece differs from what you received. Treat it as a communication error more than a work quality issue – because if it’s not part of a pattern, that’s the likely explanation anyway. For instance, you might say:

  • “I think this is a good start, but I’d like to tighten up the writing. Right now we’re taking five pages to say what  I think we could say in two. And I think we need to address the broader strategy implications more explicitly. Could you take another run at it? The piece you did last month on X is a great model to use again.”
  • “I’m realizing I didn’t fully communicate what was in my head on this. While this would work for an internal audience, we’ll need to be able to show this to clients and funders. That means it needs to be more ____.”
If you’re regularly seeing an attitude of “it’s good enough” on your staff (or in a particular team member), address it directly. You might say something like this:
  • “I want to talk about the bar we’re aiming to meet in our work. One reason we’re known for being great at what we do is that we work hard to ensure our stuff is better quality than anything else out there. That often means we need to take extra time with it to ___. (Insert whatever’s relevant to your context here, like: test ideas/edit flawlessly/make it easy to understand/align with our branding.) Sometimes work that would be good enough in another company won’t be good enough for us; we really try to stretch for greatness.”

If you can follow this up by pointing to examples of work that did meet that bar, that will usually help people understand what they should be shooting for.

You might also lay out different bars for different types of work: “For emails that are just being circulated internally, it’s fine to write informally and it’s not a big deal if you don’t proofread perfectly. But for anything going to the public, we need to be rigorous about writing and proofreading; that’s where mistakes matter and reflect badly on us.”

The important thing in all of these cases is to be direct about how the work is missing the mark and what the bar you’re going for looks like, keeping the focus on the work itself and not the person. (That last part is the difference between “this piece needs to do a better job of communicating with sophisticated audiences” and “your writing is making us sound amateur.”)

Recomended Posts