Case Study 22-1: "Marcus's Shutdown"

What flooding looks like from the inside — and what a flooding-aware response would be


Background

Marcus Chen has been working as a paralegal at the firm for eight months. He is sharp, careful, and deeply anxious about his professional standing — partly because he is watching how he presents himself as a pre-law student, partly because Diane, his supervisor, has a directness that he finds difficult to read, and partly because he knows his future recommendation letters live in this building.

When Diane is pleased with his work, she says nothing. When she has a concern, she is direct and specific — which Marcus knows, intellectually, is the ideal supervisory style, and which, experientially, lands on him like a warning every time. He has never been explicitly criticized by Diane. He has also never entirely felt safe with her.

He has been avoiding something for two weeks. A client file — the Greenfield estate — has a discrepancy in the timeline he constructed. He caught it himself, three days after submitting the file. The discrepancy is not large; it is a matter of a date notation on a trust document that conflicts with the filing date. But it is an error, it is his error, and he has been waiting for Diane to notice it.

This morning, she calls him into her office.


The Conversation

Diane is at her desk. She has the Greenfield file open.

"Sit down," she says. Not unkindly. Just directly.

Marcus sits.

"I've been looking at the Greenfield timeline." She turns the file so he can see it. "This date here" — she points — "doesn't match the filing date on this document." She places the second document alongside the first.

Marcus looks at the documents. He already knew this was there. He has known for thirteen days. He has three separate explanations prepared — or he had them, somewhere, in some part of his thinking that is now, in this moment, very hard to locate.

"I see it," he says. His voice sounds normal. He does not feel normal.

"What happened here?"

And something strange occurs: Marcus, who had been preparing for this moment for thirteen days, who had an explanation, who had even rehearsed the words "I noticed this myself a few days after filing, and I think what happened was —" goes completely blank.

Not slightly blank. Not the kind of blanked-out feeling where you have a thought and it's just slightly out of reach. Blank like a white wall. Like the explanation is not in the building.

"I —" he starts. "I'm not — I need to look at it again."

Diane looks at him. There is a quality in her looking that he cannot read, and his inability to read it is making everything worse. Is she angry? Disappointed? Waiting? He cannot tell.

"Take a moment," she says.

This should be helpful. It is not helpful. The moment becomes a place where he is supposed to have something, and he does not have it. The moment gets heavier.

"I think I made a notation error," he says, finally. This is technically true. It is also profoundly incomplete. It is the kind of answer that answers nothing.

Diane sets down the file. She is quiet for a moment.

"Did you know about this before I called you in?" she asks.

Marcus does not answer immediately. The honest answer is yes. He caught it himself. He noted it. He planned to bring it to her and did not. He had reasons — good reasons, reasons that made sense — and those reasons are also nowhere in this room.

"I — I think I may have seen something." He stops. That is not right. He tries again. "I wasn't sure if it was —" He stops again.

Diane waits.

Marcus looks at the documents. He understands that he is doing something wrong in this conversation — that he is giving Diane less than she is asking for, less than he owes her, less than the situation requires. He is aware of this from a slight remove, as though watching himself from just slightly outside his own body. He cannot seem to close the distance.

"I need to review my notes," he says. He does not know why he says this. He has reviewed his notes. He knows exactly what happened. But the words have come out, and he cannot unsay them, and now he is in a place where he has implied uncertainty about something he is not actually uncertain about.

Diane sets down her pen.

"Okay," she says. "Get me your notes and let's talk again this afternoon."

Marcus nods. He leaves her office. He is in the hallway for maybe four seconds before he is able to take a full breath.

He had not been able to breathe normally the entire time he was in there.


What Happened: A Neurological Account

Marcus experienced flooding. To understand what happened in that room, it helps to follow the physiological sequence in real time.

The pre-load condition. Marcus had been carrying low-grade elevated cortisol for thirteen days. He knew about the error. He had been waiting for Diane to notice. The waiting is itself a chronic mild stressor — anticipatory anxiety maintains a low-level stress response over time, meaning Marcus arrived at this conversation with his baseline arousal already elevated. He was closer to his flooding threshold before the conversation started.

