Feedback Etiquette for Neurodivergent Professionals

Four modes day-to-day feedback shows up in, each with its own etiquette and its own right response. Reading the mode is more important than reading the literal text.

1. Course-correct

Small, in the moment, low-stakes. A colleague is flagging one thing they'd like done differently next time. Signal: short message, no framing, often no preface. "For next time, attach the deck instead of pasting it." "Quick note — try not to @-channel for non-urgent updates."

The right response is brief acknowledgment plus actually doing it next time. "Got it, will do." Three words. Then the next instance, you do the thing differently. The change is the response; nothing else is required. What neurodivergent professionals often misread it as: a pattern observation. The literal text of a course-correct can sound severe if you weight it against your standards for review feedback. It usually isn't.

2. Pattern observation

Your manager or a peer has noticed a recurring thing. Signal: longer message or a 1:1 mention, framing like "I've noticed..." or "a few times now..." or a specific count. "I've noticed you've been signing off before our team's standup the last two weeks — is something going on with the timing?"

The right response is acknowledging the pattern, asking one clarifying question if needed, and proposing the change. "Yeah, I've been moving heads-down time to the morning and standup's catching the edge of it. I'll shift back to starting the day after standup instead." This is a real behavior change but specific to the pattern named. What neurodivergent professionals often misread it as: a personal failing requiring a full restructuring of their schedule. The pattern named is the pattern to address — usually nothing more.

3. Pre-formal

The thing that, if you don't fix it, will show up in your written review. Signal: more deliberate framing, sometimes a calendar slot, often the phrase "I want to flag" or "want to make sure we talk about." "I want to flag that the project hand-off last month is going to come up in calibration — let's talk through it."

The right response is taking it seriously, asking what the review-version of this conversation will say, and starting the 30-day evidence trail (see decoding vague communication feedback for the mechanic). Pre-formal feedback is a gift; your manager is telling you what the review will say while you still have time to change it. What neurodivergent professionals often misread it as: a course-correct, because the delivery can feel casual. The phrase "I want to flag" almost always upgrades a piece of feedback from course-correct to pre-formal; treat the phrase as a tier-shift signal.

4. Relational

Feedback that's really about the relationship, not about the work. Signal: vague content, awkward delivery, often after a 1:1 ends or in a sidebar context. "Hey — just wanted to check in. Are we good?" "Things have felt a little off lately, I just wanted to name that."

The right response is naming the relational layer back, briefly. "Thanks for raising that. I think we are — I've been heads-down on [project], which has made our 1:1s feel more transactional than usual. Let me put 15 minutes of unstructured time on next week's." What neurodivergent professionals often misread it as: a feedback request needing a project status update. Relational feedback is asking for connection, not for content. Provide the connection.

The four modes look superficially similar but reward different responses. Misreading the mode is one of the most common ways day-to-day feedback ends up costing more than it should.

Giving feedback to a manager or a peer runs on different etiquette than receiving it. Three principles cover most of the territory.

Ask permission, even briefly. Unrequested upward or sideways feedback often reads as criticism even when it isn't. The opener that works: "Can I share something I noticed?" or "Do you want a thought on the [thing]?" The permission ask takes three seconds and produces a meaningful difference in how the feedback lands. Most colleagues say yes; the rare no is itself useful information about whether the moment is right.

Name the behavior, not the person. "The way the last update was framed left me unsure what action was being asked for" is feedback about a specific artifact. "You frame your updates in a confusing way" is feedback about the colleague. The first invites a response; the second invites a defense. The behavior-framed version is also more accurate — most feedback is about a specific moment that could be different, not about the person being different.

Propose, don't prescribe. "What if we tried sending the recap as a short bullet list?" gives the colleague room to engage with the suggestion or counter it. "You should send the recap as a short bullet list" closes the conversation. Proposing also signals you're contributing to a shared problem, not assigning a task to someone who didn't ask you to.

