NeurodivergentW
Individual storyrsd·September 25, 2026

RSD at Work: Marketing Manager Case Study & Recovery

A 36-year-old Marketing Manager

A marketing manager's Friday-afternoon Slack message becomes a weekend of rewriting, dread, and pre-emptive apology — plus the Spiral Loop tools that finally shortened it.

rejection sensitivityrsd at workadhd maskingworkplace burnoutpeople pleasing at workperformance feedbackneurodivergent workplace

Illustrative composite story: This is an illustrative composite story synthesized from aggregated Workplace Spiral Quiz data. Names and identifying details have been changed.

Workplace Spiral dimensions

rsd20%
burnout20%
shutdown20%

Challenge

A 36-year-old marketing manager at a mid-sized B2B software company owned campaign strategy for a team of four, and spent the days before every review cycle bracing for a verdict. A vague Slack message from a director on a Friday afternoon would set off a familiar loop: rewriting finished work, scanning old conversations for evidence of failure, and arriving Monday already exhausted. The work looked excellent from the outside; the cost of producing it was invisible.

Solution

Using the Spiral Loop Framework, they started interrupting the cycle at the naming stage: writing down the trigger, separating what was actually said from what they had added to it, and delaying any response to ambiguous feedback by 24 hours. Free tools from neurodivergentworkplace.com — including the Workplace Spiral Quiz and the worksheets in the tools library — gave them a feedback fact-check page, a short holding-response script, and a boundary script to practice out loud. A direct ask to their director for written, specific feedback changed the input itself, and a Friday rule against taking on new commitments protected the edges of the week. None of it is a cure; it is scaffolding, and it tends to work better alongside professional support.

Outcomes

Spiral recovery time
Shortened from most of a weekend to a few hours, and often within a working day
↓ improved
Boundary-setting with new requests
Began declining or renegotiating low-priority work instead of absorbing it silently
↑ improved
Spiral episodes from ambiguous feedback
Noticeably fewer, as a 24-hour rule and a feedback fact-check replaced pre-emptive rewriting
↓ improved

“I used to read the same two-line message fifteen times looking for the part where I'd already failed. Now I write down what it actually says, wait a day, and answer that instead of the version I invented.”

An anonymous Workplace Spiral Quiz participant
Marketing Manager

The Slack Message That Started the Spiral

The message was eleven words long: Hey — got a minute to talk about the Q3 campaign deck before Monday? It arrived at 4:47 on a Friday, from a director who was, as far as anyone could tell, in a good mood. The marketing manager reading it — 36, three years into leading a team of four at a mid-sized B2B software company — felt their chest tighten before they finished the sentence.

By Friday night they had opened the deck and rewritten the opening slide four times. By Saturday they had reconstructed the entire week: the joke that landed flat in standup, the slide the director had paused on for two extra seconds, the fact that someone else had been copied on a thread they weren't. By Sunday evening the deck was on version eleven and the dread had settled in like weather.

Monday's meeting lasted six minutes. The director wanted one stat moved to the front and asked whether the team could pull the launch forward a week. There had been no criticism. There had never been any criticism. That was the part that stung most — not the feedback, but the proof that a whole weekend had been spent responding to a conversation that never happened.

Recognizing the Pattern

Searching for language for this, they found the Workplace Spiral Quiz at neurodivergentworkplace.com/workplace-spiral-quiz. The result came back dominated by Rejection Sensitive Dysphoria, with burnout and shutdown trailing as quieter echoes — the shape often described as the RSD Overachiever. The quiz is a reflection tool, not a diagnostic instrument, but the description was uncomfortably recognizable: scanning for tone, saying yes to every request, treating usefulness as the only safe position in a room.

The RSD half was obvious in hindsight. Ambiguous written feedback — anything that did not arrive with clear, warm, specific approval — got run through a catastrophizing filter. A one-line Slack message from a stakeholder could occupy an entire commute. The overachiever half was quieter. They had become the person who volunteered first, delivered early, and never said a meeting time did not work. It read as excellence from the outside and felt like standing in a hallway waiting for a door to open.

Burnout showed up as the bill for all of it. Shutdown showed up in small moments — the inbox left unopened, the performance review left unwritten, the meeting spent nodding while a sentence refused to form. The pattern was not three separate problems. It was one loop with three exits.

What Actually Helped: A Loop Small Enough to Use on a Friday

What helped was not a revelation. It was a framework small enough to reach for at 4:47 on a Friday. The Spiral Loop Framework breaks the pattern into four moves: name the trigger, name the loop, interrupt it, and recover on purpose. Written down, it sounds almost too simple. In practice it handed the manager a sequence to follow when their body had already decided the weekend was over.

The first tool they used was a plain feedback fact-check page from the free tools library at /tools. Two columns: what the person actually said, and what I added. The Friday message went in the left column as an eleven-word request for a meeting. The right column filled up with years of accumulated evidence that they were about to be found out. Seeing both columns side by side did not dissolve the feeling, but it made the feeling negotiable.

The second tool was a 24-hour rule for ambiguous feedback: no rewriting, no pre-emptive apologies, no long explanatory replies the same day. Instead, a short holding response. Something close to: Thanks for flagging this. Can you point me to the one thing you would change first? That sentence did two jobs — it bought time and it replaced a guess about the feedback with the actual feedback.

The third tool was a boundary script, practiced out loud before it was ever needed: I can take that on, but it means pushing the newsletter back. Which matters more this week? The first few times it came out shaky and over-explained. By the sixth time, it came out in one breath. None of this is medical advice. It is the kind of scaffolding that tends to be worth building with a therapist, coach, or clinician when the pattern is long-standing or painful enough that self-help tools alone are not enough.

Where Things Stand Now

Nothing about this resolved cleanly. The manager still notices the tight chest when a message begins with Hey —. The difference is what happens next. Ambiguous written feedback that used to consume a weekend now usually resolves within a working day, and often within a couple of hours, because there is a sequence to follow instead of a spiral to fall into.

They also changed conditions rather than only coping with them. In a 1:1, they asked their director for feedback in writing where possible, with a specific ask attached, and started each 1:1 by reading the agenda aloud so that silence in the meeting could not be read as disapproval. They began declining or renegotiating work they would previously have absorbed in silence, and noticed the team's workload conversations get more honest as a result.

The quiz score is not the point, and no tool is a cure. The point is that the loop became visible, and visible loops are easier to interrupt than invisible ones. A shorter spiral is not a small thing when you have been losing weekends to them.

Published: September 25, 2026

This content is for informational purposes only and is not medical advice, diagnosis, or treatment.

Your Cart (0)

Your cart is empty