Case Study 11-1: The Language of Marcus's Mistake

A Practical Walkthrough — Annotated Transcript and Corrected Version

Background

Marcus Chen is a 22-year-old pre-law senior who interns three days a week at a mid-sized litigation support firm. His supervisor, Diane, manages four interns and two junior associates. Marcus is bright, detail-oriented, and genuinely committed to doing good work — but he has a persistent problem: his language patterns undermine everything he communicates.

He over-hedges. He qualifies his statements until they lose their weight. He apologizes before he has done anything wrong, which signals that he expects to be wrong. And when he tries to raise something that actually matters to him, the hedging and the qualified language make his concerns almost impossible to take seriously.

For the past three weeks, Marcus has been staying an average of 90 minutes past his scheduled hours to complete tasks that Diane assigns at 4:15 p.m. — just before his shift technically ends. He has said nothing. He has not asked for comp time. He has not told Diane that this is affecting his evening class schedule, which it is. He finally decides to say something.

He prepares what he thinks is a careful, non-confrontational statement. He believes he has used an I-statement. He has not.

The Conversation: Marcus's First Attempt

Marcus knocks on Diane's open office door. Diane looks up from her monitor.

Marcus: "Oh — sorry to bother you. Do you have maybe a quick second? This won't take long."

Diane: "Sure. What's up?"

Marcus: "So, um — I'm not sure if this is even like, a real issue, or if I'm maybe reading things wrong, but — I kind of wanted to maybe mention something. If that's okay."

Diane: "Go ahead."

Marcus: "Right, so — I feel like you maybe don't realize how much I've been staying late. Like, every single time you give me an assignment after four, I end up staying way longer than I'm supposed to. And I just — I'm not sure if this is — I don't want to make it into a thing, but I feel like you don't really consider what that does to my schedule."

Diane: [slight pause] "I didn't realize you had a hard out at a specific time. You should have said something."

Marcus: "Yeah, no, totally — I mean, I should have, probably, I just — I guess I didn't want to be difficult or whatever. It's probably fine. I just thought I'd mention it."

Diane: "Okay. I'll try to keep that in mind."

Marcus leaves. Nothing is agreed to. Diane goes back to her monitor. Marcus still does not know if anything will change.

Annotated Transcript: What Went Wrong

Let's examine Marcus's language move by move.

"Oh — sorry to bother you."

Annotation: Marcus has not bothered Diane. He knocked on an open door and she invited him in. By opening with an apology for his own presence, Marcus is signaling — before he has said a word about the actual topic — that he expects to be an imposition. This is a preemptive self-diminishment that immediately frames his concern as probably not worth Diane's time. It also hands Diane the authority position in the conversation before any power dynamics have been established.

"Do you have maybe a quick second? This won't take long."

Annotation: Two problems here. First, "maybe a quick second" is over-qualified — a genuine request would be "Do you have a few minutes?" The hedging communicates that Marcus does not believe his own request is legitimate. Second, "This won't take long" is a preemptive minimization of the conversation Marcus is about to have. If the topic matters — and it does — saying it won't take long establishes that it probably doesn't matter. Marcus has undermined his own concern before he has raised it.

"I'm not sure if this is even like, a real issue, or if I'm maybe reading things wrong..."

Annotation: This is catastrophic framing. Marcus is treating his own perception as suspect before Diane has responded. He is inviting Diane — or himself — to dismiss the concern entirely on the grounds that he might be wrong about whether it constitutes "a real issue." The effect is that the listener hears: "This might not matter. I might be wrong. Feel free to tell me this is nothing." This is not humility. It is conversational self-sabotage.

"I feel like you maybe don't realize how much I've been staying late."

Annotation: This is a classic disguised you-statement. Marcus has opened with "I feel like," which sounds like an I-statement, but the content — "you maybe don't realize how much I've been staying late" — is not an emotion. It is an attribution about Diane's awareness (or lack thereof). Marcus is acting as an authority on Diane's inner state. The sentence also contains another hedge ("maybe"), which softens the already-problematic statement further. The correct structure here would be an actual emotion word followed by a specific, observable description.

