A Day in the Life of a MBB Analyst 2026

A first-year analyst at McKinsey, BCG, or Bain spends most days on one piece of one client project: analysis or client interviews in the morning, problem-solving with the team in the afternoon, and slides in the evening. The week below is a full travel week at the client, which is the heavy end; many teams now travel two or three days a week, and some work mostly remotely.

I'm Stephen Turban, founder of WSG and a McKinsey & Company and Harvard alum. I went through McKinsey's on-cycle recruiting myself, and I've since guided dozens of students through it.

Most undergrads at McKinsey start as Business Analysts, and the role, pay, and path to getting hired are covered here. If this day sounds like the job you want, the full playbook for landing an MBB offer is here.

How a Client Project Is Set Up

A client project is called a study at McKinsey, a case at Bain, and usually a project at BCG. Each project is one client question, split into pieces called workstreams, and the analyst owns one of them. A client might ask why its costs are higher than a competitor's, whether to enter a market, or which business to sell, and the firm puts a small team on it, usually three to six people for two to six months at McKinsey.

The team has three layers:

Partner (and at McKinsey, the associate partner one level below): owns the client relationship, sells the work, and guides the team in its problem-solving sessions. Partners travel more than any other level because they're visiting several clients.

Engagement manager (project leader at BCG): runs the project day to day, manages the team, gives feedback on the work, and is the client's main contact.

Analysts and consultants: gather the data, build the models, and make the pages. At McKinsey, an Associate (usually post-MBA) owns a larger workstream and guides the Business Analysts.

The manager splits the client's question into workstreams, and each workstream has its own interviews, data, and pages in the final presentation. On a cost project, the split might look like this:

The analyst owns a whole workstream, here manufacturing, alongside consultants who own the others, all under one engagement manager.

The team also works from a hypothesis, meaning an early best guess at the answer that the data then tests, so you form a view before all the data is in. Say the question is why manufacturing costs are high. Your first guess might be that one plant runs too much overtime. Every interview and data request now has a purpose, which is checking whether the overtime idea holds. If the plant manager says overtime is normal but scrap rates doubled last year, the hypothesis changes, and so does next week's plan.

Monday: Travel Day on a Client-Site Project

On a travel project, Monday starts with an early flight and ends with more work at the hotel. In February 2026, a former McKinsey consultant who started as a business analyst described a project week on Leland as three kinds of day: travel days on Monday and Thursday, client-site days on Tuesday and Wednesday, and an office day on Friday. On that project the whole travel-day morning went to getting there, because the client was a two-hour drive from the airport, so the workday proper started on site at 1 p.m. and ran late into the evening at the hotel:

In this write-up, the travel day and the client-site day both end with work until 11:30 p.m., while the office day ends at 5:45.

That project "involved more travel than average," and the client was in a remote area. Most McKinsey teams now travel two to three days a week instead of the old Monday-to-Thursday pattern, and how much you travel depends mostly on the client. Bain and BCG both describe their entry-level roles as involving regular travel to client sites.

Once you're on site, Monday afternoon starts with lining up goals and tasks with the manager. The week usually runs toward a client meeting near its end. The biggest client meeting is the steering committee, or SteerCo: the senior client executives overseeing the project, who review the findings and agree on next steps. On some projects it meets every week, and StrategyCase calls it "the real deadline"; on others, an ex-McKinsey coach on PrepLounge says it typically meets every few weeks. Either way, the week's plan is built around what has to be ready for that meeting: which pages, which interviews, and which data.

Tuesday and Wednesday: Analysis by Day, Slides by Night

A client-site day typically runs from about 8:30 a.m. until somewhere between 8 and 11 p.m., with interviews and analysis during the day and slides at night.

The morning check-in. The team meets first thing, often at 8:30, to go over the day's priorities and flag anything that's stuck.

Interviews. Talking to client staff is a big part of the analyst's day, because interviews tell you what the numbers can't. You might sit down with a plant manager, a regional sales lead, or a finance director, with your hypothesis and a short list of questions, to pressure-test what the data is telling you. Some days also include a call with an expert inside the firm who has worked on a similar problem.

