Case Study 31-01: Marcus's Email Mistake

Background

Marcus Chen, 22, has been working as a paralegal at a mid-sized law firm for the past eight months. It is, by several measures, a good job: the work is intellectually interesting, it looks strong on law school applications, and his supervisor, Diane, is generally competent and fair. But for the past six weeks, Marcus has noticed something troubling: his hours have been quietly, incrementally reduced. He went from a consistent 28–30 hours per week to 22–24 hours with no explanation offered. The reduction is financially meaningful — Marcus helps cover his share of rent with Tariq — but more than that, it feels like a signal. Like something has shifted in how Diane sees his work.

Marcus has raised the issue twice, briefly, in passing. The first time, he caught Diane in the hallway between meetings and said, "Hey, I noticed my hours were a little lower this week — is everything okay?" Diane said, "Yeah, we've just had a lighter caseload. It should level out." The hours didn't level out. The second time, he sent Tariq a text that said, "Should I just talk to Diane about the hours thing again?" Tariq's reply: "Yeah, bro. But like, properly."

Marcus doesn't do it properly. He does something that feels like the next best thing: he writes an email.

The Email Marcus Sent

To: Diane Reardon From: Marcus Chen Subject: Concerns About My Recent Hours

Hi Diane,

I hope this finds you well. I wanted to follow up on the issue of my scheduled hours, which I mentioned briefly a few weeks ago. I've noticed that my hours have been significantly reduced over the past six weeks (from approximately 28–30 hours per week to 22–24 hours), and I haven't received any explanation for the change.

I want to make sure I understand whether this reflects a temporary caseload adjustment or something more permanent. I also want to flag that as someone who relies on consistent income, this change has had a real impact on me financially.

I value my position here and want to make sure I'm meeting expectations. If there's something about my performance that's contributed to this change, I would genuinely appreciate the opportunity to discuss it and address any concerns.

I'd welcome the chance to speak with you about this when you have time.

Best, Marcus Chen

Marcus read this email at least fifteen times. He thought it was measured, professional, and clear. He sent it at 7:42 a.m. on a Tuesday.

What Marcus Intended vs. What Diane Received

To understand why this email was a mistake, we need to examine the gap between Marcus's intent and Diane's experience of the message — a gap that email, by design, cannot bridge.

What Marcus intended: - To open a professional conversation about something that was worrying him - To signal that he was a responsible, financially aware adult - To leave the door open for Diane to share feedback about his performance - To request a meeting rather than have the whole conversation in writing - To come across as non-confrontational and collaborative

How the email likely reads to Diane:

The email begins "I hope this finds you well" — a standard pleasantry — and then pivots immediately to a detailed enumeration of exactly how much Marcus's hours have been reduced (from 28–30 to 22–24, to be specific). Diane, reading this, hears: I have been tracking this. I have numbers. I am building a case.

The phrase "I haven't received any explanation for the change" is passive in construction but active in implication. It says: you owe me an explanation you haven't provided. In the hallway conversation, Marcus's tone was genuinely curious. In the email, the same content reads as an implicit accusation: you have failed to explain yourself.

"As someone who relies on consistent income, this change has had a real impact on me financially" — Marcus included this because it was true, and because he thought it would humanize his situation. Diane reads it differently. In professional contexts, detailing personal financial consequences of a supervisor's decisions can read as pressure: you are causing me financial harm. It is, unintentionally, a statement of consequences — and a supervisor receiving a statement of consequences from a report tends to experience it as a threat, however mild.

The line about performance — "If there's something about my performance that's contributed to this change" — was intended to show self-awareness and openness. It may read to Diane as: I suspect there is a performance issue and I am calling your attention to the fact that you have not addressed it. Or: I am subtly reminding you that you have a legal and professional obligation to give me performance feedback before reducing my hours.

And Diane sees the request for a meeting at the end and knows that that conversation is now going to be formal, on the record, and preceded by this email — which she will have to have read multiple times before the meeting in order to prepare a response.

None of Marcus's intentions were bad. But email failed to carry them.

Why Email Was the Wrong Medium

This situation called for a conversation, not a document. Here's why:

The content was emotionally loaded. Marcus was worried, financially stressed, uncertain about his standing, and anxious about the relationship. None of that was readable in the email — and all of it needed to be visible for Diane to respond with appropriate care.

The relationship was already somewhat strained. When there is existing tension in a relationship, email intensifies rather than reduces it. There was no warmth in the email to counteract the implied accusation of inadequate communication.

