Why managers give vague feedback — and three fixes

"You're doing great. Maybe just be a bit more strategic." Every manager has said some version of this, and every person who's received it has walked away with nothing — because there's nothing in it. No moment, no behavior, no next step. The person nods, says thanks, and goes back to their desk to guess at what "more strategic" means, which usually results in either no change at all or a change in the wrong direction. What makes this worth examining rather than just criticizing is that vague feedback almost never comes from laziness or indifference. It comes from three specific pressures acting on the manager in the moment — and once you can name which one is operating, the fix is surprisingly mechanical.

Fix one: you don't actually have the specifics

The most common reason feedback comes out vague is the least flattering to admit: you don't have a concrete example, because you didn't see one. You have an impression — a residue accumulated from second-hand comments, a general vibe about someone's work, a sense that something's slightly off. Impressions can't be stated specifically, because there's no specific thing in them. So they come out as adjectives: scattered, not strategic, needs more polish.

This gets worse the more removed you are from the work. A manager with eight reports and a calendar full of meetings genuinely does not observe most of what their team does. So the honest diagnosis is often: I don't have the specifics because I wasn't there.

The fix isn't better phrasing — it's better inputs. You can't articulate what you haven't observed, so go get observations before you give feedback. Read the actual pull request or document rather than relying on a summary. Sit in on the meeting the concern came from. Ask one clarifying question of the person who raised it: "what specifically happened that made it feel disorganized?" Once you have a real moment, specificity is almost automatic — it's much harder to be vague about something you actually watched happen. And if after looking you find there's no concrete example, that's a genuinely useful result: it may mean the concern was someone else's impression, not a pattern worth raising at all.

Fix two: vagueness is conflict-avoidance in disguise

The second pressure is emotional. Specific feedback is harder to say because it's harder to argue with — and being hard to argue with is exactly what makes it feel confrontational. "You interrupted Priya three times in Thursday's review" is a factual claim about a real event; it can be discussed, and it might produce a reaction. "Just be mindful of how you come across in meetings" is soft enough that nobody has to feel anything. So the manager reaches for the vaguer version, and it feels kind.

It isn't kind. It's comfort for the giver, purchased with the receiver's ability to improve. The person can't act on "be mindful of how you come across," so they either ignore it or spend weeks anxiously auditing everything they do. The vagueness that spared an awkward thirty seconds costs them months of clarity. This is the same instinct that produces the feedback sandwich — softening delivery until the message is gone.

The fix is to separate the specificity from the severity. These are independent dials, and vague-feedback-givers usually think they're the same one. You can be extremely specific and extremely warm at the same time: "In Thursday's review you cut Priya off three times — I don't think you noticed, and I know you were under time pressure. Worth watching, because she's stopped volunteering things." That's precise and kind. Being specific doesn't mean being harsh; it means giving the person something real to work with. If the honest version is genuinely difficult, that's a separate skill — delivering hard feedback without crushing someone.

Fix three: you're out of time and default to a summary

The third pressure is structural. Feedback gets squeezed into the last two minutes of a 1:1, or delivered in a hallway, or written at the end of a long review form. Specificity takes a little time — you have to recall the moment, describe it, and hear the response. When there isn't time, the brain compresses, and compression produces exactly the smoothed-over generality that carries no information: overall good, work on communication.

The fix is to change when feedback happens, not how hard you try to be specific. Give it close to the moment, when the details are still available to both of you, and reserve actual room for it rather than tacking it onto the end of something else — which is why the structure of your 1:1 matters more than your vocabulary. Small and frequent beats comprehensive and rare; a two-sentence observation the day after a meeting is worth more than a paragraph three months later, and it takes less effort to produce.

The vague version vs the specific one

Diagnosing which pressure you're under

1. 1

   Before you speak, try to name the moment

   If you can't name a specific instance, you have an impression rather than an observation — that's pressure one. Go get the specifics before you say anything, or accept there may be nothing real to raise.
2. 2

   Notice if you're softening as you talk

   If you had a specific sentence in your head and it came out fuzzy, that's pressure two: conflict-avoidance. Separate the dials — keep the precision, add the warmth, and say the concrete thing.
3. 3

   Check whether you left yourself any time

   If feedback keeps landing in the final ninety seconds, that's pressure three, and no amount of effort will fix it in the moment. Move feedback earlier and closer to the event instead.
4. 4

   Test it against the actionability bar

   Before delivering, ask: could they describe what to do differently tomorrow based on this? If not, it isn't feedback yet — it's an impression, and it needs a moment and a behavior attached. Research from the Center for Creative Leadership on behavioral feedback keeps landing here: specificity is what makes feedback usable at all.

Where Mirorly fits

Notice that all three pressures — thin observation, conflict-avoidance, no time — apply just as hard to the feedback you receive, and worse: the people best placed to tell you how you're doing report to you, so they're under all three pressures plus the power gap. Which means the vague feedback you're trying to stop giving is almost certainly the only kind you're getting. "You're doing great, keep it up" is the sound of your own team hitting exactly these constraints. Mirorly is the structural fix on the receiving side: specific behavioral questions your team answers about how you actually work, aggregated with an anonymity threshold so honesty is safe, and your self-view placed next to theirs so the gaps are visible. The core leadership behaviours template gives you the specificity that a hallway conversation never will — and reading feedback that precise about yourself is the fastest way to learn what precision is worth giving.

Common questions

The one-line summary

Vague feedback comes from three nameable pressures — you didn't observe the specifics, you softened to avoid conflict, or you ran out of time and compressed — and each has a mechanical fix: go get real observations before speaking, treat precision and warmth as independent dials rather than a tradeoff, and move feedback closer to the moment with actual room reserved for it; the test is whether the person could say what to do differently tomorrow.