Resources · Unwritten Workplace Rules
Feedback Etiquette Decoded
By Debra Solomon,
Last updated
In thirty years of coaching, the comment I hear most often is some version of this: "I didn't realize that was feedback until it came back around." That's the real trouble with workplace feedback. Handling a hard note is one thing. Spotting that a note was even given is the part that trips people up, because most feedback at work doesn't arrive the way the handbook says it will. It comes wrapped in softeners, buried in a passing comment, pitched at a tone the speaker assumes you'll read on your own. If you tend to take words at face value, you can miss it entirely. On this page I'll show you how feedback actually gets delivered, how to tell a real signal from conversation filler, how to ask for specifics without sounding defensive, and how to take a hard note without losing the rest of your week to it.
How feedback actually works
Most feedback at work runs on a quiet assumption: that you'll read the delivery, not just the words. When a manager says "it might be worth taking another pass at the intro," she usually means "the intro doesn't work, please redo it." The soft phrasing is packaging. The instruction sits underneath it. A lot of neurotypical people strip the packaging off without thinking and hear the instruction. A lot of neurodivergent people hear the actual sentence, a mild and optional-sounding suggestion, file it away, and then get blindsided when the same thing comes back louder a month later.
That gap has nothing to do with how smart you are or how hard you work. It comes down to how the signal gets read. Offices tend to deliver hard messages sideways, partly to be polite and partly to let you save face. The unspoken deal is that you'll meet them halfway and inflate the message back up to its real size. When you don't, your manager walks away sure she was clear, and you walk away sure nothing important was said. Neither of you notices the wire got crossed.
You don't have to become a mind reader to close that gap. You just need the handful of patterns that mark real feedback, plus one habit for the moments you're unsure: when you can't tell how big a comment was, ask. The rest of this page is those patterns and those asks. In thirty years of coaching, I've watched this one skill, reading the size of a comment, prevent more performance-review surprises than anything else I teach.
Handling a hard note is one thing. Spotting that a note was even given is the part that trips people up.
Real feedback vs. filler
Not everything that sounds like feedback is feedback. People think out loud, float half-formed reactions, and make conversational noise that means nothing at all. Treat every offhand remark as a directive and you'll wear yourself out and start to look reactive. The skill is telling the signal from the noise, and a few reliable markers help.
Real feedback tends to be specific, repeated, or tied to a consequence. If your manager names a particular thing ("the deck had three typos"), raises the same point more than once, or links it to something that matters ("the client noticed the typos"), treat it as real and act on it. Filler tends to be vague, one-off, and free of consequence: "interesting," "we'll see," "good stuff" said while glancing at a phone. Sometimes a comment starts as filler and turns real on the second mention. The repeat is the tell. When someone brings a thing up twice, they've decided it matters enough to risk sounding repetitive, and for most managers that's a high bar.
Tone and timing carry information too, and they're the hardest part to read. A note delivered in a scheduled one-on-one usually outweighs one tossed over a shoulder on the way out of the room, because the person chose a place to put it. A note that comes with a pause around it ("So. About the report.") usually weighs more than one that slides by in the middle of a sentence. You won't catch every nuance live, and you don't need to. You need to catch enough to flag the ones worth a follow-up, then use the follow-up to confirm what you couldn't read in the moment.
Here's a filter I give people. At the end of each week, look back at the comments you got and sort them into two piles: "named, repeated, or had a consequence," and "vague and one-off." Act on the first pile. Let the second go unless it shows up again. It feels mechanical because it is. You're building on purpose the sorting that other people do without noticing, and on-purpose beats anxious every time. The point is simple: stop letting the things that matter slip past while the noise eats your attention.
When it's not about that
Some feedback is about the thing it names. Some is about something else, and the named thing is just the safest example the person could reach for. "Your emails are too long" sometimes means your emails are too long. Other times it means "I'm not sure you're prioritizing well, and the length is the evidence I can point to." Telling those two apart changes what you do next. Fix the surface complaint while missing the real one and the feedback just comes back later wearing a different outfit.
The tell is whether fixing the literal complaint would actually settle the person. If you shortened every email and your manager still seemed uneasy, the emails were never really it. Coded feedback usually points at a theme: trust, judgment, reliability, fit. A cluster of small complaints (emails too long, meetings run over, follow-ups slow) is rarely three separate problems. It's usually one read, something like "I'm not sure this is under control," coming out through whatever concrete examples were handy. Treat the cluster as one signal, not a to-do list.
This is the category where guessing costs you the most, because the price of guessing wrong is high and the coded delivery was built to avoid being said out loud. So don't guess. Surface it, gently. Something like "I want to make sure I fix the right thing. Is this about the emails specifically, or is there a bigger pattern you're seeing?" gives the person room to say the real thing. Some will take it. Some won't, and that tells you the trust isn't there yet, which is worth knowing too. Either way you've done the one move that beats decoding from the outside: you asked the person who actually knows. Knowing which moment calls for which move is the same context skill I cover in meeting dynamics decoded.
Asking for specifics without sounding defensive
"Can you give me a specific example?" is the most useful sentence you have in a feedback conversation, and it's the one people swallow most often for fear of sounding defensive. So let me reframe it for you. Asking for an example is exactly what someone who takes the feedback seriously does. Defensiveness argues with the note. A request for specifics accepts the note and asks for the detail you need to act on it. To the person across the table, those two sound completely different, as long as you get the framing right.
The framing that works is collaborative. "I want to get this right. Can you point me to a moment where the tone came across wrong?" lands as engagement. "When have I ever done that?" lands as a challenge, even when you mean the exact same question. The difference is whether your question assumes the feedback is valid and just needs detail, or questions whether it's valid at all. Lead with the assumption that they're right and you need the specifics to fix it. You can always weigh it for yourself later, in private, once you have the example in hand.
Vague feedback is genuinely hard to act on, and you're allowed to need more before you can. "Be more strategic," "work on your communication," "show more leadership": none of those are actionable as written. The trap is treating the vague version as a verdict you have to accept in silence. Think of it as an opening line with its example missing. The real feedback is the specific underneath, and your job is to draw it out with a calm, curious question. If you ask twice and still get nothing concrete, that's information too. Feedback nobody can make specific often says more about the manager's discomfort than your performance. I go deeper on this in the performance-reviews pillar, where the stakes are higher and the script matters more.
Receiving without spiraling
For a lot of neurodivergent professionals, the hardest part of feedback comes after you've understood it. It's the first ninety seconds, when the whole day suddenly feels like it's about to collapse. Criticism can land harder and faster than the situation calls for, and the wave of "I've ruined everything" shows up before the rational read can catch up. This is common, it's real, and it says nothing bad about you. What it does mean is that the live moment and the processing afterward have to be handled separately. Try to do both at once and you get the spiral.
Buy yourself time without disagreeing. "Thank you, I want to sit with that for a second," or "That's helpful, let me think it through and come back to you." You're not required to respond to feedback in real time, and the urge to defend or explain or fix it right now almost always makes things worse while you're flooded.
Acknowledge it, take the note, and end the live part there. Nothing you say mid-wave will be as good as what you'll say once it passes. Pausing here reads as composure, and composure is the professional move.
The processing happens later, on purpose, and it has a shape. First, separate the feedback from the feeling. Write down what was actually said, in plain words, with the catastrophe your brain added stripped off. "The report had errors" is the feedback. "I'm bad at my job and everyone knows it" is the feeling. Note that second part, then set it aside. Second, sort what's true and useful from what's true but minor and what doesn't fit. You can act on an accurate note without swallowing the inflated story that rode in with it. Third, if a real repair or reply is needed, do it the next day in writing, when you're clear. None of this asks you to feel nothing. The goal is to keep the feeling out of the driver's seat while you decide what to do. And it's exactly the kind of recurring, situation-specific thing that gets easier when you have people to compare notes with. That's what the Spectrum Roadmap Community is built for.
The short version
- Before you react, work out how big the comment actually was. If you can't tell, ask.
- Treat feedback as real when it's specific, repeated, or tied to a consequence. The repeat is the strongest tell.
- When a complaint feels coded, surface it gently instead of guessing at what it really means.
- Ask for a specific example. Framed right, it reads as engagement, not defensiveness.
- In the moment, buy time without disagreeing. Do the real processing later, on paper, when you're clear.
Frequently asked questions
How do I know if feedback is serious or just a passing comment?
Look for three markers: specificity, repetition, and consequence. Serious feedback usually names a particular thing, comes up more than once, or gets tied to something that matters ("the client noticed"). Passing comments are vague, one-off, and free of consequence. The most reliable tell is repetition. When someone brings a thing up twice, they've decided it's worth the risk of sounding repetitive, which means it matters. When you honestly can't tell, a short follow-up costs you nothing: "Was that something you'd like me to change, or just a thought?"
Is it okay to ask for a specific example when I get feedback?
Yes, and it usually helps you more than it costs you. Asking for an example shows you take the feedback seriously and plan to act on it. The whole thing rides on framing. "I want to get this right, can you point me to a moment where this happened?" reads as engagement. "When have I ever done that?" reads as an argument, even if you mean the same thing. Lead with the assumption that the feedback is valid and you just need the detail to act.
How do I keep critical feedback from ruining my whole day?
Separate the live moment from the processing. In the moment, do one thing: buy time without disagreeing. "Thank you, let me sit with that and come back to you." You're not required to respond on the spot, and most defenses made while you're flooded make things worse. Then process later, on purpose: write down what was actually said in plain words, peel off the catastrophe your brain added, sort what's true and useful, and handle any real response the next day in writing. The pause between landing and responding is the whole skill.
What if the feedback is genuinely vague and I can't act on it?
Treat vague feedback like "be more strategic" or "work on your communication" as an opening line with its example missing, not a verdict you have to accept. Ask for the specific, calmly, and twice if you need to: "Can you point me to a recent moment where I could have been more strategic?" If you still get nothing concrete, that's information too. Feedback nobody can make specific often says more about the giver's discomfort than your work. Don't act on a fog. Ask for the shape underneath it.
How is everyday feedback different from a performance review?
Everyday feedback is real-time, low-ceremony, and easy to misread, because it shows up in the flow of work: a comment in a hallway, a line in a Slack message, a softened note in a one-on-one. Performance reviews are scheduled, written down, and consequential, with their own prep and scripts. This page covers the day-to-day version: reading the signal, asking for specifics, and not spiraling. The formal-review version, with its prep, handling criticism on the record, and negotiating goals you can actually hit, lives in the performance-reviews pillar.
Sources I trust and point people to
The links below pair well with this page. For the legal floor under all of this (accommodations, disclosure, your rights), see the resources at the bottom of the workplace disclosure guide.
- Understood.org, Workplace. Broader workplace guidance for neurodivergent adults, with especially useful coverage of how rejection sensitivity and feedback intersect for ADHD.
- Job Accommodation Network (JAN). Accommodation ideas for situations where feedback delivery itself is a barrier, such as requesting written feedback in advance of a verbal conversation.
This page is one of five under the broader unwritten-rules guide. Its closest companion is meeting dynamics decoded, since most feedback gets delivered in or around meetings. For the disclosure side of all this, when and whether to tell your employer you're neurodivergent, see the disclosure decision framework.