What Management Consulting Is Actually Like

You came straight out of Northwestern. Why consulting?

Honestly? Because I didn't know what I wanted to do and consulting was the answer to that problem that also came with a good salary. That's not the answer you're supposed to give. The answer you're supposed to give is: "I wanted exposure to multiple industries and accelerated professional development." And that's true. But the real reason I went to the career fair and talked to the Big 4 firms and not, say, the tech companies or the banks, is that consulting lets you postpone choosing. You can be 22 and not know if you want to be in healthcare or retail or private equity, and consulting says: great, we'll figure it out together. We'll put you on a healthcare project for three months and then a retail restructuring for four months and by year three you'll know what you like. What they don't tell you is that by year three you still won't know what you like, but you'll be very good at PowerPoint.

Describe what you actually do.

I build slides. I know that sounds reductive. It's not. Let me walk you through a case. We were hired by a regional grocery chain, 140 stores, annual revenue around $2.3 billion, headquartered in the Midwest. Their CEO wanted to understand whether they should expand into three new markets or invest in store renovations in their existing footprint. That's the "case," in consulting language. Our team was four people: a partner named Richard who owned the client relationship, a manager named Anika who ran the day-to-day, me, and an analyst named Jordan who was in his first year. The engagement was scoped at 10 weeks.

My role was to build the market entry analysis. That means: pull demographic data from Census and Esri for the three target markets. Model revenue projections based on comparable store performance. Estimate build-out costs by contacting commercial real estate brokers and construction firms in each market. Assess competitive density by mapping every Kroger, Publix, Aldi, and Walmart Supercenter within a 10-mile radius of potential sites. Build all of this into a framework that says: Market A is attractive because X, Market B is risky because Y, Market C is a wash. Then turn that framework into slides that Richard can present to the CEO in a 90-minute session.

That work took me about three weeks. The analysis was solid. Anika reviewed it, pushed back on some assumptions about cannibalization rates, I revised. We got to a good place. Then Richard looked at it for the first time on a Thursday afternoon and said "I think we're framing this wrong. Can we restructure around customer segments instead of markets?" That meant rebuilding the entire deck from a geographic lens to a demographic lens. Which is not a small change. It's a fundamental restructuring of the logic. I rebuilt it over the weekend. Monday, Richard looked at it again and said "actually, let's go back to markets but keep the segment overlay." So now it's a hybrid. That's version three. The final deck, the one the CEO saw, was version seven. I made 11 distinct versions of the core slide that compared the three markets. Eleven. Each one took between 45 minutes and two hours. That's roughly 15 to 22 hours on one slide. The CEO glanced at it for about 40 seconds during the presentation and said "makes sense" and moved to the next page.

That sounds like it would make you want to throw your laptop out a window.

It does. And it doesn't. The frustrating part is obvious: the rework, the weekend, the feeling that your analytical work is being filtered through someone else's aesthetic preferences. Richard didn't change the analysis. He changed the framing. The answer was the same in every version. Market A was the best option. But how we told the story of why Market A was the best option changed 11 times because Richard was optimizing for how the CEO would receive it, not for analytical accuracy. And he was right to do that. That's the part that took me two years to understand. Consulting isn't an analytical job. It's a persuasion job that uses analysis as raw material. The analysis has to be right. But being right isn't sufficient. You also have to be right in a way that the person hearing it can accept and act on. That's a different skill. It's a communication skill. And it's the thing that separates the people who become partners from the people who become very talented analysts who leave at year four.

Are you one of those people?

Probably? I'm in year four and I haven't decided. The partner track from here is: get promoted to manager, then senior manager, then director, then partner. Each step is roughly two to three years. Partner by 37 or 38 if things go well. Partner compensation at our firm is roughly $500,000 to $1.2 million depending on the practice and your book of business. The money is real. But the path to get there requires becoming Richard. It requires becoming someone whose primary skill is managing client relationships and shaping narratives, not doing the analytical work. And I don't know if I want to be Richard. I like Richard. He's good at his job. But his job is 60% selling, 30% managing, and 10% thinking. My job right now is 10% selling, 20% managing, and 70% thinking. I like the thinking. The thinking is why I'm here. If I stay, I'll do less and less of it every year.

