RSD at Work as a Client Success Manager: Case Study
A 33-year-old Client Success Manager
A 33-year-old Client Success Manager read one vague Slack message as proof she was about to be fired. Here is how she mapped her RSD Overachiever spiral and shortened recovery time.
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 33-year-old Client Success Manager was the top performer on her renewal team and privately convinced that one ambiguous message would end her career. A vague Slack request from her manager triggered a week of over-preparation, cancelled plans, and four hours of sleep, even though the meeting itself was routine. Rejection sensitivity showed up as the loudest signal in her spiral profile, with burnout and shutdown trailing behind it.
Solution
She took the Workplace Spiral Quiz at /workplace-spiral-quiz, which named her dominant pattern, and then used the Spiral Loop Framework to break each episode into trigger, story, behaviour, and cost. Working through the free tools at /tools, she built a 24-hour rule for reacting to ambiguous messages, a two-minute evidence check, and a short script for asking managers for specificity instead of guessing. She also practised declining the first project offered in a meeting. This is educational, peer-sourced workplace strategy rather than medical advice, and it works best alongside whatever support a person already has.
Outcomes
“I used to read a two-word Slack message and decide I was about to be fired. Now I notice the spiral starting, and I have something to do about it.”
The Feedback That Started the Spiral
The message arrived at 4:40 on a Thursday afternoon: "Do you have a sec tomorrow to talk about the Q3 renewals?" No agenda, no emoji, no context. A 33-year-old Client Success Manager at a mid-sized B2B software company read it eleven times in the next two minutes. She owns roughly twenty accounts, and she is very good at her job — which is exactly why the message felt like the beginning of the end. By 6pm she had cancelled dinner with a friend and rebuilt her entire renewal deck from scratch. By 11pm she had written and deleted four different apology emails for reasons she could not name. She slept about four hours, woke at 5am to re-read the message, and spent the morning 1:1 braced for a conversation about performance. The actual topic was a new account assignment and whether she had capacity for it. The meeting lasted fourteen minutes.
Recognizing the RSD Overachiever Pattern
What the manager said was neutral. What the Client Success Manager heard was: you are slipping and everyone has noticed. That gap between a vague input and a catastrophic interpretation sits at the centre of the RSD Overachiever pattern, and it rarely looks like tears or visible panic. It looks like overwork. Over the next few weeks the loop repeated with smaller and smaller triggers. A client reply one sentence shorter than usual. A colleague's thumbs-up instead of a comment. A calendar invite titled simply "quick chat." Each time the response was identical: double the effort, triple the preparation, apologise preemptively, then collapse on the weekend with a vague mix of resentment and exhaustion. When she took the Workplace Spiral Quiz, rejection sensitivity was her loudest result by a wide margin, with burnout and shutdown trailing behind — the classic shape of a pattern driven by fear rather than by actual workload.
Mapping the Loop with the Spiral Loop Framework
The turnaround started with a quiz, not a therapist. A colleague mentioned the Workplace Spiral Quiz at /workplace-spiral-quiz, a short self-assessment that scores which common workplace spiral patterns a person leans into. Taking it took ten minutes. Reading the results took longer, because it was the first time the experience had a name that was not "being dramatic" or "being bad at handling pressure." The framework behind the quiz treats a spiral as a loop: trigger, story, behaviour, cost, repeat. Seeing it as a loop rather than a personality flaw made it workable. She started writing each episode down. Trigger: ambiguous Slack message. Story: "I'm about to be managed out." Behaviour: build a twelve-slide deck nobody asked for. Cost: one lost evening, one short night, growing resentment toward a manager who had done nothing wrong. Once the story step was visible, it was the step she could actually argue with.
What Actually Helped
The first tool she adopted was a 24-hour rule. When a message produced a spike of dread, she wrote the catastrophic interpretation in a notes app and did nothing with it for a day. Most of the time the story looked absurd by the next morning. She paired it with a two-minute evidence check from the free tools at /tools — a short prompt set that asks what was actually said, what was actually implied, and what is actually known. The second tool was a script. Instead of absorbing vague feedback and guessing at it, she started asking for specifics in plain language: "Thanks for flagging that — when you say the deck needs to be more strategic, what would that look like on slide one?" It felt exposing the first few times. It also ended most spirals inside the meeting rather than three days later. Alongside it, she began passing on the first project offered in any meeting and replying with "let me check my capacity and come back to you tomorrow," which bought her nervous system the pause it needed. None of this is medical advice. It is peer-sourced workplace strategy, and it tends to work best alongside whatever support a person already has. The goal is not to eliminate a reaction but to shorten the distance between the trigger and the recovery.
Where Things Stand Now
A season later, things are better without being fixed. She still over-prepares some weeks. She still notices a small drop in her chest when her manager's name appears in Slack. The difference is what happens next. Instead of a week of overwork, it is an afternoon. Instead of volunteering for everything, she asks what the team actually needs and answers honestly when the answer is nothing. She describes the change in terms of recovery time rather than confidence. Boundaries remain awkward. Some weeks the loop wins outright, and she treats that as information rather than failure. But the pattern is now something she observes from the outside instead of something that happens to her — and for anyone whose career has been quietly shaped by rejection sensitivity, that shift is the whole game.
This content is for informational purposes only and is not medical advice, diagnosis, or treatment.