Is Management Consulting Stressful?

The travel. I know that sounds like the thing everyone says, and it is the thing everyone says, because it's the thing. My schedule right now is: 5:30 AM alarm on Monday, 7:15 AM flight to Charlotte, Marriott check-in by 10, client site by 10:30, work until 7 or 8, hotel, work from the hotel until 11, sleep. Tuesday and Wednesday are the same minus the flight. Thursday: client site until 3, Uber to the airport, 5:45 PM flight back to DCA, home by 8 if there are no delays, which there are delays about 40% of the time. Friday I'm in the D.C. office for "team day" but mostly I'm recovering from the week while pretending to be productive.

I've done this for 38 straight weeks. Not 38 total. Thirty-eight consecutive. The engagement I was on before Charlotte was in Minneapolis. Before that, Hartford. I've been home for five or more consecutive nights exactly twice in the past year: once at Christmas and once when I had COVID. My apartment costs $2,400 a month. I sleep there an average of 10 nights a month. That's $240 per night for the privilege of having a place where my mail goes. My plants died in month four. I bought fake ones. My roommate, Jordan, and I coordinate our schedules on a shared Google Calendar so we know who's actually going to be there on any given night. Most weeks, neither of us is.

The physical part is worse than the logistical part. I've gained 14 pounds since starting because hotel dinners and client lunches are the only social interactions I have Monday through Thursday, so I eat more than I would at home because eating is the event. My skin is bad from recycled airplane air. I've had three sinus infections in three years. My dermatologist asked me if I travel frequently and when I said "four days a week, every week," she said "that explains a lot" and prescribed a moisturizer that costs $48 and lives in my carry-on next to the laptop charger and the Marriott Bonvoy card that has accumulated 340,000 points. The points are the only upside. I used them for a vacation in Maui last year. I stayed in a Marriott.

The clock. At MBB, you're on a promotion timeline from the day you start. Associate for two to three years. Engagement manager for two to three years. Associate principal for two years. Then partner or out. Every transition has a gate. Every gate has a review. Every review is a comparison against your cohort. If you're not in the top half, you get "development feedback," which is consulting language for "you have six months to fix this or we start the conversation about your transition." "Transition" is consulting language for "leaving." There's an entire vocabulary designed to make firing sound like personal growth.

I'm in year five. I made engagement manager last year, which means I cleared the first gate. The next gate is associate principal, which requires demonstrating "business building" capability, which means: bringing in revenue. Not just delivering work. Selling work. That's a fundamentally different skill than anything I've done for the past five years. For five years I've been rewarded for analytical rigor, client management, and team leadership. Now the game changes and I'm being evaluated on my ability to generate $3 to $5 million in new engagements. If I can't, I won't make AP. If I don't make AP within two to three years, the clock runs out.

The specific stress is that the clock runs independently of your performance. You can be excellent at your current level and still get pushed out because you haven't demonstrated capability at the next level fast enough. My colleague, Wendy, was one of the best engagement managers I've ever worked with. Clients loved her. Teams loved her. She didn't make AP because she wasn't selling. She left four months ago for a VP of Strategy role at a healthcare company. She's happier. She's also making $80,000 less. The up-or-out system doesn't optimize for "who is doing the best work." It optimizes for "who is most likely to become a partner." Those are different questions with different answers.

The rework cycle. I don't mean revision, which is normal. I mean the specific pattern where you build something, it gets reviewed by the manager, revised, reviewed by the senior manager, revised again, sent to the partner, and the partner says "I think we need to rethink the approach." That last sentence erases a week of work. Not because the work was wrong. Because the partner's mental model of the answer evolved between the time they scoped the work and the time they saw it. This happens on maybe 60% of the cases I've been on. It's not malicious. Partners are managing four or five cases simultaneously and their attention is fragmented. They give directional guidance, you build it, and by the time they review it, they've had three calls with the client that changed their thinking. The result is that the most stressful thing about my job is not the volume of work. It's the volatility of work. I can handle 65 hours if I know what those 65 hours are going to produce. What I can't handle is 65 hours where 20 of them produce something that gets scrapped because the direction changed.

Last month I built a benchmarking analysis for a financial services client. Forty-seven companies, twelve metrics each, normalized across four different reporting standards. It took me about 18 hours. My manager, Vikram, reviewed it, liked it, sent it to the partner. The partner said: "I think the client already knows the benchmarking story. Can we pivot to a profitability decomposition instead?" Vikram called me at 9:30 PM and I could hear in his voice that he'd already processed his own frustration and was now in the business of managing mine. He said "I know." I said "yeah." We rebuilt it. The profitability decomposition took another 14 hours. The partner used three of the seven slides we built. I keep a tally. Not officially, not in a spreadsheet. Just in my head. The number of slides I've built versus the number the client has seen. The ratio right now is roughly 4 to 1. Three quarters of my output never leaves the building.

The politics you didn't sign up for. Not office politics, although those exist. Client politics. Every consulting engagement exists inside a client's organizational power structure, and that power structure has factions, alliances, grudges, and agendas that have nothing to do with the problem we were hired to solve. The person who hired us, usually a C-suite exec, has a vision. The people affected by our recommendations, usually VPs and directors, have a different vision. And the people doing the actual work, the managers and individual contributors we interview, have a third vision that's usually the most accurate but carries the least political weight.

