How to Explain Consulting Exhaustion to Someone Who's Never Done It (A Script That Actually Works)

Telling someone 'I worked 85 hours this week' never lands the way you need it to. Here's a specific communication framework — with word-for-word scripts — for explaining consulting exhaustion to partners and family who've never experienced it.

You came home at 11 PM on a Tuesday, sat down at the kitchen table, and your partner asked how your day was. You said "fine" or "long" or maybe just nothing at all. And they looked at you with that expression — somewhere between concern and frustration — and you felt the gap between you widen by another inch.

The problem isn't that they don't care. Most partners, family members, and close friends genuinely want to understand what's happening to you. The problem is the language you're using to explain it. When you say "I worked 85 hours this week," you're describing an output. You're handing them a number and expecting them to feel what you felt. They can't. Not because they're unsympathetic, but because 85 hours is an abstraction that their nervous system has no reference point for.

Why the Hour Count Doesn't Land

Most people who haven't worked in consulting understand tiredness from physical labor or from a single high-pressure deadline. What they don't have a frame for is the specific combination of things happening to you simultaneously: holding six client relationships in active memory across different industries, performing emotional warmth on calls when you're running on four hours of sleep, making judgment calls at 9 PM that you know you'll be questioned on at 8 AM, and doing all of this while being available, polished, and responsive at any moment the client decides to ping you.

That's not the same as working a lot of hours. Hours are the container. What's inside the container — the cognitive load, the emotional performance, the physiological state of someone whose cortisol has been elevated for eight consecutive weeks — that's what you're actually trying to communicate. And that's what the word "busy" or even "85 hours" completely fails to convey.

The Translation Framework: Three Shifts That Make the Difference

Instead of describing what you produced or how long it took, describe what's actually happening to your body and brain. Here's a framework built around three specific shifts:

Shift 1: Translate cognitive load into something they've experienced. Don't say "I have a lot of deliverables." Try: "You know how after you've been in back-to-back high-stakes conversations all day — like the day of your dad's surgery, when you were coordinating everything for everyone — and by 6 PM you can barely form a sentence? I'm in that state every single day by 3 PM, and then I have four more hours of calls." You're not exaggerating. You're using their memory as a bridge.

Shift 2: Name the physiological state, specifically. "Tired" is the most underspecified word in the English language. Instead, try: "My hands are shaking a little when I eat dinner right now. I've been grinding my teeth so hard I woke myself up twice last week. That's not tired — that's what chronic stress does to a body over months." Specific physical symptoms land in a way that "exhausted" never will.

Shift 3: Tell them exactly what you need, rather than leaving it implied. Most consultants describe their state and then leave the conversation hanging, which forces their partner to guess whether they want advice, sympathy, solutions, or space. Close the loop explicitly: "When I go quiet after I get home, I'm not shutting you out. I literally need 30 to 45 minutes where no one asks me anything, and then I come back. I'm asking you to give me that window without it feeling like rejection."

A Script for Partners Who Feel Shut Out

This is the conversation most consultants avoid having because they don't know how to start it without it turning into a fight about priorities. Here's a template — adapt it to your voice, but keep the structure:

"I want to explain something that I've been bad at explaining. When I come home and I'm silent, or when I can't really be present on weekends, it's not about you and it's not about us. Here's what's actually happening: my brain has been in problem-solving, performance mode for 12 to 14 hours. The part of me that can connect emotionally and be a real partner is genuinely offline — not metaphorically, but in a way that I feel physically. I'm not asking you to think that's okay or that it should keep happening forever. I'm asking you to understand that when it does happen, silence is me trying to come back online, not me checking out. What would help me most right now is [a specific, concrete thing — 20 minutes alone, you making dinner, no questions about work until I've eaten]."

Notice what this script does not contain: an apology for your job existing, a promise that it will change soon, or a request for them to validate that your suffering is real. Those framings invite debate. This framing invites understanding.

What This Conversation Is Not

Before you have it, be clear with yourself about what you're doing. You're not asking them to fix anything. You're not asking for permission to keep working these hours. You're not presenting a complaint that requires a solution from them.

If the conversation drifts toward "maybe you should quit" or "have you talked to your manager," you can redirect without being defensive: "I'm not asking for advice on the job right now. I'm asking for help understanding what I'm experiencing so you know what's going on with me. That's it."

This matters because consultants who don't set this frame up front often end up in a meta-argument about whether the job is sustainable instead of the actual conversation they needed to have. The goal of this exchange is connection and clarity, not problem-solving.

Being unable to explain what's happening to you at home creates a second layer of weight on top of the work itself — the loneliness of going through something intense and feeling completely alone in it, even when someone who loves you is sitting four feet away. Getting this language right doesn't solve the hours or the load, but it closes that particular gap.

Next week we start talking about what you can actually control during a high-intensity period — even when the hours aren't negotiable. If you want a structured place to start tracking your own state right now, Burnout Baseline: The Consulting Survival Protocol ($67) is a Notion-based system built specifically for consultants in the middle of exactly this. It includes a weekly energy log, a burnout severity self-assessment with clear action triggers, a decompression rituals menu, and a "what to do right now" emergency protocol for the nights when you don't even know where to start. It works within the reality of 80-hour weeks rather than pretending they don't exist.