"Every single time you give me an assignment after four, I end up staying way longer than I'm supposed to."

Annotation: This contains an absolute ("every single time") that is almost certainly inaccurate and invites Diane to search for exceptions. It also uses vague quantities ("way longer"). The phrase "than I'm supposed to" implies a rule that Diane may not be aware of — and if Diane is not aware of it, the phrase is opaque. What does "supposed to" mean? What is Marcus's scheduled end time? Has that been established and communicated? The behavioral content that Marcus needs to communicate — the frequency and duration of the late stays — is present but surrounded by hedges and absolutes that obscure it.

"I feel like you don't really consider what that does to my schedule."

Annotation: This is a second disguised you-statement, and it is the most damaging sentence Marcus says. "I feel like you don't really consider" is an accusation about Diane's character and thought processes dressed up in I-statement grammar. The word "really" adds contemptuous emphasis. This sentence will activate defensiveness in a way that is entirely predictable — and that Marcus does not want. Diane's response, notably, is to point out that she didn't know about the scheduling constraint — which suggests that Marcus's accusation about Diane's consideration is actually unfounded. Marcus blamed Diane for not considering something she did not know about.

"I don't want to make it into a thing."

Annotation: Marcus undercuts his own concern by explicitly labeling it "a thing" — a phrase that trivializes. He is communicating, again, that he is not sure his concern deserves to be taken seriously. This is the third time in the same brief statement that Marcus has minimized the very concern he is trying to raise.

"I should have, probably. I just — I guess I didn't want to be difficult or whatever. It's probably fine. I just thought I'd mention it."

Annotation: This is a complete retraction dressed up as a response. Marcus has been told by Diane that he should have said something. Rather than using this as an opening to establish what he needs going forward, Marcus retreats entirely. "It's probably fine" contradicts the entire reason he had this conversation. "I just thought I'd mention it" frames his legitimate workplace concern as casual small talk. By the end of the exchange, Marcus has essentially told Diane that nothing needs to change — even though he still needs something to change.

The Core Problems, Summarized

Marcus's language had four primary failure modes:

Preemptive minimization: Multiple times, Marcus told Diane that his concern might not matter before she had any chance to respond to it.
Disguised you-statements: Two of Marcus's "I feel" sentences were actually accusations about Diane's awareness, consideration, and character.
Absolutes: "Every single time" is both inaccurate and counterproductive.
No clear request: Marcus never stated what he needed. He described a problem, blamed Diane (covertly), and then took the blame back — without ever saying: "Here is what I am asking for."

A confrontation without a clear request is a complaint. Complaints do not resolve anything. Requests do.

The Second Run: Marcus's Revised Conversation

Marcus takes a day to reflect on how the conversation went. He identifies that he said nothing useful and made an accusation he did not intend to make. He decides to try again, this time using the tools from Chapter 11.

He prepares by writing out: - The specific observable facts (what has happened, how often, how long) - His genuine emotion about it - The concrete impact on him - What he is actually asking for

He also identifies the specific sentences he was tempted to use that were disguised you-statements, and he replaces them.

Marcus knocks on Diane's door the next morning.

Marcus: "Diane, do you have five minutes? I want to follow up on something I tried to raise yesterday, because I don't think I said it well."

Diane: "Sure, sit down."

Marcus: "I want to be direct about something that's been affecting me. Over the past three weeks, I've received assignments at or after 4:15 p.m. on six or seven occasions. My shift ends at 4:30, and I've been staying 60 to 90 minutes past that to finish them. I haven't said anything until now, which is on me — I should have raised this sooner."

Diane: "I genuinely didn't realize your shift ended at 4:30. That's been my assumption error."

Marcus: "I appreciate that. What I should have made clearer is that I have a class on Tuesday and Thursday evenings at 6:30, and the late stays are cutting into my transit and prep time. That's been stressful."

