RSD at Work: A Product Marketing Manager Case Study
A 39-year-old Product Marketing Manager
A product marketing manager whose rejection sensitivity turned a two-line Slack message into a week of overwork and dread — and the Spiral Loop Framework habits that shortened the recovery.
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
Challenge
A vague four-word message from a manager ('Can we chat tomorrow?') reliably launched a full internal emergency: catastrophe rehearsals, rewritten decks at 1 a.m., volunteered extra work, and pre-emptive apologies. The pattern was an RSD Overachiever loop — intense pain from perceived criticism, people-pleasing, and overworking to prove worth — with moderate burnout and low shutdown, so the person rarely collapsed but rarely rested either.
Solution
After finding the Workplace Spiral Quiz and recognizing a dominant RSD pattern, the person learned to map the loop using the Spiral Loop Framework: trigger, emotional surge, story, behavior, aftermath. They interrupted it with a 24-hour rule before replying to ambiguous feedback, one clarifying-question script, a spiral log kept in the free tools at neurodivergentworkplace.com/tools, and a small set of boundaries such as declining one non-urgent request per week and requesting written feedback instead of hallway comments. Progress was treated as shortened recovery time, not as a cure.
Outcomes
“I still get that drop in my stomach when a message is short and unexplained. The difference is that now I know it's a loop, not a verdict — and I can usually wait it out instead of working all night to fix something that was never broken.”
The Breaking Point
The message arrived on a Thursday afternoon and was four words long: 'Can we chat tomorrow?' It came from a manager who was, by every available signal, pleased with the quarter. There was no context, no agenda, no softening emoji. For most people that is a neutral calendar item. For this 39-year-old product marketing manager, it was the opening scene of a nine-hour internal emergency. By six in the evening the first version of the story had formed: the launch retro had gone badly, someone had complained, the positioning document was too long, the messaging was wrong. By nine, the story had a sequel — a performance conversation was coming, followed by a quiet exit. That night involved re-reading six weeks of Slack threads, hunting for the exact sentence that had caused all of it. It was never found, because it did not exist. Sunday-evening dread had become a familiar weekly companion, arriving even on weeks with nothing to dread.
How the Spiral Actually Ran
The loop followed a predictable shape. A short, unexplained message landed — the trigger. Within minutes came a physical surge: heat in the chest, tight jaw, a drop in the stomach. Then the story, always the least charitable version available. Then the behavior: a deck rewritten at one in the morning, two extra projects volunteered for, meeting notes offered before anyone asked, three apology messages sent for a mistake that had not happened. Then the aftermath — exhaustion, embarrassment, and a quiet resolve to work harder so it would never happen again, which is precisely what fed the next round. The 1:1 the next day lasted eleven minutes. The manager wanted to talk about a conference budget. The relief lasted about ninety seconds before it curdled into something sharper: shame at how much energy had just been spent on a conversation that never happened. That sequence — brief relief, then shame, then more overwork to prove worth — is what made the pattern so durable. The overwork was not ambition. It was insurance.
Recognizing the Pattern
The map arrived through a late-night search that ended at the Workplace Spiral Quiz on neurodivergentworkplace.com/workplace-spiral-quiz. The result described a dominant rejection-sensitivity pattern with moderate burnout and low shutdown — an RSD Overachiever loop. Reading it was less like a diagnosis and more like someone describing a room the person had been living in for years and had never named. The Spiral Loop Framework gave that room a floor plan: trigger, surge, story, behavior, aftermath. The insight was not that the feelings were wrong, but that the loop could be interrupted earlier than it usually was. Naming the stage out loud — 'this is the story stage, not the facts stage' — was the first intervention that worked even slightly. None of this is medical advice; it is an educational way of noticing a pattern, and anyone exploring whether ADHD is part of their picture should talk to a qualified clinician.
What Actually Helped
The changes were small, and most of them were scripts. Instead of answering an ambiguous message with a paragraph of self-defense, the person used one clarifying question: 'Thanks for flagging — which part would you like me to change first?' If the message was vague and it was after 6 p.m., a 24-hour rule applied: no replies, no rewrites, no apology drafts until morning. Twice a week that rule alone saved an entire night of work. The free tools at neurodivergentworkplace.com/tools supplied the rest. A spiral log tracked triggers, the story that followed, and how long the episode actually lasted — which turned out to be far shorter than it felt. A trigger inventory revealed that short messages from senior people, hallway feedback, and being left off a thread were reliable starters. A ten-minute walk before drafting any reply became non-negotiable, mostly because it worked. Boundaries were the hardest part and the least dramatic. The person began declining one non-urgent request most weeks, blocked thirty minutes after every 1:1 to decompress instead of returning straight to the inbox, and made one plain request of their manager: 'If something is time-sensitive, please say so in the message.' They also asked for feedback in writing where possible, not because written feedback hurt less, but because it was less ambiguous — and ambiguity was the fuel.
Where Things Stand Now
This is not a cure story. Vague messages still land hard, and there are still evenings when the chest tightens before the rational brain arrives. What changed is the length of the episode. Where a four-word Slack message once cost a week of overwork and a weekend of dread, it now costs an evening — sometimes two days on a bad week. Spiral episodes are noticeably fewer, and more of them are caught at the story stage rather than the behavior stage. The boundaries hold perhaps half the time, which the person counts as progress rather than failure. The internal standard has shifted from 'prove you are valuable immediately' to 'wait until you have information.' That is a smaller-sounding goal than it is. As they put it: the point was never to stop feeling things — it was to stop paying for them with entire weekends.
The Takeaway
For anyone who recognizes the RSD Overachiever shape — the catastrophizing after vague feedback, the pre-emptive overwork, the apology messages — the useful first step is not self-improvement but pattern recognition. Take the Workplace Spiral Quiz, name which stage of the loop you are in, and try interrupting it one stage earlier than usual. Shortening the spiral is a realistic goal. Eliminating it is not, and it does not need to be.
This content is for informational purposes only and is not medical advice, diagnosis, or treatment.