What do your weeks look like?

When I'm on a case: Monday morning flight to wherever the client is. Last quarter it was Minneapolis. Before that, Dallas. The hotel is a Marriott because our firm has a Marriott corporate rate. I've stayed in approximately 80 Marriotts in four years. They all look the same. The sheets are always white. The desk is always too small. The lamp is always on the wrong side. I work at the client site Monday through Thursday. "Client site" means a conference room that the client gave us, which we've filled with our laptops and empty LaCroix cans and a whiteboard covered in frameworks. We work from about 8 AM to 7 or 8 PM at the client site, then go back to the hotel and work from 9 PM to midnight on slides and models. Thursday evening flight home. Friday is supposed to be an "internal day" for firm activities, training, and personal development. In practice, Friday is a catch-up day where I finish the slides I couldn't finish during the week because the client kept scheduling meetings during my work blocks.

The travel sounds glamorous for about three months. Then it becomes a logistics problem. My apartment in Chicago is where I keep my things. I sleep there Thursday night through Sunday night. My roommate, Casey, who works in marketing at a CPG company, sees me more on FaceTime than in person. I've been dating someone, Theo, for about eight months, and our relationship exists primarily on Tuesday and Thursday evenings via text message and on weekends when I'm not too tired to leave the apartment. Theo is patient. More patient than the situation probably warrants. I told him once that consulting is like being in a relationship with a job that travels with you, and he said "so I'm dating someone who's already in a relationship." He was joking. Mostly.

What's the thing about consulting that nobody tells you before you start?

The expertise illusion. I'm four years in and I've worked on grocery retail, pharmaceutical manufacturing, insurance distribution, and municipal government. I know something about all of them. I don't know enough about any of them. The client hires us because they believe we bring expertise. What we actually bring is a structured approach to problem-solving and very good slides. The domain expertise, the deep knowledge of how grocery supply chains actually work or how insurance distribution networks are structured, that lives in the client's people. We're packaging their knowledge in a framework and selling it back to them with a recommendation. This is not a criticism. The framework has value. The outside perspective has value. The structured approach genuinely helps. But there's a moment on every engagement where someone at the client, usually a VP who's been in the industry for 20 years, looks at you and you can see them thinking: "This 29-year-old is going to tell me how to run my business?" And the honest answer is: no, I'm going to help you organize what you already know into a story that will get your CEO to fund the thing you've been asking for. That's the real product. I am a professional translator between middle management's ideas and the C-suite's attention span.

You were in operations before consulting. What pulled you across?

I managed a distribution center for a logistics company in Memphis for four years before business school. 220 employees, three shifts, $45 million in annual throughput. I knew operations. I could run a DC. The problem was that running a DC is not a thinking job after year two. It's a management job. And I wanted a thinking job. A friend from college, Raj, had gone to Tuck and then into consulting, and he described the work as "getting paid to solve a new problem every three months." That sounded right. I applied to Tuck, got in, and recruited into boutique consulting specifically because I didn't want the Big 4 or MBB machine. I wanted to be in the room. At a 40-person firm, everyone is in the room. There's no analyst sitting in a corner building a model that a partner presents. I build the model and I present the model and I defend the model when the CFO pushes back on my assumptions. That exposure happens in year one at a boutique. It happens in year six at a Big 4.

Your firm does turnarounds. What does that mean in practice?

A company is losing money, running out of cash, or both. They hire us to figure out why and fix it. "Fix it" usually means: identify the 5 to 10 things that are bleeding cash, build a plan to stop the bleeding, and then stay for 6 to 12 months to make sure the plan actually gets executed. That last part is the difference between boutique turnaround work and Big 4 strategy work. Strategy firms build the plan and leave. We build the plan and stay. We're in the building. We're in the weekly ops meetings. We're on the plant floor arguing with the plant manager about changeover times and scrap rates. The joke in our firm is that we're consultants who get their hands dirty. The reality is that turnaround work requires it because the companies we work with are usually too broken to execute a plan without someone standing next to them.