I'm running a transformation project at a manufacturing company right now. The CEO hired us to restructure their go-to-market organization. The Chief Revenue Officer thinks the restructuring is a proxy for replacing him, which it might be. The VP of Sales is cooperating because she thinks the outcome will expand her scope. The VP of Marketing is stonewalling because he thinks the outcome will reduce his budget. None of them will say any of this directly. They say things like "I want to make sure we're being thoughtful about this" (translation: slow it down until I can position myself) and "I'm supportive of the process" (translation: I'll cooperate publicly and undermine privately). My job is to produce an analytically sound recommendation while managing four simultaneous political realities that I can see but can't name. If I name them, I lose trust. If I ignore them, the recommendation fails because nobody implements a restructuring that threatens their power without fighting it.

The stress isn't the politics themselves. It's that the politics are invisible in the work product. My slides show org charts and revenue models and capability assessments. They don't show the fact that I spent 90 minutes yesterday on a call with the CRO, essentially providing therapy, while he processed his fear that this project will end his career. That call doesn't appear on my utilization report. It doesn't appear in the project plan. It's completely invisible work that consumes roughly 40% of my energy on a transformation engagement. And if I don't do it well, the project fails, and the failure shows up in my performance review as a delivery issue, not a political management issue, because the review system doesn't have a field for "navigated a CRO's existential crisis without losing the engagement."

My body. I ran cross-country in college. I could run a half marathon in 1:38. I haven't run in two months because by the time I get back to the hotel at 8:30 PM, I've been awake for 14 hours and the idea of lacing up running shoes feels like a cruel joke my past self is playing on my present self. I've gained 22 pounds since starting at the firm. My blood pressure was 138/88 at my last physical. My doctor asked about my stress levels and sleep habits and I described my work schedule and she looked at me the way a mechanic looks at you when you describe the sound your car is making. Like she already knew the diagnosis before I finished talking.

The sleep is the worst part. I cannot overstate how much consulting destroys your sleep. Not just the quantity, although the quantity is bad (six hours is a good night, five is average, four happens twice a month). The quality. My brain does not turn off. I wake up at 2 or 3 AM thinking about the model. Not a nightmare. Just... thinking. The model is there, in my head, and my brain is running scenarios. What if the assumption about market share erosion is 200 basis points too aggressive? What if the client pushes back on the discount rate? These are not urgent thoughts. They're not thoughts that benefit from being had at 2:47 AM in a Marriott in Charlotte. But my brain has lost the ability to distinguish between work time and sleep time. The boundary dissolved somewhere around year three and I haven't been able to rebuild it.

My husband, Marcus, is an architect. He works hard. He works long hours sometimes. But when he comes home, he's home. He doesn't wake up at 3 AM thinking about floor plans. I asked him once if he does, and he laughed, and the laugh told me everything about the difference between a career with boundaries and a career without them. I'm 34. I used to run half marathons. Now I take melatonin and hope for six hours. That's the trade. Nobody puts it on the recruiting brochure, but that's the trade.

Sundays. I don't mean Sunday work, although Sunday work happens. I mean the feeling that starts at about 4 PM on Sunday and settles into my chest like a low-grade electrical current. The Sunday Scaries. Everyone in consulting knows the term. Most people outside of consulting think it means "I don't want to go back to work tomorrow." That's not what it means. It means: the part of my brain that was resting for 36 hours just received a signal that rest is over, and the signal arrived three hours before the actual work starts, which means I lose the last three hours of my weekend to anticipatory anxiety about a Monday that hasn't happened yet.

The specific thing I'm anxious about changes every week. Sometimes it's a client meeting where I know the partner is going to present my analysis and the client is going to push back and I'm going to be sitting there trying to look confident while someone who runs a $600 million business tells me my market sizing is wrong. Sometimes it's the flight. I have a 6:40 AM flight to Houston tomorrow, which means a 4:45 AM alarm, which means I should be asleep by 10 PM, which means the anxiety about the alarm is preventing me from sleeping, which means the alarm will go off after five hours of bad sleep, which means I'll be tired on the plane, which means the work I planned to do on the plane won't get done, which means I'll be behind before the day starts. The cascade is predictable. I've had this exact cascade roughly 180 times. I know it's irrational. Knowing it's irrational doesn't make it stop.

My girlfriend, Sophie, can see it happen. She says my energy changes at around 4 PM on Sundays. My voice gets flatter. I check my phone more. I start thinking about packing. She calls it "the shift" and she's learned not to take it personally but I can see that it costs her something. She gets 36 hours of a person who's present and then the shift happens and she gets the pre-Monday version who's already half gone. She's a veterinarian. She works hard. She has stressful days. But she doesn't have Sundays. Her Mondays are just Mondays. Mine are a countdown that starts the afternoon before. I've been in therapy for a year, partly because of this. My therapist says the Sunday anxiety is a conditioned response and we're working on decoupling the temporal trigger from the emotional response. That's the kind of sentence you learn to say when you've been in consulting long enough to turn your own mental health into a framework.