Resources · Unwritten Workplace Rules
Feedback Etiquette Decoded
Last updated
Most workplace feedback isn't delivered the way the handbook implies. It arrives wrapped in softeners, buried in passing comments, and calibrated to a tone the speaker assumes you'll read automatically. For neurodivergent professionals who take words at face value, the hard part isn't handling criticism. It's knowing which comment was criticism in the first place. This guide decodes 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 in hard feedback without the spiral that eats the rest of your week.
How feedback actually works
Corporate feedback runs on an unwritten assumption: that the person receiving it will decode the delivery, not just the words. The manager who says "it might be worth taking another pass at the intro" usually means "the intro doesn't work, please rewrite it." The words are a softener. The instruction is underneath. Most neurotypical professionals strip the softener off automatically and hear the instruction. Many neurodivergent professionals hear the literal sentence (a mild suggestion, optional), move on, and then get confused when the same issue comes back harder later.
This isn't a failure of intelligence or effort. It's a difference in how the signal gets read. The corporate norm is to deliver hard messages indirectly, partly out of politeness and partly to give the receiver room to save face. The norm assumes you'll meet it halfway by inflating the message back up to its real size. When you don't, the gap is invisible to you and obvious to your manager, who walks away thinking they were clear and you weren't listening.
The fix isn't to become a mind reader. It's to learn the small set of patterns that mark real feedback, and to build one habit that closes the gap without requiring you to guess: when you're not sure how big a comment was, ask. The rest of this guide is the patterns and the asks. In 30 years of coaching neurodivergent professionals, Debra Solomon has found that this one skill, decoding the size of a comment, causes more avoidable performance-review surprises than any other.
Real feedback vs. filler
Not everything that sounds like feedback is feedback. People narrate as they think, float half-formed reactions, and make conversational noise that means nothing. Treating every offhand remark as a directive is exhausting and makes you look reactive. The skill is telling the signal from the noise. A few reliable markers separate real feedback from filler.
Real feedback tends to be specific, repeated, or tied to a consequence. If your manager names a particular thing ("the deck had three typos"), brings the same point up more than once, or connects it to something that matters ("the client noticed the typos"), it's real, so act on it. Filler tends to be vague, one-off, and consequence-free: "interesting," "we'll see," "good stuff" said while looking at a phone. A comment can also start as filler and become real on the second mention. The repeat is the tell. When something comes up twice, the person has decided it matters enough to risk seeming repetitive, which for most managers is a high bar.
Tone and timing carry information too, and they're the hardest part to read. Feedback delivered in a scheduled 1:1 generally outranks feedback tossed over a shoulder on the way out of a room, because the person chose a container for it. Feedback that comes with a pause before or after it ("So... about the report.") is usually weightier than feedback that flows in the middle of a sentence. You don't have to catch every nuance live. You have to catch enough to flag the ones worth a follow-up, and then use the follow-up to confirm what you couldn't read in the moment.
A practical filter: at the end of each week, look back at the comments you got and sort them into "named, repeated, or had a consequence" versus "vague and one-off." Act on the first pile. Let the second pile go unless it shows up again. This sounds mechanical because it is. You're building, deliberately, the sorting that other people do without noticing, and deliberate beats anxious. The goal isn't to treat everything as urgent. It's to stop missing the things that are.
When it's not about that
Some feedback is about the thing it names. Some feedback is about something else entirely, 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. Sometimes it means "I don't trust that you've prioritized correctly, and the length is the evidence I can point to." Decoding which one you're dealing with changes what you do next, and fixing the surface complaint while missing the real one is how people end up baffled when the feedback returns in a different costume.
The tell is whether fixing the literal complaint would actually satisfy the person. If you shortened every email and your manager still seemed uneasy, the emails were never the issue. Coded feedback usually points at a theme: trust, judgment, reliability, or fit. A cluster of small complaints (emails too long, meetings run over, follow-ups slow) is rarely about emails, meetings, and follow-ups as separate problems. It's usually one underlying read ("I'm not sure things are under control") expressed through whatever concrete examples were handy. Treat the cluster as one signal, not three tasks.
This is the category where guessing is most dangerous, because the cost of guessing wrong is high and the coded delivery is specifically designed to avoid being said out loud. So don't guess. Surface it, gently. A question like "I want to make sure I'm fixing the right thing. Is this about the emails specifically, or is there a bigger pattern you're seeing?" gives the person permission to say the real thing. Some will take it. Some won't, and that itself tells you the relationship isn't there yet, which is information worth having. Either way you've done the one move that beats decoding from the outside: you asked the person who knows. Reading which moment calls for which move is the same context skill covered in meeting dynamics decoded.
Asking for specifics without sounding defensive
"Can you give me a specific example?" is the single most useful sentence in feedback, and the one neurodivergent professionals most often swallow for fear of sounding defensive. Here's the reframe: asking for an example is what someone who takes the feedback seriously does. Defensiveness argues with the feedback. A request for specifics accepts it and asks for the detail needed to act. Those read completely differently to the person across the table, as long as you get the framing right.
The framing that works is collaborative, not adversarial. "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 same thing. The difference is whether your question assumes the feedback is valid and seeks detail (good) or questions whether the feedback is valid at all (reads as a fight). Lead with the assumption that they're right and you just need the specifics to fix it. You can always re-evaluate later, privately, once you have the example in hand.
Vague feedback is genuinely unfair to act on, and you're allowed to need more. "Be more strategic," "work on your communication," "show more leadership": none of these are actionable as stated. The mistake is treating the vague version as a verdict you have to accept silently. It's an opening line. The real feedback is the specific example underneath it, and your job is to extract that example with a calm, curious question. If you get nothing concrete even after asking twice, that's worth noting too: feedback no one can make specific is often more about the manager's discomfort than your performance. We go deeper on the vague-feedback problem in the performance-reviews pillar, where the stakes are higher and the script matters more.
Receiving without spiraling
The hardest part of feedback for many neurodivergent professionals isn't understanding it. It's surviving the first ninety seconds after it lands without the rest of the day collapsing. Critical feedback can hit harder and faster than the situation warrants, and the wave of "I've ruined everything" can arrive before the rational read catches up. This is common, it's real, and it doesn't mean anything is wrong with you. It does mean the in-the-moment response and the after-the-fact processing have to be handled separately, because trying to do both at once is what produces the spiral.
Buy 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 obligated to respond to feedback in real time, and the instinct to defend, explain, or fix it immediately almost always makes things worse while you're flooded.
Acknowledge, take the note, and end the live portion. Nothing you say while your nervous system is mid-wave will be as good as what you'll say once it passes. The pause is not weakness; it's 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, stripped of the catastrophe your brain added. "The report had errors" is the feedback. "I'm bad at my job and everyone knows it" is the feeling. Note it, then set it aside. Second, decide what's true and useful, what's true but minor, and what doesn't fit; you can act on accurate feedback without accepting the inflated story that rode in with it. Third, if a real repair or response is needed, do it the next day in writing, when you're clear. This isn't about feeling nothing. It's about not letting the feeling make decisions on your behalf, and it's exactly the kind of recurring, situation-specific pattern that gets easier when you have people to compare notes with. That's what the Spectrum Roadmap Community is built for.
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 consequence-free. The single most reliable tell is repetition: when something comes up twice, the person has decided it's worth the risk of seeming repetitive, which means it matters. When you genuinely can't tell, a short follow-up ("Was that something you'd like me to change, or just a thought?") costs you nothing and removes the guesswork.
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 signals that you take the feedback seriously and intend to act on it. The key is framing: "I want to get this right, can you point me to a moment where this happened?" reads as engagement, while "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 detail to act on it.
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 in real time, and most defenses made while flooded make things worse. Then process later, on purpose: write down what was actually said in plain words, separate the feedback from the catastrophe your brain added, decide 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?
Vague feedback like "be more strategic" or "work on your communication" isn't a verdict. It's an opening line that's missing its example. Ask for the specific, calmly and twice if needed: "Can you point me to a recent moment where I could have been more strategic?" If you still get nothing concrete after asking, that's information too: feedback no one can make specific is often more about the giver's discomfort than your performance. 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's delivered in the flow of work: a comment in a hallway, a line in a Slack message, a softened note in a 1:1. Performance reviews are scheduled, documented, and consequential, with their own preparation rituals and scripts. This guide 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, lives in the performance-reviews pillar, which goes deeper on the higher-stakes conversation.
External sources we cite and trust
The links below pair well with this guide. For the legal floor underneath workplace navigation (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 sub-pillars 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 corporate navigation, when and whether to tell your employer you're neurodivergent, see the disclosure decision framework.