Case Study 8.1: Marcus's Catastrophe Ladder
A Practical Walkthrough of Decatastrophizing in Action
Background
Marcus Chen is 22, a college senior and pre-law student in his final semester. He has been working as an unpaid intern at Whitmore & Associates for four months. His internship agreement specifies 20 hours per week during the academic semester. For the past eight weeks, he has been consistently working between 30 and 34 hours per week.
He knows this is a problem — financially, because he's supporting himself with part-time food delivery shifts that he increasingly cannot fit into his schedule; and academically, because his thesis writing has been crowded out. He has documented his hours carefully. He has the email trail.
He also has Diane Whitmore's recommendation letter pending. Diane is a 15-year partner. Her letter, for three of his law school applications, is scheduled to be submitted by March 15th — four weeks from now. The internship ends May 1st.
The situation is unambiguous. The path forward is, objectively, to send Diane a short, professional note. And yet Marcus has been sitting on this for three weeks, sleeping badly, and running the same cognitive loop every time he gets close to writing the email.
This case study walks through his pre-confrontation cognitive process, applies the Catastrophe Ladder, and traces what happens when he actually has the conversation.
Stage 1: Surfacing the Catastrophe Chain
Marcus's therapist (whom he started seeing in November for generalized anxiety) has been asking him to write things down. He finally does, at 11:50 PM on a Wednesday, the way you finally clean the kitchen drain after the water has been pooling for a week.
Here is what he writes:
What I need to say: Diane, I've been tracking my hours, and I've been averaging 30-32 hours per week. My contract specifies 20. I want to talk about how we can get back to that.
What I'm afraid will happen:
- Diane hears "I've been tracking my hours" and reads it as surveillance — as though I've been building a case against her.
- She gets defensive. She thinks I'm implying she's been exploiting me deliberately, or worse — that I'm suggesting fraudulent billing for hours that weren't contracted.
- She goes to the other partners. "This intern is documenting hours and raising complaints." I become a liability.
- The partners investigate. Or they don't — they just note my name as someone who causes trouble.
- The recommendation letter gets colder. Or it doesn't get written at all.
- Three of my law school applications are weaker. Or missing a key letter entirely.
- I get waitlisted. I get deferred. I get rejected from my top choices.
- I reapply next cycle. But I've lost a year. My GPA was good but not remarkable. Without the Whitmore letter, my applications are missing a narrative anchor.
- I end up doing document review. Not forever, maybe. But long enough that it shapes my trajectory.
- Dad picks up the phone when I call to tell him law school didn't work out.
He reads this back to himself. Then he writes one more line, in brackets:
[This is catastrophizing. I know this is catastrophizing. And I believe every word of it.]
That bracket is the opening. The cognitive work starts there.
Stage 2: Building the Catastrophe Ladder
Marcus's therapist has taught him the ladder framework. He draws it out.
RUNG 5 — Imagined Catastrophe
"I ruin my career before it starts.
I call my dad. He picks up."
RUNG 4 — Secondary Catastrophe
"I don't get into law school.
I spend a year regrouping."
RUNG 3 — Loss of Key Resource
"The recommendation letter is withdrawn
or so negative it hurts my application."
RUNG 2 — Relationship Damage at the Firm
"Diane tells the partners.
I'm labeled a troublemaker.
The internship becomes hostile."
RUNG 1 — Diane's Immediate Reaction
"Diane takes this as an accusation.
She gets defensive. She thinks I'm
building a case or implying fraud."
RUNG 0 — Actual Situation
"I need to tell Diane that my hours
have exceeded my contracted 20/week
and ask how we can address that."
The catastrophize chain is now visible. The question is whether each rung realistically leads to the next.
Stage 3: Testing Each Transition
Marcus works through the ladder, transition by transition. He is trying to do something genuinely difficult: assess each link in the chain using evidence rather than fear.
Transition: Rung 0 → Rung 1
Claim: Diane will interpret a billing concern as an accusation of fraud or misconduct.
Evidence for: Billing ethics are serious in law. The words "I've been tracking my hours" could theoretically be read as adversarial. Diane is a partner with reputational stakes.
Evidence against: Marcus and Diane have had a professional, functional relationship for four months. He has not been a source of problems. The request itself is completely standard — a conversation about workload alignment is normal at any internship or job. Diane has displayed competence under pressure before: when a client called last month upset about a bill, she handled it calmly and professionally. There is nothing in Marcus's history with Diane that suggests she defaults to defensiveness.
Realistic probability of this transition: Low to moderate. There is perhaps a 20–30% chance Diane has any kind of defensive initial reaction. Even if she does, defensive does not equal hostile.
Transition: Rung 1 → Rung 2
Claim: Even if Diane gets defensive, she will escalate to the partners and label Marcus as a troublemaker.
Evidence for: Partners at law firms do talk to each other. Diane does have this option.
Evidence against: This would require Diane to decide that a reasonable workplace request from an intern is worth escalating — which would be unusual, potentially embarrassing for her as a supervisor, and professionally disproportionate. Most experienced managers handle these conversations without escalating them. There is no evidence Diane has a pattern of punitive escalation. The more likely outcome, even in a defensive scenario, is a direct conversation.
Realistic probability of this transition: Very low — perhaps 5–10% given even a defensive Diane.
Transition: Rung 2 → Rung 3
Claim: Even if the partners were alerted, the consequence would be a withdrawn or damaged recommendation letter.
Evidence for: Partners do control what gets written under their names. Theoretically possible.
Evidence against: This chain now requires: (a) Diane to take a professional grievance to partners, (b) partners to react negatively rather than appropriately, AND (c) Diane to decide her letter should be withheld or sabotaged. Each assumption builds on the previous one. By this point, the scenario is not merely possible — it requires a series of improbable events occurring in sequence. Additionally, a law firm that withdrew a recommendation letter because an intern asked about contracted hours would be creating enormous liability for itself.
Realistic probability: Near zero. The multiplicative probability of reaching Rung 3 from Rung 0 is already well under 5%.
What the Analysis Reveals
Marcus does not need to go further. By the time he reaches Rung 2, the probability has already dropped to something vanishingly small. The catastrophe chain that has felt like a logical sequence turns out to be a series of unlikely transitions, each dependent on the previous one occurring and each requiring increasingly improbable behavior from the people involved.
The catastrophized worst case is theoretical. The realistic worst case is something quite different.
Stage 4: The Realistic Worst Case
Marcus writes out the realistic worst case — not the catastrophized version, not the optimistic version, but the honest assessment of what could go wrong.
Realistic worst case: Diane has a defensive moment. The conversation is slightly uncomfortable. She may not immediately acknowledge the issue fully. Marcus may feel anxious during and briefly after the conversation. The working relationship might be slightly cooler for a week or two.
These outcomes are uncomfortable. They are not catastrophic. Marcus would survive them. He has survived awkward professional interactions before. He has the documentation to support his position. Even a slightly cooler working relationship does not affect the recommendation letter that has already been requested and is, by all accounts, on track.
He sits with this realistic worst case. Then he asks the follow-up question his therapist introduced:
Can I live with that?
Yes. Marcus can live with an awkward conversation and a briefly cooler relationship.
Stage 5: The Three-Column Thought Record
Marcus completes a thought record for his primary automatic thought.
| Column 1: Situation | Column 2: Automatic Thought | Column 3: Rational Response |
|---|---|---|
| I need to tell Diane that I've been averaging 30+ hours/week against a contracted 20, and ask how we can address it. | "If I bring this up, she'll think I'm accusing her of fraud, escalate to the partners, and I'll lose the reference that my law school applications depend on." | Diane has been professionally competent and calm under pressure in the interactions I've observed. A reasonable workload concern is a normal professional communication, not an accusation of fraud. The chain of events I'm imagining requires multiple unlikely transitions, each dependent on the previous. The realistic outcome of this conversation is far more likely to be resolution or adjustment than escalation. The risk of NOT saying anything — continued overwork, thesis falling behind, growing resentment — is something I've been underweighting. |
Stage 6: The Pre-Confrontation Cognitive Check
The night before he sends the email, Marcus runs through the four-step check:
Step 1 — Surface the automatic thoughts:
"She'll think I'm accusing her. She'll tell the partners. I'll lose everything."
Step 2 — Name the distortion:
Catastrophizing (treating an unlikely chain as inevitable). Fortune telling (certainty about Diane's reaction without evidence). Possible mind reading (assuming I know her interpretation).
Step 3 — Generate a rational response:
The realistic version is: I have a legitimate, documented concern. Raising it is professionally appropriate. The most likely outcome is a resolution conversation. Diane has demonstrated professionalism. Even a defensive initial reaction is not the same as an escalation. The chain I've been running breaks at Rung 1.
Step 4 — Set an intention:
I want to communicate clearly, without accusation, and find a mutual adjustment. I want to stay curious about any logistical factors I might not be aware of. I'm not going into this to win; I'm going in to find a workable path.
Stage 7: The Email
Marcus writes the email at 7:45 AM. He has edited it eleven times over the past three weeks. This version takes six minutes.
Subject: Quick check-in about my hours
Hi Diane,
I've been keeping track of my weekly hours and I've been averaging around 30–32 hours over the past eight weeks, which is above my contracted 20. I wanted to flag this and check in with you directly — I want to make sure I'm understanding the expectations correctly and see if there's a way to get back to the contracted hours, particularly as I'm coming into my thesis crunch.
Happy to talk through whatever works for you.
Thanks, Marcus
No accusations. No apologies. No preemptive justifications. A statement of fact, a check-in, and a collaborative frame.
He sends it. His hands are slightly cold. He goes to class.
Stage 8: The Actual Conversation
Diane responds four hours later.
Subject: Re: Quick check-in about my hours
Marcus — Yes, I'm glad you brought this up. I've been aware that the billing on your assignments has been uneven and I've been meaning to address it. Can you come by Thursday at 3?
Marcus reads this three times.
She was going to address it. She noticed. She had also been waiting to raise it.
Thursday's conversation takes eleven minutes. Diane explains: two projects came in unexpectedly in December and the staffing model wasn't updated to reflect the volume shift. She has already flagged it to the firm administrator. Going forward, she'll cap his assignments at 22 hours maximum and flag him when projects are in scope. She apologizes for the January and February weeks — "that wasn't intentional, but it wasn't right."
The catastrophe that Marcus spent three weeks constructing has a 22-hour-per-week ceiling and an apology.
Analysis: What the Tools Did
Looking back at this case, three things are worth noting.
The Catastrophe Ladder interrupted the chain rather than eliminated the fear. Marcus was still anxious when he sent the email. The ladder didn't make the fear disappear; it made the fear legible. He could see, clearly, that his certainty about catastrophic outcomes was not supported by evidence. The fear was a signal from his threat system, not a prediction from an oracle.
The thought record externalized a thought that had been feeling like reality. Written down, the automatic thought ("she'll think I'm accusing her of fraud... I'll lose everything") became a claim that could be examined rather than a condition that had to be managed. Externalization is one of the simplest and most powerful things the thought record does.
The pre-confrontation cognitive check changed his intention. Marcus did not enter the conversation with "I need to protect myself." He entered with "I want to find a workable path, and I want to understand her perspective." That shift — from defensive to curious — changed the email's tone and almost certainly changed Diane's response.
What This Case Illustrates About Catastrophizing
This case is, in one sense, a story about an anxious 22-year-old overcomplicating a workplace email. In another sense, it illustrates something that applies at every level of professional and personal life: the catastrophizing mind is not rare, and it is not a sign of weakness. It is a feature of a threat system doing its job too aggressively in a context that does not require that level of vigilance.
The work of decatastrophizing is not to eliminate the threat system — it's to calibrate it. To give it accurate information about the actual stakes, the actual probabilities, and the actual resources available to you.
Marcus's resources, as it turned out, were substantial: documentation, a functional professional relationship, a legitimate concern, and an email application. The catastrophizing mind had been hiding those resources behind a wall of imagined disaster.
The Catastrophe Ladder didn't give Marcus new resources. It revealed the ones he already had.
Discussion Questions
-
At what point in the catastrophe chain did you notice it becoming implausible? Was it the same point Marcus identified, or different?
-
Marcus brackets his catastrophizing with the note: "I know this is catastrophizing. And I believe every word of it." What does this tell us about the relationship between cognitive insight and emotional conviction? Is knowing you're catastrophizing sufficient to stop it?
-
Diane says she had "been meaning to address" the billing issue. What does this reveal about the cost of Marcus's three-week delay — and who bore that cost?
-
How would this situation have unfolded differently if Marcus had entered with all-or-nothing thinking instead of catastrophizing? What would the "all-or-nothing" version of his internal narrative have sounded like?
-
The catastrophizing chain required Marcus to imagine Diane behaving in specific, implausible ways. What does this reveal about how catastrophizing depends on assumptions about other people's behavior? How does that intersect with mind reading?