When a Shitty Email Opens an Old Courtroom

A few years ago, when I was working at a group private practice, a practice-wide email went out from administration. I don’t remember the exact wording now, which probably tells you something, because I remember my reaction much more clearly than I remember the actual email. It was likely something ordinary: a reminder about procedures, a clarification about documentation, one of those emails that gets sent because the same issue keeps coming up and somebody finally decides to put it in writing.

But when I read it, I heard tone.

And once I heard tone, I wasn’t just reading a policy reminder anymore. I was reading disrespect. I was reading control. I was reading someone talking down to me. I was reading someone keeping score. My interpretation was already moving before I had done anything useful with the actual facts.

The reaction in my head was immediate: “That didn’t land well. I’m done. I’m out of here. I don’t need this. I’m not W-2, and I’m not going to be talked to like this.”

That was the part I had to pay attention to later. There was the email, and then there was the story I attached to the email. By the time I walked into the owner’s office, I was already responding to the story. I had already assigned motive, intent, hierarchy, and disrespect. I had already built the case.

To his credit, the owner was a therapist and could tolerate feedback without turning the conversation into a defensive mess. We talked through the email, clarified the intention, and the whole thing ended up being completely reasonable. Which made it more uncomfortable, because once the conversation was over, I had to look at the size of my own internal reaction.

The email may have had tone. Maybe it did. Maybe I added some of it. Either way, the intensity of my response had gone past the facts I actually had.

That is the part people skip. They want to stay in court about whether the other person was rude, dismissive, controlling, passive-aggressive, unfair, or condescending. Sometimes they were. Sometimes the email did have tone. Sometimes the policy was stupid. Sometimes the boss really was incompetent.

That still does not explain why your reaction went from zero to burn the whole thing down.

The Email Was Current. The Room Was Old.

That is why the image for this piece looks the way it does.

The laptop is showing a petty administrative email. Time sheets. Compliance. “Thank you for your attention to this matter.” The kind of corporate language that sounds polite while carrying a threat underneath it. The kind of language that smiles while copying your supervisor.

But behind the laptop is a command-staff room: uniforms, rank, contempt, authority, institutional pressure. That is the whole point. The current situation is a boring email. The reaction is being organized by an older room.

Most people have some version of this.

Someone asks for clarification, and it feels like you’re being audited by the IRS.

Someone gives feedback, and it feels like a demotion is already in progress.

Someone sends a reminder, and it feels like control.

Someone questions a decision, and your mind starts building a legal defense before you have even asked one clarifying question.

Different room. Different people. Different facts. Same reaction.

That is where the pattern starts to show itself.

Schema: The Survival Template

The simplest way I know to explain a schema is this: a schema is a survival template.

It is a rule your mind built from experience. Based on what has happened before, this is probably what is happening now.

That rule may have made sense when it formed. It may have helped you read a room faster. It may have helped you survive criticism, control, shame, or consequences. The problem comes when the old template keeps getting applied automatically to situations that only resemble the original threat.

Then you are responding to what happened and what it reminds you of.

That is the whole concept. A schema is a survival template. The work is noticing when the template showed up before you did.

How the Template Gets Built

When I look back at my own life, I can see why that particular template got built.

One part came from growing up with a father who was a scientist. Extremely intelligent. Very analytical. Also very critical. That combination is tricky because criticism can hide inside competence. It can sound reasonable. It can sound like precision. It can sound like someone is simply trying to make the work better. And maybe sometimes they are. But when that is the atmosphere you grow up in, feedback starts carrying a different meaning.

Nothing was ever quite right. Nothing was ever a perfect score. If something could be improved, it was pointed out. If something was wrong, it was definitely pointed out. Over time, a kid learns the rules of that room. A question can become a correction. A correction can become exposure. Feedback starts feeling less like information and more like proof that you missed something again.

Then add identity.

I grew up gay in a conservative Christian environment. When you are a kid in that setting, identity itself becomes something people evaluate. You learn early that parts of who you are may create consequences if they become visible. People can call it love while quietly teaching you to hide. They can talk about truth while making certain truths feel dangerous. They can talk about morality while making your existence feel like a problem to be managed. Sometimes words like ‘abomination’ were used, but nobody has to sit you down and explain the lesson directly. You learn it from the room. You learn it from what gets praised, what gets punished, what gets whispered about, and what everyone pretends they are not saying.

So now criticism has an old charge on it. Authority has an old charge on it. Being evaluated has an old charge on it.

Then I spent twelve years in law enforcement, which reinforced the same pattern from another direction.

