Decoding Vague Communication Feedback

Six concrete meanings. When your manager rates your communication as a development area, they almost always mean at least one of these — and sometimes more than one. The diagnostic move is figuring out which.

1. Visibility — "I don't know what you're working on"

Your work is good; the manager just doesn't see enough of it. The rating reflects the gap between what you're producing and what's visible to the person doing the rating. This is the most common meaning, especially for neurodivergent professionals who tend to focus deeply on the work itself and surface only when it's done. The fix is not better speaking. It's weekly written updates — a Friday three-line summary of what you worked on, what's blocked, what's coming next week, sent to your manager and ideally to your skip-level. The work doesn't change; the visibility does.

2. Status updates — "I find out about delays too late"

You waited until you had a complete answer when the manager wanted the partial one earlier. Specifically, you didn't surface the in-progress state of work where decisions or risks were involved. The fix is surfacing partial state — a Slack message at the moment of any delay or scope change, not at the moment of resolution. The principle: your manager would rather know about the problem at 60% certainty than learn about the resolution at 100% certainty. Most neurodivergent professionals over-index on resolution because the in-progress message feels incomplete; the in-progress message is the point.

3. Stakeholder management — "Other people complained to me about working with you"

There's a peer or partner-team relationship that's frayed, and the manager is filing it under "communication" rather than naming the relationship directly. Often the relationship was frayed by something specific — a disagreement that didn't get resolved cleanly, a meeting that went sideways, a piece of work that crossed a team boundary the wrong way. The fix is identifying the specific relationship and repairing it directly. The question that surfaces this meaning is asking your manager whether the feedback came from them or from someone else; the answer usually identifies the relationship in question.

4. Meeting presence — "You don't say enough in meetings" or "you say too much"

Meeting participation calibration is off for the manager's context. This is its own category because the response is different — it's not about written communication, channel choice, or stakeholder repair. It's about reading the meeting type and matching your participation pattern to it. The patterns that work are covered in meeting dynamics decoded; this page handles the diagnostic, that page handles the response.

5. Tone — "Your emails come across as blunt / cold / abrupt"

Written-channel tone calibration. Almost always specifically about email or Slack, almost never about in-person communication. The fix is one of two things, depending on diagnosis: either the writing genuinely is reading as colder than you intend (in which case small structural changes — a one-line warm opener, a closing acknowledgment — usually solve it), or the writing is fine and a specific recipient finds direct writing uncomfortable (in which case the fix is recipient-specific, not global). Asking for the specific email or message that prompted the feedback is the move that distinguishes the two.

6. Influence — "You should advocate for your ideas more" or "you push back too hard"

The manager wants a specific influence style and hasn't articulated it. The two versions of this — "more" and "too hard" — sound opposite but produce the same diagnostic move. Ask for an example of someone the manager thinks does this well, then ask what specifically that person does that you don't. The answer is usually a pattern your manager admires but can't explain in the abstract. Watching it in practice is more useful than hearing the description; the conversation that surfaces it is more useful than the rating itself.

Often more than one of these is in play at once. The clarifying question handles that case too.

The response trap is hearing "your communication needs work" and explaining why your communication was actually fine in the situations you remember. This loses, even when the explanation is correct.

The reason it loses: your manager isn't asking for a defense. They're signaling something they want changed. The defense reads as "I disagree with the rating," which puts your manager in the position of either backing down or doubling down. Most managers double down — the rating is already written, and the defense often shifts a soft rating into a harder one.

The pattern that works has four steps. Acknowledge: "Okay — I want to take this seriously." Ask for specifics: the clarifying question from the previous section. Name the gap: once you have the example, say what you read it as in the moment versus what your manager read it as. ("I was treating that as a quick async handoff; I'm hearing you read it as needing more synchronous context.") Propose the structural change: a specific behavior change with a timeline. ("Starting next week, I'll add a 10-minute live walk-through for any handoff that touches the deploy pipeline.")

The structure works because it shows you noticed, you took responsibility for the gap (not for being wrong, but for the gap between your read and theirs), and you proposed a specific change rather than a vague commitment to "improve." Specific behavior changes are easier to track and easier for your manager to give you credit for in the next review.

The reframe is harder for neurodivergent professionals than it sounds. The literal-first reading of "work on your communication" makes "but my communication was fine" feel like the obviously correct response — because in many of the specific moments you remember, your communication probably was fine. The reframe is treating the feedback as a signal about what your manager wants more or less of, rather than as a claim about the past you need to litigate. Past performance is fixed; the next cycle is the only variable. Respond to the variable.

Frequently asked questions

What if my manager won't give a specific example?

This is itself diagnostic. Either the rating is pattern-based without any specific incidents attached to it, or the manager doesn't want to put the example in writing. Both are worth knowing. If the rating is pattern-based, the move that works is proposing the structural change anyway: "Even without a specific example, I want to take this seriously — I'm going to send weekly written updates starting Friday and ask you to flag anything that's still not landing." This converts an ungrounded rating into a measurable change for next cycle. If the manager doesn't want to put the example in writing, that's a separate signal — usually about their own discomfort with the conversation rather than about your work.

Is "you're too direct" the same as "your communication needs work"?

Usually a subset — most often a version of tone (meaning #5) or influence style (meaning #6). The difference is that "too direct" is already specific enough to act on, where "work on your communication" is not. When the feedback names the dimension, you can skip the clarifying-question step and go straight to asking for the moments. "Can you point me to two recent examples where my directness landed wrong?" Same diagnostic move, applied to a more specific input.

Should I disclose during this conversation?

Usually not as the first response. Disclosure as a reaction to a critical-feedback moment puts the disclosure in the same memory frame as the criticism, which is rarely what you want. If the feedback genuinely connects to an accommodation need, the better order is: respond to the feedback on its own terms first, run the clarifying-question and 30-day evidence-trail moves, then schedule a separate disclosure conversation a week or two later when the review pressure isn't in the room. The full framework for the disclosure decision is in our disclosure decision framework guide.

What if I think the feedback is biased rather than fair?

Separate the question of whether the rating is wrong from the question of whether the bias is actionable. The 30-day evidence trail moves the rating regardless of the bias question — building a record of changed behavior is useful whether your manager's read was fair or unfair. The bias question, if you decide to pursue it, has its own set of remedies: HR conversations, external advisors, formal complaint processes. Those pathways live outside the rating-defense move and benefit from being kept separate. Authoritative resources on workplace bias and discrimination are linked at the bottom of this page.

How do I bring this up if the feedback came in a 1:1 and not a formal review?

Easier, not harder. 1:1 feedback is in the ongoing rhythm where you can ask the clarifying question in the same conversation. The phrasing barely changes: "Got it — can you give me a specific example from the last 30 days where that didn't work, so I'm working on the right thing?" The same diagnostic move, delivered in real time. The advantage of 1:1 feedback is that the example is usually fresh in your manager's mind and the conversation hasn't been compressed into a written rating yet.

What if I'm worried asking the question makes me look defensive?

It doesn't, if framed as fact-finding rather than rating-defense. The specific phrasing — "Can you give me a specific example from the last 30 days where my communication didn't work?" — has three properties that prevent the defensive read. It accepts the premise (you're asking which example, not whether there is one), it scopes the question to a manageable window (30 days, not the whole year), and it ends with "didn't work" rather than "was a problem," which is workflow-framed rather than judgment-framed. If you're worried about delivery, practice it out loud before the meeting. Three rehearsals is usually enough.