I'll give you a recent example. We were hired by a mid-size packaging manufacturer, about $180 million in revenue, three plants, headquartered in Ohio. They'd been losing money for two straight years. EBITDA was negative $4 million. The PE firm that owned them brought us in with a simple mandate: get this company to breakeven within 12 months or we're shutting it down. That's the stakes. Not "how do we grow?" Not "what's our five-year strategy?" Will this company exist in a year?

I spent the first two weeks in the plants. Walking the floor, talking to shift supervisors, pulling production data. The problems were, as they usually are, both obvious and invisible. Obvious: one of the three plants was running at 61% capacity utilization. That's a building that's 39% empty but still costs money to heat, insure, and staff with a skeleton maintenance crew. Invisible: the scheduling system across all three plants was a spreadsheet that one guy named Dave maintained, and Dave was very good at his job, but Dave had been doing it the same way for 14 years and the business had changed around him. Product mix had shifted from high-volume commodity packaging to lower-volume specialty runs, and the scheduling logic hadn't adapted. They were scheduling a specialty run the same way they scheduled a commodity run, which meant changeover times were killing them. Average changeover was 3.2 hours. Industry benchmark for their equipment was 1.4. They were losing 1.8 hours per changeover, and with 6 changeovers per day across two plants, that's 10.8 hours of lost production daily. Multiply by their average margin per production hour and that's roughly $8,500 a day in lost contribution margin. $8,500 a day because nobody had rethought the scheduling logic since 2010.

Did you fix it?

We got changeover down to 1.9 hours within four months by implementing a modified SMED methodology and resequencing the schedule to cluster similar runs. We closed the underperforming plant and consolidated production into two facilities. We renegotiated three supplier contracts and reduced raw material costs by 7%. Total annualized impact: $11.2 million in cost reduction and margin improvement. The company went from negative $4 million EBITDA to positive $6.8 million in 14 months. The PE firm kept the company. 340 people kept their jobs. Well, 290. We had to cut 50 positions when we closed the third plant. That's the part that sits with me. The $11.2 million and the 50 people who lost their jobs are the same decision. You can't do turnaround work and pretend that cost reduction is an abstraction. It's people. Dave, the scheduler, kept his job because we needed his institutional knowledge. But the three maintenance workers at the closed plant, I met all of them, and they were good at their jobs, and they lost those jobs because the math said the plant should close. I made that recommendation. The math was right. The recommendation was right. And three people whose names I know are looking for work because of something I put on a slide.

How is boutique consulting different from Big 4 day to day?

Smaller teams, deeper engagement, less polish. A Big 4 team on a $180 million company would be 6 to 8 people. Our team was three: me, a manager named Sonia, and an associate named Drew. Three people doing the work of six means everyone does everything. I'm not above pulling data from an ERP system. Sonia builds models. Drew presents to the plant managers. There's no hierarchy of task allocation. You do what needs doing. The trade-off is support infrastructure. Big 4 firms have research teams, design teams, knowledge management databases, proprietary benchmarking data. We have Google, industry reports we buy one at a time, and our own experience. The slides are uglier. The analysis is often better because the people doing the analysis are the same people who saw the plant floor, which means the numbers have context. When I model a changeover improvement, I'm not using a benchmark from a database. I'm using the number I observed standing next to the press operator watching him retool the die set. That specificity is worth something. It's worth a lot, actually. It's why clients hire a 40-person firm instead of a 40,000-person firm.

What about consulting do people get wrong?