Analysis. Much of the morning usually goes into Excel. The client's data comes in, and you turn it into something that answers your piece of the question: cost per unit by plant, margin by customer, or headcount by function, ending in a chart that shows one finding. A data request is easier to analyze when it names the exact cut you need, such as monthly cost by plant split into labor, materials, and overhead.

The problem-solving session. On many days, the team sits down with the manager and often the partner to go through the pages so far and test the argument. In the Leland write-up, it runs from 1 to 2 p.m. with the associate partner. This is where your work gets questioned. If the partner asks why one plant's overtime is high and you don't know, that question becomes your next interview or data request.

The pages. The evening goes into turning the day's work into slides. Three ideas shape how the firms build them:

• The ghost deck: early in the project, the team writes the page titles for the whole presentation with the pages mostly empty, so everyone can see the argument before the analysis exists. Management Consulted describes it as a "barebones outline" built before "filling in the analysis." Your workstream shows up as a few titles over empty pages, and your job is to prove them or replace them.

• Sentence titles: each page's title states its finding in a full sentence, so a client can follow the presentation by reading the titles alone. "Plant costs by region" is a label. "The Midwest plant costs 22 percent more per unit than the other three, and overtime explains most of the gap" is a finding.

• Answer first, and MECE: the pyramid principle, developed by Barbara Minto at McKinsey, puts the answer first, then the few reasons that support it, then the data behind each reason. Those reasons should be MECE (pronounced "mee-see"), short for mutually exclusive and collectively exhaustive: they don't overlap, and together they leave nothing out. If your reasons for high plant costs are overtime, scrap, and "labor," the list fails, because overtime is labor.

Here is the plant example laid out as a pyramid:

The title states the answer, the reasons under it don't overlap, and each reason rests on its own data and interviews.

The client-site day in the chart under Monday shows what a heavier day looks like: the author led a client workshop in the afternoon, then had dinner with the associate partner and team before working until 11:30. When the steering committee is on Thursday, Wednesday night is usually the long one: StrategyCase's Bain guide says "the night before a client steering committee is long; the day after it is often short."

Thursday: Client Meetings and the Trip Home

Thursday is often the day the client sees the work, and on a travel project it ends with the trip home. On a SteerCo week, that's the steering committee itself. Between steering committees, the team meets the client in smaller working sessions to share progress, confirm assumptions, and collect new data.

How much you present to the client yourself varies by firm and project, and at McKinsey it can start earlier than your title suggests. StrategyCase writes that at McKinsey "you will present to executives far sooner than your title suggests you should," and a Bain associate consultant on Bain's careers blog describes presenting "our work to partners and clients." StrategyCase's Bain guide, though, says that in client working sessions associate consultants "observe and take notes," and Hacking the Case Interview's BCG guide says "a junior consultant never advises a client alone."

Thursday is also the second travel day of a travel week. The Leland write-up notes that on Thursdays "the schedule shifts slightly to accommodate the drive back to the airport."

Friday: The Office Day and Your Next Project

Friday is usually a shorter day at your home office, often finishing by 5 or 6 p.m. In the chart under Monday, Friday is the office day, with the morning on internal prep or client video calls and the afternoon on scheduling and networking, then wrapping up and out the door by about 5:45.

You don't stay on one team for long. A staffing coordinator or staffing team matches available consultants to new client projects, and the partner running a project lobbies for the people they want. In the Leland write-up, when a project is nearing completion, Friday afternoons can include staffing calls with the lead partner or engagement manager about what comes next. Between projects, consultants are on what firms call the bench or the beach, doing training, helping with proposals, and looking for the next project.

What a Remote Day Looks Like

On a remote day, the analyst does the same work from home, with the meetings on video. Because many teams now travel only two or three days a week, many weeks mix client-site days like the ones above with remote days and a Friday at the home office. Hacking the Case Interview says remote days are now "the most common type of day for many teams," and its sample remote day at McKinsey runs like this:

• 8:30 a.m.: team check-in on the day's priorities and anything that's stuck.