The trigger. When Diane opened the Greenfield file and pointed to the discrepancy, Marcus's nervous system registered this as the threat it had been anticipating for nearly two weeks. The threat response activated rapidly — not because Diane was aggressive or threatening in her manner (she wasn't), but because the situation was the feared situation. Anticipatory anxiety, when the feared event actually arrives, tends to trigger a sharp spike in arousal.

The cortical inhibition. The explanation Marcus had prepared — clear, accurate, appropriate — was stored in working memory, which is a prefrontal cortex function. As his arousal spiked, resources were redirected away from the prefrontal cortex. The explanation became inaccessible not because it wasn't there but because the system that should retrieve it was running with degraded capacity.

The behavioral markers. In real time, flooding produced: - Voice that sounded normal to Diane but felt wrong to Marcus (he was monitoring it from a slight remove — the dissociative quality of flooding) - Inability to access prepared information ("blank like a white wall") - Incomplete, hedged, inaccurate statements ("I think I may have seen something" when he knew exactly what had happened) - The strange out-of-body quality of watching himself from a slight remove and understanding he was doing something wrong but being unable to correct it - The inability to breathe normally (shallow, restricted breathing throughout)

The unintended outcome. Marcus left the conversation having failed to disclose something he had been planning to disclose. He had implied uncertainty about something he was not uncertain about. He had bought himself an afternoon meeting during which he would have to essentially start over, now with the added complication of having given incomplete answers. Flooding did not protect him from the conversation; it made the conversation worse and extended its duration.


The Counterfactual: What a Flooding-Aware Marcus Would Do

This is the most instructive part of the case study: not the analysis of what happened, but the specific reconstruction of what a Marcus who had studied Chapter 22 would do differently.

Yellow Zone Recognition

The flooding-aware Marcus would have tracked himself in the minutes before entering Diane's office. He would have noticed: his shoulders were tense, his breathing was slightly restricted, and when he had tried to mentally rehearse his explanation that morning, he'd found it slightly harder to access than expected. These are yellow zone signals.

He might also have recognized the pre-load condition: thirteen days of low-grade anticipatory anxiety had already elevated his baseline arousal. He was going into this conversation at a disadvantage before it started.

The flooding-aware Marcus, knowing all this, might have done two things before entering Diane's office: five minutes of extended-exhale breathing, and a written note — just a few words — summarizing the three key points of his explanation. (Research on flooding and retrieval suggests that externalizing key information — writing it down — reduces the retrieval burden on working memory under high arousal, making it more accessible even when cognitive resources are compressed.)

In-the-Room Recognition

The flooding-aware Marcus would feel the spike when Diane opens the file and points to the discrepancy. He would notice: heartbeat audible in his ears, the reaching-for-words that finds something different from the words, the slight out-of-body quality beginning.

He would name it to himself: "I'm flooding. This is physiology. I know the answer to this question. I need a moment."

The Pause Request

The flooding-aware Marcus would say — within five to ten seconds of the moment he recognizes the spike — something like:

"Can I ask for a moment before I answer? I want to make sure I give you the full picture, and I need a second to gather my thoughts."

This is a Step 2 pause request. It is not an admission of wrongdoing. It does not reveal that he is flooding (though that would not be catastrophic if it did). It communicates that he is taking the question seriously enough to want to answer it correctly, rather than hastily.

Diane's response — "Take a moment" — suggests she might have offered this anyway. The flooding-aware Marcus would treat this as genuine permission and use it deliberately: two or three slow exhale-extended breaths, looking at the documents (grounding to external concrete reality), and accessing his written note if he has one.

The Answer He Actually Had

The explanation Marcus had prepared, and which flooding had made temporarily inaccessible, was roughly this:

"I caught this discrepancy myself about three days after filing. I identified it as a date notation error — the trust document uses the execution date, but I entered the recording date, which is three days later. I should have brought it to you immediately when I noticed it. I didn't, and I owe you an honest account of why: I convinced myself it wasn't significant enough to flag, and I was also uncertain about how to raise it. Looking back, that was the wrong call. The fix is straightforward — the filing date is the controlling date, and I can update the timeline this afternoon."