Diane: "That's completely reasonable. What would work for you?"

Marcus: "What I'd like to ask for is this: if an assignment is going to require more than 30 minutes of work, could I get it before 3:30? That gives me time to either complete it or hand it off with a clear status update. If something urgent comes up after that, I'm open to discussing it case by case — I just need some predictability."

Diane: "That's a fair and completely workable request. I should have asked about your schedule when we set the internship up. Let's make 3:30 the standard cutoff."

Marcus: "Thank you. I should have said this three weeks ago."

Diane: "Now you know to."

Analysis: What Marcus Did Differently

He opened with a direct statement of purpose. "I want to follow up on something I tried to raise yesterday, because I don't think I said it well." This is honest, slightly vulnerable, and sets an inquiry-into-improvement frame rather than an accusatory one. He is not apologizing for existing — he is naming something specific he wants to address.

He used specific, observable, countable language. "Six or seven occasions. My shift ends at 4:30. Sixty to 90 minutes past that." These are not absolutes — they are estimates grounded in specific facts. They are credible and hard to dispute.

He took accountability for his own silence. "I haven't said anything until now, which is on me." This is important for two reasons: it is accurate, and it prevents Diane from feeling she is being blamed for something Marcus never communicated. This sentence is what makes Diane able to respond generously.

He identified the concrete impact. "I have a class on Tuesday and Thursday evenings at 6:30." This is not a complaint — it is a fact that makes sense of why the late assignments are a genuine problem, not just an inconvenience. It also gives Diane information she did not have before and could not have been expected to consider.

He made a specific, behavioral, negotiable request. "If an assignment is going to require more than 30 minutes of work, could I get it before 3:30?" This is the request that was entirely absent from the first conversation. It gives Diane something she can actually agree to, and it includes a reasonable carve-out ("I'm open to discussing it case by case") that signals Marcus is not being inflexible.

He did not use a single disguised you-statement. Notice that nowhere in the second version does Marcus say "I feel like you don't realize" or "I feel like you don't consider." He described his situation, named his feelings indirectly but genuinely ("that's been stressful"), and made a request.

What Marcus Learned

The first conversation felt safer to Marcus because he hedged everything. But safety achieved through hedging is illusory — it produces a conversation where nothing is communicated clearly enough to produce a response, which means nothing changes, which means the situation continues, which means Marcus keeps staying late and getting more frustrated. The hedging was not protecting him; it was protecting the status quo.

The second conversation felt riskier because Marcus was specific. But specificity is what made resolution possible. Diane could not respond to "I feel like you don't really consider what that does to my schedule" — there was nothing actionable in it. Diane could immediately respond to "assignments before 3:30" — there was a concrete thing to agree to.

The lesson Marcus carried forward: a confrontation without a request is a complaint. A complaint expressed in hedged, qualified, absolute-laden language is noise. A specific request, grounded in observable facts and named impact, is a conversation.

Discussion Questions

In the first conversation, Marcus made an accusation about Diane's character ("you don't really consider what that does to my schedule") that turned out to be factually unfounded — Diane did not know about his scheduling constraints. How did the over-hedging and the disguised you-statement work together to produce this result?
Marcus takes accountability for his own silence in the second conversation ("which is on me"). How does this change Diane's posture in the conversation? What would have happened if he had blamed Diane for "not checking in" about his schedule?
The case study notes that "a confrontation without a request is a complaint." How does this relate to the DESC framework from Chapter 10? Which element of DESC was entirely missing from Marcus's first attempt?
Marcus's first conversation contains no genuine emotion word — not one. His second conversation also avoids explicit emotion labeling, though it references stress. In what contexts is it better to name your emotion explicitly, and in what contexts is it sufficient to name the concrete impact?
How might Marcus's pattern of over-hedging interact with his professional development as a pre-law student? What does the language of law require that his current communication patterns undermine?