They think we're strategists. We're therapists. Maybe 30% of my job is analytical. Finding the problem, modeling the solution, building the business case. The other 70% is managing human beings through change they didn't ask for and don't want. The plant manager who's been running his facility for 20 years and now a 36-year-old from Boston is telling him his changeover process is broken. The CFO who hired us but didn't tell his COO, so the COO is actively undermining the engagement. The PE firm that wants results in 90 days but won't approve the capital expenditure needed to achieve them. Every engagement has a client politics layer that's invisible from the outside and consumes most of the energy on the inside. My analytical skills got me hired. My ability to sit in a room with a hostile plant manager and make him feel heard and then slowly bring him around to a new way of thinking is what keeps me employed. Business school doesn't teach that. Operations didn't teach that. I learned it by getting it wrong for two years and watching Sonia, who's better at it than I am, do it right.

You were in nonprofit before Wharton. That's an unusual path into MBB.

I managed education programs at a mid-size nonprofit in Philadelphia. We ran after-school programs in 23 schools across the city. My job was to oversee program delivery, manage a team of 12 site coordinators, and report outcomes to funders. The salary was $54,000 after four years. I loved the mission. I was very good at the work. The problem was that I kept hitting a wall where the things I wanted to change required resources and influence I didn't have. I'd write a grant proposal to redesign our tutoring model based on data showing the current model wasn't working, and the executive director would say "we can't change the model because the funder wants the current model." The funder wanted the model that produced the metrics they could put in their annual report, regardless of whether those metrics reflected actual student outcomes. I spent four years trying to change things from inside a system that was structurally incentivized not to change. That's what pushed me toward business school. Not consulting specifically. Business school. I wanted tools.

MBB recruiting happened at Wharton the way MBB recruiting happens at every top MBA program: relentlessly. The firms are on campus from orientation week. They sponsor events, host dinners, run coffee chats, and assign alumni mentors. By the time first-round interviews happen in January, you've had 20 to 30 touchpoints with each firm. It's a machine. I went through the machine because the salary was $190,000 all-in for a first-year associate and I had $148,000 in MBA debt and a nonprofit savings account that contained roughly $3,200. The math was very simple. I needed money. MBB pays money. Whatever complexity I wanted to add to that decision came after.

What is MBB actually like from the inside?

Fast. Dense. Occasionally brilliant. Mostly exhausting. The best way I can describe it is: imagine the smartest people you went to school with, put them in a room, give them a business problem, and tell them they have six weeks to produce the answer. Now add a partner who changes the question every Friday. Now add a client who doesn't believe the answer. Now add 60-hour weeks as a baseline with spikes to 80 during "work streams" and "steercos" and "pre-reads." The intellectual stimulation is real. The pace is real. The prestige is real. The burnout is also real.

My current case is a healthcare company, about $4 billion in revenue, that wants to enter a new market segment. My team is six people. I'm responsible for the competitive landscape analysis, which means mapping every competitor in the target segment, their market share, their pricing, their distribution strategy, and their likely response to a new entrant. The data sources are: public filings, industry reports from IBISWorld and Frost & Sullivan, expert interviews (we have a service that connects us with industry experts who charge $500 to $1,000 per hour for phone calls), and proprietary data from the client's own market research team. I synthesize all of this into a framework that answers: who are we competing against, what are they good at, and where is the opening?

The work itself is engaging. The problem is that the work exists inside a system that optimizes for client perception over analytical depth. The partner on this case, Martin, is brilliant. He's also managing three other active cases simultaneously, which means he reviews our work in 30-minute windows between calls. He reads the executive summary. He looks at the key exhibits. He gives directional feedback like "make the competitive threat more vivid" or "the client CEO thinks about this in terms of customer segments, not geographies." That feedback is useful. It's also vague enough that I'm interpreting it and hoping I interpreted it correctly, because the next review window is Friday and if I interpreted it wrong, I've wasted a week. This happens roughly every third cycle. I call it "misreading Martin," which is my most consistent failure mode and also the most common failure mode of every associate I know.

$190,000 all-in. Does the money match the work?