This explanation is clear. It is complete. It is honest about the error and honest about the two-week delay. It is exactly what Diane is asking for. And Marcus knew it — had it prepared, had it ready — before flooding rendered it temporarily inaccessible.

The productive conversation that Marcus wanted to have would have been approximately three minutes long. Diane would likely have said something like "Okay, fix it today and let me know when it's done." The matter would have been closed.

Instead, the conversation produced incomplete answers, an afternoon follow-up meeting, and — crucially — a new, complicating question about whether Marcus's hesitation indicated something about his judgment or his honesty. That new question did not exist before the flooding.

Honest Assessment of the Harder Part

The flooding-aware Marcus also recognizes something that the above account might obscure: there was a legitimate concern underneath the flooding that was not purely physiological. He had known about the error for thirteen days and had not disclosed it. This was a real decision he had made, and the flooding, in a sense, was protecting that decision from examination — making the disclosure harder by making words harder to access.

This is not uncommon. Sometimes flooding and avoidance are separate phenomena that compound each other: we flood partly because the threat response is activated, and partly because our nervous system senses that what is about to be said will involve something difficult we have been avoiding. The two things — physiological flooding and the real, valid discomfort of a disclosure that involves accountability — are different, even when they feel the same.

The flooding-aware Marcus knows he would still need to have a hard conversation with Diane about the thirteen-day delay. The flooding protocol does not resolve that conversation; it just makes the conversation possible. What he avoids, by managing the flooding, is adding a second problem (the dishonest-by-omission answers) to the first problem (the delayed disclosure).


Afternoon Meeting: The Recovery

Marcus does not wait for the afternoon meeting. An hour after the morning conversation, he goes back to Diane's office.

"Do you have five minutes? I want to be more straightforward than I was this morning."

Diane closes what she was reading. "Sit down."

He sits. He has the written note in his pocket, and he has done a short regulation practice in the restroom. His heart rate is normal. He can think clearly.

"I knew about the discrepancy," he says. "I noticed it myself about three days after filing. I should have come to you right then, and I didn't. The reason I gave you this morning — that I wasn't sure — that wasn't honest. I was sure. I was just unsure about how to raise it."

Diane holds his gaze for a moment. "Why didn't you come to me?"

"Because I was embarrassed about the error, and I was hoping it wouldn't come up. That was wrong, and I know it."

Diane is quiet for two seconds. Then: "I appreciate you coming back. The error itself is minor. The thirteen-day delay is worth thinking about, because that's the part that affects how I can rely on you. If something comes up in future, I need you to come to me within twenty-four hours. Can you do that?"

"Yes," Marcus says.

"Fix the timeline today."

"I will."

The conversation lasted seven minutes. The productive conversation Marcus had been unable to have that morning — the one the flooding had prevented — took seven minutes once the flooding was resolved and he had returned to his own clear thinking.


Discussion Questions

  1. The chapter distinguishes between flooding and avoidance, noting that they can compound each other. How were both present in Marcus's story? Is the flooding a cause of the avoidance, a result of it, or something else?

  2. Marcus's flooding was triggered by a conversation he had been dreading and preparing for simultaneously. How does anticipatory anxiety interact with flooding threshold? What does this suggest about situations we spend a long time dreading?

  3. The "unintended outcome" of Marcus's flooding — incomplete answers that raised new questions about his honesty — is arguably worse than full disclosure would have been. What does this tell us about the relationship between flooding and self-protection? When does self-protection (the instinct that flooding is partly serving) actually undermine our interests?

  4. Marcus's recovery — returning to Diane's office an hour later — required him to do something harder than the original conversation would have been: he had to acknowledge that he had given incomplete answers in addition to acknowledging the original error. How does this illustrate the compound cost of unmanaged flooding?

  5. What specific elements of Marcus's context — his role as a student watching his professional standing, his uncertainty about how to read Diane, the thirteen-day delay — made his flooding threshold particularly low for this conversation? What would he need to change (if anything) to reduce his vulnerability in similar conversations?


Case Study 22-1 | Chapter 22: Navigating Emotional Flooding — Yours and Theirs