Danielle Ralston
MBA · MSW · ADHD-CCSP · PhD(c) · Master ADHD Coach · 50+ Coaching Certifications · AuDHD · Founder of ND Hive
Quick Answer
Someone gives you a small note on your work. “Can you tweak this part?” And your whole body drops. Your face goes hot. Your stomach knots. Before you have read the rest of the sentence, a story is already writing itself: they think I am bad at this, they regret hiring me, I always mess this up. By the time you respond, you are responding to the story, not the note.
That is not weakness, and it is not you being dramatic. That is Rejection Sensitive Dysphoria firing a pain spike before your thinking brain has caught up.
The pain spike and the actual message are two different things, and they arrive at different times. The spike is a body event. It hits in the first few seconds and it feels like the whole truth. The message is information. It is usually smaller, more specific, and more survivable than the spike makes it feel. The skill is not to stop the spike. It is to let the spike pass before you decide what the message means.
This page is not about what RSD is. We cover that elsewhere. This is about the exact moment feedback lands at work or in your community: how to ride out the spike without acting on it, how to find the real message underneath, and how to repair if you reacted before you could catch it.
Why Feedback Hits So Much Harder Than It Should
You have been here. A manager says “we need to talk” and you spend the next two hours rehearsing your own firing. A teammate edits your draft and you read every change as a verdict on your competence. Someone in a community space disagrees with you and you go quiet for a week, certain you have ruined the relationship. The feedback was ordinary. Your reaction was not, and you know it, which adds a second layer of shame on top of the first.
Here is what is actually happening. For many ADHD, autistic, and AuDHD brains, the nervous system treats a piece of criticism the way it would treat a physical threat. A neutral note about your spreadsheet and a genuine danger can light up the same alarm. The reaction is fast, it is physical, and it arrives before thought. This is the pattern we call the Threat Misfire Loop: your threat-detection system pattern-matches an ordinary tone shift or correction to every past experience of being criticized, shamed, or rejected, and it reacts at full volume.
So the problem at work is not that you cannot take feedback. The problem is that the feedback and the pain arrive together, fused, and the pain is louder. You hear “fix this paragraph” and what registers in your body is “you are failing.” The information and the threat alarm hit at the same instant, and the alarm wins.
This is the part nobody told you. You are not too sensitive to be a professional, or too fragile for community. You are running a system that delivers feedback and a threat response in the same package. The work is learning to unfuse them. To let the body event happen, recognize it for what it is, and wait for it to pass before you read the actual message. Almost everything that goes wrong with feedback and RSD goes wrong in the gap between the spike and the response, when you act on the alarm instead of the information.
The Frame: The Spike Is a Body Event, Not a Message
Here is the reframe that changes how feedback lands.
When criticism arrives, two separate things happen, and learning to tell them apart is the whole skill. There is the spike, and there is the message.
The spike is the body event. Per the Threat Misfire Loop, it runs in stages, and it runs fast. A trigger lands. Your nervous system reads it as a threat. Your body reacts: the dropped stomach, the hot face, the held breath. Then a meaning spiral takes over: “they are mad, I am the problem, I always do this.” The spike feels like truth because your body is fully convinced. But a body reaction is not evidence. It is an alarm, and alarms misfire.
The message is the information underneath. It is almost always smaller than the spike. “Move this section up.” “I needed that by Tuesday.” “I disagreed with your point.” The message is workable. It is specific. It does not actually say “you are worthless” or “everyone here regrets you.” The spike said that. The message just asked for a change.
You cannot reason your way out of a spike while it is firing. That is the trap in the standard advice, which tells you to “challenge the thought” or “ask if they are really mad.” By the time you are at the thinking stage, your body has already fired and your reaction is already loading. You cannot argue with a body event that already happened. You can only learn to recognize it sooner and wait it out.
So the move is not to stop the spike. The spike is going to come. The move is to name the spike as a spike, let it move through your body, and refuse to respond to the feedback until it has passed. The message will still be there in twenty minutes. It will be clearer then, because you will be reading information instead of fighting an alarm. The spike is real. The story it tells you is not reliable. You are allowed to feel the spike all the way through and still wait to decide what the feedback means.
You are not overreacting. You are reacting on time to a threat alarm that fired early. The skill is letting the alarm finish before you answer the door.
What to Do When Feedback Lands: In the Moment, and After
None of this asks you to feel less. The spike is going to spike. These steps are about what you do with the gap between the spike and your response, so the alarm stops running the show. Pick one or two to start. You do not need all of them at once.
1. Name the spike the second it hits
The first move is the smallest and the most powerful. When you feel the drop, say to yourself, silently, “that is the spike.” Not “I am being attacked.” Not “I am failing.” Just “that is the spike, and it will pass.”
Naming it creates a half-second of distance between the body reaction and the meaning spiral. That half-second is often the whole intervention. You are telling your brain: this is a known nervous system event, not new evidence about my worth. The spike does not get a vote on what the feedback means. It just gets to happen.
2. Buy time before you respond to anything
This is the rule that protects you most. Do not reply while the spike is firing. Not to the email, not to the comment, not in the meeting if you can help it. Almost all the damage RSD does to your work relationships happens in the response you fire off in the first ten minutes.
If it is written, give yourself a flat rule: no replies to feedback for one hour, longer if you can. Draft your reaction in a notes app where nobody can see it, then delete it. If it is live, you are allowed to say “thank you, let me think about that and come back to you.” That sentence is professional, it is complete, and it buys you the time the spike needs to pass. You are not avoiding the feedback. You are waiting until you can read it as information.
3. Do the body work, because the loop runs through your body
The spike is not a thought you can think your way out of. It lives in your chest, your stomach, your breath. So you regulate the body, not the argument. Stand up and walk for five minutes. Drink a glass of water slowly. Put your feet flat on the floor and take three long exhales, slower on the way out than the way in.
This is not a relaxation tip. It is the actual intervention, because somatic regulation reaches a body event in a way cognitive reframing cannot. You are letting the alarm finish. When the body settles, the meaning spiral loses its fuel, and the feedback gets quieter and smaller, closer to its real size.
4. Find the message underneath, on paper
Once the spike has passed, go back to the feedback and do one thing: write down the literal words that were actually said. Not the story your brain wrote. The actual sentence. “Can you move this section up.” That is the message.
Then ask: what is the specific, doable thing being requested? Almost always it is smaller than the spike claimed. The spike said “they think you are incompetent.” The words said “move this section.” Put the two side by side on paper and the gap is the RSD. Respond to the words. Leave the story behind.
5. Repair if you reacted before you could catch it
Sometimes the spike wins. You snap, or over-explain, or go cold, or fire off the defensive email before you remember any of this. That is not a failure of character. It is a fast alarm beating a slow skill, and the skill is still being built.
Repair is short and clean. You do not need to grovel or explain RSD to your boss. A simple “I reacted faster than I meant to yesterday. I have thought about your feedback and here is what I will change” does the entire job. It is honest, it is professional, and it closes the loop. Most people respect a clean repair far more than they noticed the original reaction. You are allowed to be a person who reacts and then comes back.
6. Tend the aftermath shame before it feeds the next one
The last stage of the loop is the second wave: “why did I react like that, I always do this, they must think I am a mess.” This aftermath shame is not harmless. It is what loads the next spike, because now you walk into the next piece of feedback already braced and already ashamed.
So name the aftermath too. You survived a nervous system event. You did not fail a test of your worth. Treating it that way, on purpose, breaks the feedback loop that makes the next spike worse. The kinder you are to yourself in the aftermath, the smaller the next spike gets.
None of these are about caring less or toughening up. They are about putting a gap between the alarm and your answer, so the message gets through and the spike does not get to write your reply.
What This Looked Like for One Member
A member came to me convinced she was about to lose a job she was actually good at. Every time her manager left a comment on her work, she said, she “fell apart for a day.” She had started avoiding the shared documents entirely, because opening one and seeing a note felt like opening a verdict. Her work was strong. Her reaction to feedback on it was eating her alive.
Nothing about her was the problem. She was reading a body event as a message, every single time, and acting on the body event before the message could land.
So we built her a protocol. The second she saw a comment, she named it: “that is the spike.” Then a hard rule, no replies for one hour, no exceptions. In that hour she walked, or she drafted her furious reaction in a private note and deleted it. After the hour, she wrote down the literal words of the comment next to the story her brain had told her. Every time, the words were small. “Add a header here.” “Can we discuss the timeline.” The story was enormous. The words were a Tuesday.
The change was not that the spike stopped. It still came. The change was that it stopped running her job. She started replying to the words instead of the story, the next day instead of the same minute. The last time we talked, she had stopped dreading the shared documents. Not because feedback stopped hurting. Because she finally had a gap between the hurt and the reply, and the gap was where her real, capable self got to answer.
Your Next Step
You are not too sensitive for your job or your community. You are running a nervous system that delivers a threat alarm and a piece of feedback in the same package, with the alarm turned up loud. That is not a character flaw. It is a wiring pattern, and it is one you can learn to work with.
You do not have to fix this tonight. The next time feedback lands and your stomach drops, try one thing: name it. “That is the spike.” Then wait an hour before you respond to anything. That is the whole first step.
And you do not have to practice it alone, which is the part that quietly matters most. The ND nervous system was built to regulate in connection, not in isolation. At ND Hive we have live body doubling all week and a community full of people who know exactly what the feedback spike feels like, where you can talk through a hard note before you fire off a reply you will regret. Borrowed steadiness is often the difference between reacting and responding.
Come sit with us. Bring the piece of feedback that is still living rent-free in your head.