On an hourly basis, no. Let me do the math because I've done this math. $190,000 all-in means roughly $165,000 base and $25,000 in performance bonus and signing bonus amortized across the first year. After federal and New York state and city taxes, I take home about $126,000. I work an average of 62 hours a week. That's 3,224 hours per year. $126,000 divided by 3,224 is $39 per hour take-home. If I use the billing rate that the firm charges the client for my time, which is approximately $650 per hour, I generate roughly $2.1 million in annual revenue for the firm. I take home $126,000 of that. So I capture about 6% of the value I generate. My friend Ben from Wharton went to Google as a product manager. He works 45 hours a week, makes $195,000 all-in, and takes home about $54 per hour after California taxes. He captures a smaller percentage of the value he generates because Google's margins are higher, but he works 17 fewer hours per week. On a pure hourly-comp-for-hours-worked basis, Ben is winning. On a career-trajectory basis, it's more complicated. In two years, if I make engagement manager, my comp goes to $300,000 to $350,000. If Ben gets promoted to senior PM, his goes to $240,000. The consulting path pays more at the top but extracts more at every level to get there.

You mentioned the Sunday Scaries spreadsheet. What's driving the anxiety?

Two things. The first is performance ambiguity. At the nonprofit, I knew if I was doing a good job because kids were learning and I could see it. In consulting, I know if I'm doing a good job when the partner tells me I'm doing a good job, and the partner tells me that in a semi-annual review that includes a numerical rating on a scale that nobody fully understands. The rating determines whether I get promoted, which determines whether I stay, because MBB is up-or-out. If I'm not promoted to engagement manager within four years, I'm "counseled to leave," which is consulting language for fired politely. So the stakes of the performance review are: career continuation. And the inputs to the performance review are: the subjective impressions of partners I've worked with, filtered through a calibration process where they rank me against every other associate in my cohort. I'm being compared to people I've never met on cases I've never seen, and the outcome determines whether I have a job next year. That creates a specific kind of anxiety that's always on. Not acute. Just always on. Like a hum.

The second thing is impact uncertainty. At the nonprofit, the impact was small but real. A kid who couldn't read at grade level could read at grade level. That's a thing that happened because of a program I managed. In consulting, I produce recommendations. The client chooses whether to implement them. Most of the time, they implement about 40 to 60% of what we recommend. Sometimes they implement none of it. I spent eight weeks last year building a distribution network optimization for a consumer goods company. The recommendation would have saved them $14 million annually. They didn't implement it because the COO who championed the project left the company and his successor had different priorities. Eight weeks. My nights. My weekends. Eighty hours of modeling. $14 million in identified savings. And it's sitting in someone's SharePoint collecting dust. That doesn't happen at a nonprofit. At a nonprofit, if you run the tutoring session, the kid gets tutored. The line between effort and outcome is short and visible. In consulting, it's long and often invisible.

What would you tell someone considering MBB?

That the exit opportunities are the actual product. Nobody talks about this openly, but it's the architecture of the whole system. MBB hiring is built on the assumption that 80 to 85% of people will leave within five years. The firms know this. They plan for it. The alumni network IS the business development pipeline, because an ex-McKinsey VP of Strategy at a Fortune 500 company is more likely to hire McKinsey when she needs a consultant. So the firms invest heavily in making the two-to-five-year experience valuable enough that people leave with positive feelings and a strong resume. The training is real. The exposure to C-suite problems is real. The brand on your resume opens doors that would otherwise be closed. But you're not building a career at McKinsey. You're building a resume at McKinsey. The career happens after. Most of the people I started with are already gone. My cohort was 48 associates. Fourteen remain after three years. The other 34 went to: tech (12), PE/VC (8), corporate strategy roles (6), startups (5), and back to grad school or "figuring it out" (3). They're mostly happy. They're also mostly exhausted in a way that took six months to recover from. Consulting is a sprint that the firm packages as a career. If you go in knowing it's a sprint, you'll be fine. If you think it's a career, the up-or-out moment will feel like a betrayal.