How a Product Marketer Handles RSD at Work: Case Study

The Breaking Point

The Thursday 1:1 lasted fourteen minutes and was almost entirely neutral. Near the end, her manager said something close to, 'This is solid - maybe tighten the narrative before Friday.' No raised voice, no warning sign, no stated concern. She walked out of the room already replaying it, cataloguing the pause before 'solid' and the word 'maybe.'

By 4:47 p.m. on Friday, a two-line Slack message landed: 'Hey, can we chat later?' No urgency marker, no context. She read it eleven times, built three versions of what 'later' might mean, and spent the weekend drafting a defense document nobody had requested. Sunday-evening dread arrived early, around 3 p.m., and the rest of the weekend collapsed into a low, buzzing knot in her chest.

By Monday morning she had submitted two extra drafts, apologized preemptively in a thread where nothing had gone wrong, and volunteered for a reporting project she had no capacity to run. To anyone watching, she was the reliable one. Internally, she was assembling evidence for a verdict that had not been reached.

Recognizing the Pattern

The pattern only became visible when she stopped calling it 'being too sensitive' and started calling it a loop. The Workplace Spiral Quiz at /workplace-spiral-quiz asks twenty plain-language statements, and her answers came back with a profile that felt uncomfortably accurate: Rejection Sensitive Dysphoria as the loudest signal, moderate burnout layered underneath, and a smaller shutdown response waiting behind it.

In the Spiral Loop Framework, that shape has a name - the RSD Overachiever. A neutral or vague input (a short message, a skipped greeting, a slightly delayed reply) gets read as evidence of failure. The body reacts before the reasoning mind can weigh in - jaw, chest, stomach - and then the behavior follows: overworking, over-explaining, preemptive apologies, volunteering to prove worth. The aftermath, exhaustion mixed with resentment, lowers the threshold for the next loop. She may have ADHD; she has never been assessed, and this is not a diagnosis. It is a framework that finally matched what was happening to her.

What Actually Helped

None of this required a dramatic reinvention. It required making the loop visible early enough to interrupt it. The Spiral Loop Framework separates a spiral into four moving parts - trigger, interpretation, body response, behavior - and the free tools at /tools gave her simple ways to tag each one without turning the exercise into another performance review she could fail.

The single most useful change was inserting a gap between the message and the meaning. A self-imposed 48-hour rule for anything ambiguous: no drafts, no replies, no defense documents until she had asked one clarifying question. She kept a standard line in her notes app: 'I want to make sure I fix the right thing, so let me check I am reading this correctly.'

She also started treating the physical signal - the tightening jaw, the 3 p.m. Sunday dread - as the earliest indicator that a loop was starting, rather than waiting for the emotional conclusion to arrive. This is educational content, not medical advice, and it does not replace professional support. It is a set of small, repeatable habits anyone can test and drop if they do not fit.

Scripts and Small Structures That Stuck

Two scripts did most of the work. The first was for vague feedback: 'When you said tighten the narrative, do you mean the structure or the supporting data? I would rather ask now than guess.' The second was for her own spiral: 'I am going to sit with that for an hour and come back with questions.' Both moved her from silent interpretation into an actual conversation, which is usually where the catastrophe dissolved.

The structures were unglamorous. Slack notifications batched into two windows instead of always-on. A written log, updated twice a week, of things that had gone well - not to feel good, but to have counter-evidence ready when her memory insisted on producing only failures. One standing 1:1 agenda item: 'Is there anything you need me to change, and is there anything I should stop worrying about?' Removing ambiguity in advance reduced the raw material the loop had to work with.

Where Things Stand Now

The change was real but partial, and she would say so first. The vague Slack message still lands. She still feels the drop. But the loop is shorter now - usually hours instead of a weekend - and she notices it while it is happening rather than three days later. The compulsive volunteering has slowed; she has started answering 'let me check my capacity and come back to you' instead of 'yes.' She took a full PTO day without opening Slack, which she described as harder than any deadline she had shipped that quarter.

She calls the quiz a starting point, not an answer - it gave her language for something she had spent years assuming was a character flaw. The tools at /tools are free and built to be used mid-workweek, not after a crisis. Nothing here is medical advice; it is a map of one loop, drawn by someone who has walked it, offered in case it helps someone else notice theirs earlier.