• 9:00 a.m.: focused analysis, often building or refining an Excel model on client data.

• 11:00 a.m.: problem-solving session with the engagement manager and partner.

• 1:00 p.m.: building pages based on what the team decided in that session.

• 3:00 p.m.: a working session with the client or a call with an internal expert.

• 5:00 p.m.: pulling the day's findings together and updating the storyline.

• 6:30 p.m.: an end-of-day update to the engagement manager on your workstream.

• 9:00 p.m.: a final round of edits, if a client deliverable is due the next morning.

What Changes Between McKinsey, BCG, and Bain

McKinsey, BCG, and Bain staff their teams differently (globally at McKinsey, regionally at BCG, and locally at Bain), and that mainly changes how far you travel and who you work with. The firms also hire under different titles, and how early you present to the client varies by firm, as the Thursday section describes. McKinsey hires undergraduates as Business Analysts, BCG as Associates, and Bain as Associate Consultants.

StrategyCase explains what each staffing model means for you:

• McKinsey: teams can be "pulled together from several countries," so you get more variety and more flights.

• BCG: it "sits in between, leaning regional while still sending people further afield to keep teams staffed."

• Bain: its "more local model tends to keep teams close to the home office," which StrategyCase says means "closer to home, a tighter office network, and generally easier work-life balance."

StrategyCase also says these are "general tendencies, not hard rules," and they vary by office.

How the Hours Add Up Across the Week

A first-year analyst on a project typically works about 55 to 65 hours a week, and Excel analysis and building slides tend to take the biggest share of it. That's Hacking the Case Interview's range for McKinsey Business Analysts; StrategyCase puts a normal McKinsey week at 55 to 70 hours, and Hacking the Case Interview puts BCG at 50 to 70. Weekends are mostly protected, though a bad week before a steering committee can take part of a Sunday. Between projects, hours often drop into the 40s.

Hacking the Case Interview's author, a former Bain manager, estimates how a junior consultant's 65-hour McKinsey project week splits, "based on the projects I have seen and coached on":

In this one estimate, Excel and slides take half the week, while client meetings and interviews take 15 percent.

How AI Tools Changed the Analyst's Day in 2026

At all three firms, AI tools now speed up searching past work and drafting first versions of slides and models, while the interviews, the problem-solving, and the judgment about what matters stay with the analyst.

McKinsey: its platform, Lilli, pulls together the firm's "40-plus knowledge sources," and McKinsey reports "up to 30 percent time savings in searching and synthesizing knowledge." StrategyCase says AI has taken over tasks like "reading 40 documents to find the three that matter" and "building the first ugly version of a model."

BCG: consultants use Deckster, a slide editor trained on 800 to 900 slide templates. Business Insider reported in 2025 that about 40 percent of associates use it weekly, and that its "review this" button grades slides "based on best practices used by midlevel managers and leaders."

Bain: every employee has ChatGPT Enterprise, and Bain built Sage, "our in-house AI platform powered by ChatGPT," to search the firm's knowledge, according to Bain's careers blog. Its internship page says the role "requires the regular use of generative AI tools and Bain's proprietary digital platforms to support analysis."

StrategyCase sums up the change as "AI drafts, junior consultant edits and defends," and advises treating AI output as a first draft to question. That leaves the analyst checking what the tool produced and defending it with the client, because, as the same guide puts it, "Lilli does not sit in the room when a CFO pushes back."

What the Summer Internship Looks Like

The MBB internship is the analyst job on a shorter clock, with one workstream on a real client team. McKinsey's Business Analyst Intern posting says you "join a client service team for 8-10 weeks." BCG lists its Summer Associate program at about 8 to 12 weeks between June and August. Bain's internship page doesn't give a length, but says the summer "begins with one week of training after which point you'll be staffed on a real case team," where you'll "own a distinct piece of that project."

Bain's page also says the internship "may lead to invitation for interviews or even an offer to join us as an associate consultant." To compare programs, see WSG's 15 best consulting internships for undergraduates, and for when each firm recruits, the consulting recruiting timeline for undergrads.