Marcus needed real-time feedback. He needed to know how Diane was receiving his concern. He needed to see whether she was surprised (suggesting the hours reduction hadn't been a deliberate signal) or not surprised (suggesting it had been). He couldn't get that from a reply email.

The email created a formal record before a formal record was necessary. In most professional situations, the escalation to documentation should follow direct conversation, not precede it. By sending the email, Marcus created a paper trail that made what was a solvable interpersonal issue feel like the beginning of a formal complaint — which put Diane in a defensive posture before they even talked.

Diane's Reply

Diane's reply arrived forty-seven minutes later:

Marcus —

Thank you for bringing this to my attention. You're right that your hours have been adjusted over the past several weeks. The adjustment reflects current caseload demands and is not a reflection of any performance concern.

I'd be happy to schedule fifteen minutes to discuss if you'd like.

Diane

Three sentences. Cooler than Marcus had hoped for. The explicit "not a reflection of any performance concern" was meant to be reassuring but felt clinical — like language used to close a personnel file rather than to open a conversation. The offer of "fifteen minutes" felt formal. Their next in-person interaction was stiff in ways it hadn't been before.

Marcus had gotten what he asked for — a meeting — but at a relational cost he hadn't anticipated. The email had moved the conversation from the interpersonal register to the professional register, and Diane had responded in kind.

What a Good Email Looks Like vs. What a Bad Email Looks Like

The Bad Email (Marcus's version)

Marcus's email was not malicious or incompetent. But it violated several guidelines:

Wrong medium for emotional content. The email carried Marcus's financial anxiety, his uncertainty about his standing, and his subtle concern that Diane had failed to communicate. None of these translate well to text.
Implicit accusations disguised as factual reporting. Logging the specific hour reduction ("28–30 hours per week to 22–24") is the kind of detail that signals documentation mode, not conversation mode.
Personal financial detail as unintentional pressure. Financial impact statements belong in conversation, where they can be received with empathy, not in email, where they land as consequences.
Opens a formal record prematurely. The issue could likely have been resolved in one conversation. The email made it a documented concern.

The Good Email (What Marcus Could Have Sent Instead)

What if Marcus had used email only to request the meeting, keeping the substantive content for the conversation itself?

Subject: Request to Schedule a Check-In

Hi Diane,

Would you have 20 minutes this week for a quick check-in? There's something I'd like to talk through with you directly.

Thanks — Marcus

This version does almost everything the longer email does without any of the liabilities: - It requests a conversation without having the conversation - It signals that something is on Marcus's mind without detailing the complaint - It creates no permanent record of accusation, financial pressure, or implied fault - It leaves the actual content for in-person, where tone, warmth, and real-time feedback are available - It is short enough that Diane can reply quickly and easily

The good email is a door-opener, not a message. The content goes in the conversation, not the record.

How to Recover

After the email was sent and the stiff meeting had occurred, Marcus had to rebuild what the email had slightly damaged. The recovery process involved three steps:

Step 1: Acknowledge the awkwardness, briefly, in the next interaction. Not an apology for raising the issue — which was legitimate — but a brief acknowledgment that the channel had been clunky. "I think I made that harder than it needed to be by doing it over email. I should have just asked to talk." This kind of low-key self-awareness tends to reduce residual tension and signals emotional maturity.

Step 2: Return to the normal register of their relationship. The email had pushed things into a formal register. Marcus needed to re-establish the easier, less formal dynamic through small behaviors: a genuine question about Diane's work, a moment of levity, normal engagement. Formal dynamics don't require formal repair — they just require normal interaction to dissolve the awkwardness.

Step 3: Let the meeting outcome be the final word. Diane had said the hour reduction wasn't a performance concern. Marcus, having had the meeting, needed to accept that answer and stop revisiting it digitally. Continued email about the issue would compound the formality. The issue had been raised and answered. The next data point would simply be whether the hours normalized.

Lessons

Match the medium to the content. Emotionally loaded, relational conversations belong in conversation. Email is for information and documentation.
A good email requests the conversation; it doesn't have the conversation. Marcus's email tried to do the conversation's work in advance. A better approach: email to set up the meeting, save the substance for the meeting.
Formal records should follow direct conversation, not precede it. Escalating to documentation before attempting resolution in person is usually premature and tends to put the other party on the defensive.
What feels professional can read as adversarial. The precision, detail, and emotional restraint that Marcus thought would make him look professional made Diane feel accused. Restraint without warmth is cold; in email, cold reads as hostile.
Recovery is possible but requires normal behavior, not more formal behavior. The instinct after an awkward formal interaction is to keep managing it formally. The better path is to return to the normal register of the relationship as quickly as possible.