Law enforcement is a hierarchy. Orders move down. You follow the directive. You confirm that you understand. You choose your words carefully because the structure is real and the consequences can become real quickly. If a lieutenant tells you something, the expectation is simple: follow the order, confirm you understand, and don’t debate the decision publicly.

I remember one moment that ended up in my personnel file several years ago from a different chapter of my life. I was a sergeant, and command staff wanted a policy enforced that required officers to ask permission to leave their patrol zone, even to grab lunch, use the bathroom, or stop at a gas station. These were grown adults. Some of them had been cops for twenty or thirty years.

The policy made very little sense operationally. Even the lieutenant had said in a previous conversation that he thought it was ridiculous. But policies are policies, so I enforced it. The only thing I did differently was give the officers a heads-up ahead of time so they wouldn’t be blindsided by it during roll call. My thinking was simple: let them get their frustration out over the weekend so by Monday everyone could just do the job.

Later, when I was being demoted, that situation came up. They said I had difficulty enforcing policies. I explained that I had enforced the policy, but had warned the officers ahead of time so there wouldn’t be unnecessary friction. Then I said to the lieutenant sitting in the room, “You yourself even said this policy was ‘bullshit’.”

When the demotion paperwork went in my personnel file and was emailed to me by the chief, it stated that I had said, quote, “We discussed your deficiency in relation to following directives and your response was that you did not follow the ‘bullshit’ ones”.

That wasn’t what I said. But what made it in the personnel file was a double injury from already being demoted.

When I questioned the wording, I was brought back into another meeting with the chief and the entire command staff. The chief said, “You have accused the chief of police of lying and falsifying a document.”

At that point, the conversation had moved away from the policy. It had become about power. It had become about whether I was allowed to name what happened. It had become about what the system would do if I pushed back on the way the story was being written.

That kind of experience teaches a specific lesson: what you actually said can get rewritten. Context can disappear. Speaking up can be turned into insubordination.

So you adapt. You swallow the response. You nod. You say, “Yes ma’am. Understood. Maybe I’m not remembering correctly.” Under duress you do things like this to pay your mortgage and ensure you have health insurance.

Then years later, some administrator sends a slightly irritating email about documentation procedures, and part of you reacts like command staff just walked into the room.

Winning the Argument and Losing the Pattern

This kind of work gets difficult because the trigger may contain a real signal.

Sometimes people are controlling. Sometimes they are condescending. Sometimes they do send emails with tone. Sometimes they use “policy” as a way to dress up insecurity. Sometimes the workplace really is dysfunctional.

The signal can be real and the response can still be carrying old material.

That distinction ruins the clean story. If the other person was rude, I get to stay innocent. If the email had tone, I get to keep my edge. If the policy was stupid, I get to justify the contempt. If the criticism was unfair, I get to act like every part of my response was earned.

That is how people stay stuck while sounding completely reasonable.

They can explain every detail of why they were right. They can prove the other person communicated poorly. They can point to the exact sentence that had tone. They can tell you why the policy made no sense, why the boss was incompetent, why the partner was unfair, why the criticism was inaccurate. And they may be right about all of it.

Then the same reaction shows up again next week with a different person.

That is the tell.

If the same reaction keeps appearing across different situations, the pattern is asking to be looked at.

Owning the Pattern

Owning the pattern means I can say: that email annoyed me, and I added a whole history to it. That person may have had tone, and I escalated internally before I had the facts. That policy was stupid, and my reaction also carried years of authority conflict. That criticism touched something old, and I still have to choose what I do next.

That is the adult move.

The immature move is to keep proving the trigger was real. The adult move is to ask what the trigger activated.

What story did I attach to this?

What did I assume was happening?

What did I feel compelled to do next?

Those questions expose the template. If my first impulse is to defend myself like I am on trial, there is probably an old courtroom in the background. If my first impulse is to quit, disappear, punish, retaliate, or write a five-paragraph legal brief in response to a two-sentence email, something got activated beyond the facts.

That does not make me bad. It makes the pattern visible. And visible patterns can be worked with. Hidden patterns run the show.

The goal is to stop confusing activation with accuracy.

Some emails deserve irritation. Some people communicate poorly. Some systems are ridiculous. Some authority figures should be questioned. You can still hold people accountable while taking responsibility for the size of your own response.

That is where some freedom starts to show up. Annoying freedom. The kind where growth looks less like a breakthrough and more like catching the pattern five minutes earlier than you used to.

You send the cleaner email. You ask the clarifying question. You walk into the conversation with curiosity instead of a fully prepared closing argument. You stop turning every tone issue into a referendum on your autonomy. You stop letting old authority figures write today’s response.

That is owning the pattern.

The situation may be current. The reaction may be old. And once you can see that clearly, you have a choice you did not have before.

That’s doing the work.