RSD at Work: Feedback, Performance Reviews, and Panic (Scripts + Systems)
Work is one of the most intense RSD environments because it mixes:
🧠 evaluation
👥 hierarchy
📌 ambiguity
⏱️ urgency
🧾 consequences (money, stability, reputation)
🎭 masking (“be professional” even when your body is flooding)
So RSD at work often doesn’t look like “big feelings.”
It looks like:
🌪️ overexplaining
🧊 shutting down
🪨 procrastinating
🔥 defensiveness
😶 silence in meetings
📉 sudden performance dips
🧠 rumination for days over one comment
This article is a practical, adult-focused guide to:
🧠 understand why work triggers RSD so hard
🛠️ reduce RSD activation (before it happens)
💬 respond well in the moment (even if you’re flooded)
🧾 prepare for performance reviews without spiraling
🤝 repair and protect relationships at work
📌 build systems so feedback becomes information, not danger
🧠 Why work is an RSD amplifier
RSD sensitivity increases when cues signal:
🧠 “I’m being judged.”
🫀 “I’m losing status.”
🔥 “My safety depends on getting this right.”
Work provides those cues constantly—often subtly.
🧩 The 6 biggest amplifiers at work
🧑💼 1) Power difference
🧑💼 someone else has decision power over your future
🫀 your nervous system notices
📊 2) Visibility
📊 your work is seen, compared, ranked, reviewed
🧠 visibility increases threat prediction
📌 3) Ambiguity
📌 tone in email
📌 “quick chat?” messages
📌 unclear expectations
🌪️ ambiguity is gasoline for RSD
⏱️ 4) Time pressure
⏱️ urgency reduces your processing time
🫀 and the body surges faster
🎭 5) Masking
🎭 you must look calm and competent while you’re flooded
🧠 masking increases the aftershock cost
🧾 6) High consequence stacking
🧾 bills, rent, career path
🔥 the stakes feel existential even when the comment was small
This explains why one mild correction can feel like a cliff.
🔍 What RSD at work typically looks like (adult patterns)
Work-RSD tends to show up in a handful of repeating patterns.
1) 🧠 The “interpretation spike”
📩 a short message appears
😐 tone feels flat
⏳ reply is delayed
🧠 your brain fills in: “They’re disappointed.”
2) 🔥 The “defensive competence burst”
🔥 you respond instantly
🧠 you overexplain details
📌 you try to prove you’re not wrong
😵💫 you later regret how intense it was
3) 🪨 The “freeze in meetings”
🪨 mind goes blank
😶 you can’t find words
🧠 you feel stupid
🌧️ you replay it afterward for hours
4) 🌫️ The “avoidance spiral”
🌫️ you delay the task that will be evaluated
🪨 initiation becomes impossible
🔥 deadline pressure rises
😵💫 you sprint last minute and crash
5) 🧾 The “perfectionist trap”
🧾 you rewrite everything five times
🧠 you can’t deliver until it’s perfect
🪫 you burn capacity and resent the task
🌪️ you still fear criticism
6) 🎭 The “professional mask + private collapse”
🎭 you look fine at work
🫀 you go home and crash
🌧️ you can’t talk
🎧 sensory tolerance collapses
🪨 inertia hits hard
These patterns are common across neurodivergent adults because they’re not “personality flaws.”
They’re nervous-system strategies trying to prevent rejection.
🧭 The 3 work-RSD hotspots (and why they’re brutal)
🧑💼 Hotspot 1: Performance reviews
Performance reviews combine:
🧠 evaluation + hierarchy + ambiguity + consequence
🔥 perfect RSD storm
💬 Hotspot 2: “Quick feedback” moments
Feedback delivered casually can feel worse than formal feedback because:
📌 it’s unexpected
😐 tone may be clipped
🫀 you don’t have time to regulate
👥 Hotspot 3: Meetings
Meetings are live social performance + live evaluation:
🎭 you’re perceived
🧠 you must respond in real time
📌 you can’t draft carefully
🔥 RSD is more likely to spike
🛠️ The Work-RSD Toolkit (3 layers)
Just like the main RSD article, work tools work best in layers:
🧠 before (systems and structure)
🌿 in the moment (scripts and downshift)
🧾 after (repair and meaning)
🧠 A) BEFORE: Build systems that reduce RSD frequency
This is the highest leverage part. Most people try to manage RSD only in the moment—when it’s already too late.
1) 📌 Make success criteria explicit (reduce ambiguity)
Ambiguity is one of the biggest triggers.
So you ask for clarity early.
💬 Clarity scripts
🧠 “What does ‘good’ look like for this?”
📌 “What are the top 1–2 priorities?”
⏱️ “What’s more important: speed or precision?”
🧾 “How will this be evaluated?”
🧩 If you worry you’ll sound needy
🤝 “So I can deliver what you want efficiently, can I confirm the priority?”
Clarity is not weakness. Clarity is performance protection.
2) 🧾 Request feedback structure (a professional accommodation-lite)
You don’t need to disclose anything. You can request structure as a productivity preference.
💬 Feedback format scripts
🧠 “I respond best to feedback when it’s prioritized—what’s the top thing to change?”
📝 “Could you share feedback in writing? I implement it faster that way.”
🤝 “Can we do feedback privately rather than in the group?”
🧩 If you want the “strength + improvement” structure
🌿 “It helps me if feedback includes what’s working plus the top improvement.”
That single ask can massively lower threat.
3) 📅 Pre-build “review season” protections
If you know performance review time is coming, treat it like a high-load week.
🧾 Review season protocol
🎧 reduce sensory load on review days
🧠 avoid scheduling other hard meetings that day
🧃 schedule a recovery block afterward
📝 prepare a “facts list” of your contributions
🤝 plan one safe person to debrief with
You’re not being dramatic. You’re being strategic.
4) 🧠 Build a “proof file” (anti-RSD memory)
RSD makes the brain selectively remember mistakes.
So you build an external memory that includes reality.
🗂️ Proof file ideas
📌 compliments or positive feedback screenshots
🧾 wins and completed projects
🧠 moments you solved something hard
🤝 “thank you” messages
📊 metrics that show impact
🧩 Why this helps
🧠 RSD narrows attention to threat
🧾 proof files widen the evidence base
It’s not ego. It’s nervous-system counterbalance.
5) 🧩 Reduce switching density (because switching lowers regulation)
RSD is more likely when your system is already taxed.
Switching density is often the hidden tax.
🛠️ Switching reducers
📵 notification windows (two blocks/day)
🧠 batch email/Slack responses
🧩 protect one deep-focus block
📌 cluster meetings when possible
📝 “next step note” before switching tasks
Lower switching density → higher emotional resilience.
6) 🤝 Build “micro-safety” with one colleague
Having one “safe enough” person at work reduces threat load.
🤝 Micro-safety options
🧠 someone you can ask “was that tone weird?”
🧾 someone who can clarify expectations
🌿 someone who can sanity-check feedback meaning
🫀 someone who helps you downshift after tense meetings
Work becomes less threatening when you’re not alone with interpretation.
🌿 B) IN THE MOMENT: Scripts for when you’re activated
These are designed for when your body is already surging.
Your goal is not eloquence.
Your goal is:
🌿 reduce damage
🧠 buy time
🤝 keep relationships intact
1) 🫀 The 10-second “name + pause” move
Before responding, do:
🫀 one slow exhale
🧠 “This is RSD activation.”
⏱️ pause for 2 seconds
That tiny pause prevents impulsive over-defense.
2) ⏱️ The delay scripts (your best weapon)
💬 In-person feedback
🧠 “Thank you—let me think for a moment.”
📝 “Can I reflect and follow up in writing?”
⏱️ “I want to respond carefully. Can I come back to you this afternoon?”
📩 Email/Slack feedback
🧠 “Thanks—received. I’ll review and reply by [time].”
📌 “Got it. I’ll incorporate this and share an updated version by [time].”
🧩 Why these work
🧠 they signal competence
⏱️ they buy regulation time
🤝 they prevent reactive tone
3) 🧾 The “prioritize the feedback” script
When feedback is vague, it triggers meaning inflation.
So you turn it into a ranked list.
💬 “Thanks—what’s the top priority change you want?”
💬 “If I only fix one thing, what matters most?”
💬 “Can you point to one example so I implement it correctly?”
This converts rejection into information.
4) 🧊 The “neutral acknowledgment” script (for public correction)
When corrected publicly, many people either:
🔥 fight (defend)
🪨 freeze (go silent)
A neutral script helps you stay intact:
💬 “Got it—thanks. I’ll adjust that.”
💬 “Thanks for catching that. I’ll revise.”
💬 “Understood. I’ll incorporate this.”
Then you can process privately later.
5) 🧠 The “clarify tone” script (when ambiguity is the trigger)
Sometimes you genuinely need clarity.
But do it cleanly and minimally.
💬 “Quick check—do you mean X or Y?”
💬 “Just to confirm: are you concerned, or is this a minor tweak?”
💬 “When you say ‘not ideal,’ what change would make it ideal?”
This keeps you out of mind-reading.
6) 🧱 The “stop overexplaining” guardrail
Overexplaining is a classic RSD behavior because it tries to buy safety through proof.
A simple guardrail:
🧠 keep it to two sentences
📌 then ask one question
⏱️ then pause
🧠 Two-sentence template
🧠 “Thanks for the feedback. I’ll adjust X and send an updated version by [time].”
📌 “Is there anything else you want prioritized?”
That’s it. Stop.
🧾 C) AFTER: Repair, reset, and prevent rumination
Once you’re out of the meeting or off the call, the aftershock begins.
This is where you protect your week.
1) 🧩 Facts vs meaning (the work version)
🧾 Facts: what was said
🌪️ Meaning: what my brain predicted
📌 Action: what I’ll do next
🧾 Example
🧾 Facts: “Revise the intro; too long.”
🌪️ Meaning: “They think I’m incompetent.”
📌 Action: “Shorten intro to 3 sentences.”
Action breaks rumination.
2) 🌿 The 20-minute recovery rule after feedback
Feedback drains you. Pretending it doesn’t drains you more.
So you schedule a small recovery block:
🎧 silence
🚶 short walk
🫧 bathroom break + cold water
🧺 pressure input
🪑 sit alone without being perceived
Your nervous system needs closure.
3) 🌧️ Shame hangover plan (work edition)
Shame often says:
🕳️ “You embarrassed yourself.”
🕳️ “You should quit.”
🕳️ “You’re not cut out for this.”
Instead, run a plan:
🧠 one compassionate sentence
🧾 one proof-file check
📌 one small corrective action
🎧 one sensory deposit
🧠 Compassion sentence options
🌿 “My body heard danger. That’s not my fault.”
🧠 “I can handle feedback and still be sensitive.”
🤝 “I can repair if needed.”
4) 🤝 Repair if your tone came out sharp
Work repairs should be short, clean, and specific.
💬 “I realized I sounded defensive earlier. Thanks for the feedback—I’ve adjusted X and appreciate you flagging it.”
That’s professional, mature, and disarming.
🧾 Performance Reviews: A full RSD-safe plan
This is the big one. So here’s a complete structure.
🧠 1) Before the review: preparation that reduces threat
📝 Prepare your impact list (10 minutes)
🧾 3 outcomes you delivered
🤝 2 ways you supported others
🛠️ 1 skill you improved
📌 1 challenge you handled
🌿 1 goal for next period
🧠 Request structure
📌 agenda in advance
📝 written notes if possible
🧾 success criteria clarification
🎧 Reduce sensory load
🎧 earplugs before entering office
💡 comfortable lighting setup if remote
🧺 grounding object in pocket
🧃 Schedule recovery
🌙 no heavy plans after
🚶 short walk scheduled
🪑 quiet time protected
🌿 2) During the review: scripts that keep you steady
🧠 Start with alignment
💬 “Thanks for meeting. I’d love to understand priorities for the next period and where you want me to focus most.”
📌 When criticism appears: ask for specificity
💬 “Can you share an example so I can implement it properly?”
🧾 When feedback feels vague: prioritize it
💬 “If I work on one thing first, what matters most?”
⏱️ When you feel flooded: buy time
💬 “I’m taking this seriously. Can I reflect and follow up in writing later today?”
🤝 When you need to protect your dignity
💬 “I appreciate direct feedback. It helps me most when it’s specific and prioritized.”
🧾 3) After the review: convert it into a plan (not a wound)
Within 24 hours:
🧾 write 3 bullet points: what they want
📌 write 3 bullet points: what you’ll do
⏱️ schedule one check-in
🧠 put one item into your system (calendar/task manager)
🌿 do one recovery deposit
This stops rumination from becoming your boss.
🧩 The “tone ambiguity” protocol (Slack/Teams survival)
A lot of work RSD comes from one thing:
📩 short messages with unclear tone
So instead of interpreting, you use a protocol.
📩 Step 1: Default to neutral
🧠 “I will assume neutral unless proven otherwise.”
📩 Step 2: Ask one clean clarifier (if needed)
💬 “Quick check—do you want me to change X or just note it?”
📩 Step 3: Delay if activated
⏱️ “I’ll reply in 20 minutes.”
📩 Step 4: Don’t reread repeatedly
📵 rereading = threat rehearsal
🧠 it intensifies the body response
A practical rule:
📵 read once, decide action, close the thread
🧠 The “meeting freeze” toolkit
If you freeze in meetings, it’s not incompetence. It’s nervous system + processing time.
🛠️ Tools that help immediately
📝 bring a notepad and write 3 keywords
🧠 prepare 1–2 “default phrases”
⏱️ buy time with a processing request
🤝 ask for questions in writing when possible
💬 Default phrases
🧠 “Let me think for a second.”
📌 “Can you repeat the question?”
📝 “I’d like to respond in writing so I’m accurate.”
🤝 “Here’s my initial thought—happy to follow up with details.”
🧩 After the meeting
🧾 send one short follow-up message
🧠 it repairs the “I sounded stupid” story
📌 it reinforces competence
🧾 The “fear of being wrong” trap (and how to loosen it)
Work-RSD often attaches to a belief:
🧠 “If I’m wrong, I’m unsafe.”
So you practice a controlled version of “being wrong” without collapse.
🧩 Micro-practice
🧠 ask one clarifying question you might fear is “stupid”
📝 send one draft earlier than perfect
🤝 request feedback on one small piece, not the whole project
🌿 Reframe
🌿 “Iterating is professional. Perfectionism is expensive.”
🪞 Reflection Questions (work-specific)
🪞 Which work trigger hits me hardest: performance reviews, public correction, Slack tone, or meetings?
🫀 What are my earliest body signs of RSD at work?
🧠 What do I tend to do: fight, flight, freeze, or appease?
📌 What’s one structure request that would reduce ambiguity for me?
💬 What are my three go-to scripts when activated?
🧾 What would I put in a proof file this week (one item)?
🌱 Closing: make work survivable without self-erasure
RSD at work doesn’t mean you’re unprofessional.
It means your nervous system treats evaluation as high stakes.
The goal isn’t to become numb.
It’s to become structured:
🧠 reduce ambiguity
🛠️ request feedback formats that protect you
💬 use scripts to buy time
🫀 downshift physiology
🧾 convert feedback into actions
🤝 repair quickly when needed
🌿 protect recovery so one comment doesn’t steal your whole week
📬 Get science-based mental health tips, and exclusive resources delivered to you weekly.
Subscribe to our newsletter today