For neurodivergent professionals who tend to be precise, the trap when giving feedback is over-precision. The right level of specificity for upward or sideways feedback is one step less precise than what you'd say to yourself. Where you'd say "the third paragraph of the update buried the ask and made it ambiguous whether action was needed," to a peer say "the ask got a little buried in the third paragraph — could it move up?" Same observation, less prescription, more workable for the receiver.

The asymmetry to know: peers and managers can give you precise feedback; you don't have the same latitude going up. That isn't fair, but it's the etiquette. Working within it produces better outcomes than fighting it does.

Frequently asked questions

How do I tell the difference between a course-correct and a pattern observation in the moment?

Three tells. Length: course-corrects are short, often one sentence; pattern observations are longer because they have to set up the pattern. Framing: course-corrects use "for next time" or no preface at all; pattern observations use "I've noticed" or "a few times now" or a specific count. Instance count: a course-correct references one instance, a pattern observation references multiple. When the tells conflict — a long message about one instance, or a short message with "I've noticed" — treat it as the higher-stakes version. The cost of under-responding to pattern observation is much higher than the cost of over-responding to a course-correct.

What if I get the same feedback from multiple people?

That's pattern observation by definition, regardless of how any individual instance was delivered. Three different people giving you the same small note about your meeting prep, each one delivered as a course-correct, is not three course-corrects. It's a pattern that's reached enough of the team that it's worth treating structurally. The response is the pattern-observation response: name the pattern you're hearing, ask one clarifying question if needed, propose the change. The fact that no single person framed it as a pattern doesn't change what it is.

How do I push back on feedback I disagree with?

Ask for the specific example first, then decide whether to push back. The disagreement-without-the-example move loses; it reads as defensive even when the disagreement is correct. The disagreement-with-the-example move can win because you're disagreeing with a specific moment, not with your colleague's judgment. The phrasing: "Got it — can you walk me through the moment you have in mind? I want to make sure I'm thinking about the same situation." Once you have the specific moment, you can either accept the read or surface context that changes it. Pushing back on a specific moment is a normal workplace conversation. Pushing back on a general impression rarely is.

Should I follow up in writing after a verbal feedback conversation?

For pre-formal and relational feedback, yes — a short written acknowledgment the same day. For course-corrects, no; the written follow-up is itself an overcorrect that makes a small note feel bigger than the colleague intended. For pattern observations, it depends on the relationship. With a manager, yes — a three-line note that names the pattern back and proposes the change. With a peer, usually no — the conversation itself is the close, and a written note can feel like you're escalating something they wanted handled lightly.

What if I receive feedback I think is identity-based (e.g. about being "too literal" or "too detail-oriented")?

Separate the question of whether the feedback is about identity from the question of whether the underlying behavior has a workplace cost. Sometimes both are true — being literal in a moment where the team needed implicit reading can have a real cost, even when the framing as "too literal" feels identity-based. The remedy in that case is to address the behavior cost, not the identity claim. When the feedback is clearly identity-based without any workplace cost behind it — "you're too detail-oriented" delivered about work that's correctly detail-oriented — that's different territory. Authoritative resources on workplace bias are linked at the bottom of this page; the move that helps in the moment is asking what specifically the feedback wants you to do differently, which often surfaces whether there's a behavior change being requested or whether the framing is the whole feedback.

How does this differ for remote teams?

Channel signals matter more on remote teams because there's no in-person pull-aside option. The pre-formal mode is more often delivered in a calendar invite for remote teams — a 30-minute slot with no agenda is a more reliable signal of pre-formal feedback on a remote team than on an in-person one. Relational feedback is harder to read on remote teams because the casual delivery channels (hallway, lunch, end-of-meeting lingering) don't exist. When a remote colleague sets up a 1:1 specifically with you, treat the meeting itself as the signal — usually relational, sometimes pre-formal, rarely just course-correct.