Why "Communicate Better" Isn't Actually Feedback

Quick Bridge: If you've ever handed someone the note "show more ownership" or "be more strategic" and watched nothing change afterward, the note wasn't the problem, the category was. This post breaks down why category-level feedback fails, what a research-backed model for fixing it actually looks like, and the exact language that turns a label into something a person can act on.


A performance review, once a year, with the line "needs to communicate better" written under a manager's name. The person reading it nods in the meeting. Then they go back to their desk with no idea what changed, because nothing in that sentence told them.

This happens constantly, and it's rarely because the manager didn't care enough to be specific. It's because a category is faster to write than a full sentence, and most performance conversations are built for speed, not clarity.

I have written that same lazy sentence myself, more than once, before I built a better habit around it. The habit is not complicated. It just takes more thought than the two seconds a category label takes.

The Real Cost of Vague Performance Feedback

Generic feedback is one of the most common complaints employees have about performance reviews, and for good reason. A label like "communicate better" or "show more ownership" describes a feeling the manager has, not a behavior the employee can point to.

The person on the receiving end is left to guess. Which meeting? Which message? More detail, less detail, faster, slower?

Guess wrong, and the same feedback shows up again next quarter, except now it comes with a little more frustration attached, because from the manager's side, "I already told them this."

That's the trap. The manager believes they gave feedback. The employee never got anything they could actually use, and the two of them walk out of the same meeting remembering two different conversations.

Why Category Labels Feel Like Feedback But Aren't

A category sounds like an assessment of who someone is. "You're not strategic enough" reads as a statement about identity, not action, and there is no version of "identity feedback" a person can practically act on Monday morning.

A behavior is different. It's a thing that happened, at a specific time, with specific words. It can be repeated or it can be avoided, and that distinction, repeatable versus not, is the entire line between feedback that changes something and feedback that just gets nodded at.

Gallup has found that only 16% of employees say their most recent conversation with a manager felt extremely meaningful, even though 80% of employees who received meaningful feedback in the past week report being fully engaged at work (Gallup, "A Great Manager's Most Important Habit"). That disconnect between feedback happening and feedback landing is not a frequency problem. Most managers are already having these conversations. The conversations just aren't specific enough to be the thing Gallup is measuring.

How to Turn Vague Feedback Into Something Actionable

The Center for Creative Leadership has research-backed language for exactly this disconnect, called Situation-Behavior-Impact, or SBI (CCL, "Use SBI to Inquire About Intent"). It breaks feedback into three parts: the situation, so the context is specific and not a vague pattern; the observable behavior, not your interpretation of someone's intent; and the impact that behavior had, on the meeting, the project, or another person.

I add a fourth piece when I use this with the managers I coach: what would have been better. Without it, the person knows what went wrong but not what to do instead, and a person left holding only the "what went wrong" part still doesn't have anything to act on.

Put together: "Yesterday in the team meeting, you challenged Sam in a combative way, saying X. That caused the meeting to go off topic and people stopped contributing. It would have landed better if you'd said Y instead, which keeps the disagreement without shutting the room down."

Four sentences. Every one of them does something the category label never could.

CCL also suggests an optional extension, adding a second I for Intent, asking the person what they meant before you assume what the impact tells you about their motive. That extra step matters most when the behavior is ambiguous. If someone missed a deadline, the situation, behavior, and impact are usually clear enough on their own, but if someone's tone in a meeting reads as combative, asking about intent before you land on impact keeps the conversation from turning into an accusation.

What Vague Feedback Costs You Over Time

The cost isn't just one missed conversation. It compounds. A manager who gives category feedback and sees no change usually reaches for the same category again, just delivered with more edge in their voice. "I've told you this before" becomes the subtext, even though what was actually said before was too vague to have told the person anything.

Eventually this becomes a performance improvement plan, or it becomes the manager quietly deciding the person has a ceiling. Neither of those outcomes started with a real behavior problem. They started with feedback that never specified what the behavior problem was.

There's also a cost the manager pays directly. Vague feedback protects you from having to be wrong about the details, because a category can't really be argued with. But that same vagueness means you never build the muscle of noticing the actual moment while it's fresh. Managers who default to specific feedback aren't spending more time on it in total, they're just spending it earlier, while the moment is still easy to describe.

Common Vague Feedback Phrases and What They Actually Mean

A short translation guide for three categories that show up constantly in reviews and 1-on-1s:

"Communicate better" usually means one of two things: information arrived too late for someone to act on it, or information arrived without the point stated first. Name which one it was, in one sentence, with the actual meeting or message it happened in.

"Be more strategic" usually means the person proposed a solution without connecting it to the business reason behind it. Point to the specific proposal where that happened and what question went unanswered.

"Show more ownership" usually means the person surfaced a problem and then waited, instead of driving it to resolution themselves. Name the specific moment the waiting started and what taking it further would have looked like.

"Be more of a team player" usually means the person optimized for their own scope in a moment where the group needed something from them, a review, a favor, a piece of context, and they didn't offer it unprompted. Name the specific ask that went unanswered or unnoticed.

In every case, the category is standing in for a sentence the manager hasn't written yet. Writing that sentence is the entire fix.

Your Next Move

Pick the next piece of feedback on your list that you'd currently describe with a single word, communication, strategy, ownership. Before you say anything, write the situation, the specific behavior, the impact, and what better looks like, as four separate sentences. Then say those four sentences instead of the word.


What's a piece of feedback sitting on your list right now that you've been describing as a category instead of a behavior?


You're great at the work. Let's make you impossible to ignore.

If you are looking for help giving feedback that actually changes behavior instead of getting nodded at and forgotten, consider reaching out. https://www.jessestaffordcoaching.com

Comments

Popular posts from this blog

You Should Mix up Your 1-on-1 Locations

How to Get Manager Approval for Engineering Side Projects at Work: A Framework for Getting Buy-in for Technical Improvements

What Does a Good 1-on-1 Look Like?