A Typical Day at McKinsey: What Consultants Actually Do
You’ve cleared the PSG. The offer has landed. So what does actually showing up at McKinsey look like? Here’s an honest, hour-by-hour look at a consultant’s working day — built from first-hand accounts and industry research.
Understanding the rhythm of a consultant’s working day is useful long before you walk through the door — it shapes how you think about the role, what you’re signing up for, and why the assessment process is designed the way it is.
Here’s an honest look at what a typical working day involves, built from publicly available first-hand accounts and industry research.
The Basics: Hours and Structure
McKinsey consultants typically work 55 to 65 hours per week during active project phases, with the intensity varying significantly depending on where you are in the project lifecycle.[1] Early phases involve scoping and hypothesis-setting; mid-project is where the real analytical grind happens; the final weeks are dominated by polishing deliverables and steering committees.
The week itself follows a distinct pattern. From Monday to Thursday, most consultants are physically at the client site — which often means travel. Friday is typically a remote day, lighter on meetings and used for synthesis, professional development, or catching up on admin. Weekends are generally protected at McKinsey, with Saturday and Sunday work treated as a genuine last resort rather than an expectation.[2]
What the Day Actually Looks Like
On travel days, the alarm may go off well before 6am to catch a morning flight. Consultants use this time to scan emails, flag anything urgent, and mentally map out the day. Arrivals at the client site tend to be between 8 and 9am.
The day usually opens with a short team check-in — 15 to 30 minutes — where everyone clarifies what they’re working on, surfaces blockers, and makes sure workstreams are coordinated. This is where priorities shift if a client has raised something overnight.[3]
The morning block is typically the most productive heads-down time. For a junior consultant or business analyst, this means building spreadsheet models, structuring data, conducting desk research, or drafting slides. The goal is to have something concrete to bring to the client by afternoon.[3]
Late mornings and early afternoons are peak time for client interaction. This might be a working session to walk through preliminary findings, an interview to gather context from a business unit head, or a collaborative workshop. These meetings are where the analytical work either lands or gets challenged — both are valuable.[4]
The afternoon is where raw analysis becomes a story. Consultants review their findings, identify the so-what, pressure-test the logic with their engagement manager, and start shaping the narrative for the next client update. McKinsey places significant emphasis on the “pyramid principle” — leading with the conclusion, then the supporting evidence — so building this skill early matters a great deal.[3]
Before major client presentations, evenings are rarely quiet. Decks get reviewed, numbers get sense-checked, and talking points get refined. Teams often work together through dinner, especially in the final days before a steering committee meeting. Most consultants log off by 8 or 9pm on a normal night, though this can extend significantly during crunch periods.[1][2]
The PSG — McKinsey’s Problem Solving Game — is explicitly designed to simulate the kind of thinking required on the job. The ability to work quickly through ambiguous data (Redrock), manage competing variables under pressure (Sea Wolf), and make sound judgement calls with incomplete information (SFL) maps directly onto what McKinsey consultants do every day.
What Makes It Hard
It’s not just the hours. The cognitive load of consulting at McKinsey is genuinely high. You’re expected to get up to speed on an unfamiliar industry quickly, form a credible view, and present it to senior executives — sometimes within weeks of starting a project. Junior consultants often describe the learning curve as steep but deliberate: the firm invests heavily in training, mentorship, and structured feedback cycles.
The travel is also a factor that surprises many new joiners. Spending three or four nights a week in a hotel, away from friends and routines, takes adjustment — even when the client is in an interesting city.
What Makes It Rewarding
Equally, the pace of exposure is unlike most careers. In two years, a McKinsey consultant might work across three industries, several countries, and a dozen different business challenges. The analytical toolkit you build — structured problem decomposition, data-driven storytelling, stakeholder communication — stays useful for the rest of your career, wherever you end up.
Most former consultants describe the intellectual environment as the defining draw: surrounded by people who are genuinely sharp, working on genuinely consequential problems, with access to data and decision-makers that most analysts never see.
The Bottom Line
A day at McKinsey is structured but demanding, varied but intense. If you’re preparing for the PSG assessment, understanding what consultants actually do can sharpen your motivation — and it can also help you perform better on the assessment itself. The skills the game tests aren’t arbitrary. They reflect exactly the kind of thinking McKinsey needs on day one.
Preparing for the McKinsey PSG?
Practice all four current scenarios — Redrock, Sea Wolf, SFL, and Ecosystem — with full simulations and worked explanations.
Sources
- Day in the Life of a McKinsey Consultant — CaseBasix
- Work-life Balance at McKinsey — MConsultingPrep
- A Day in the Life of a McKinsey Management Consultant — Leland
- A Day in Life of Management Consultant: Timeline & Routine — MConsultingPrep
- Why Consultants at McKinsey, BCG and Bain Work Long Hours — CaseCoach
- A Day in the Life of a Management Consultant — Hacking the Case Interview