MASTERS TO CONSULTING
You open a consulting firm's careers page.
"Problem-solving."
"Client impact."
"Strategic recommendations."
It sounds impressive.
It also tells you surprisingly little about what you might do at 10:17 on a Tuesday morning.
Consulting becomes much less mysterious when you zoom in.
Your day may begin with a question nobody has fully answered
Imagine your client is losing customers.
The engagement manager does not hand you a neat assignment saying, "Calculate X."
You may get something closer to:
"Can we figure out what is driving churn before Thursday's client meeting?"
Now the work begins.
You might break the problem into hypotheses, request data, interview someone from the client's sales team, analyze customer segments, build a chart, discuss what it means with your team, revise the chart, and eventually help turn it into a recommendation.
That entire chain can happen around one tiny part of a much larger engagement.
The analysis is only the middle.
For a closer look at one common entry-level role, read McKinsey Business Analyst: What is It & What Do They Do?.
Your master's probably taught you the first half... not necessarily the second
Graduate school can prepare you surprisingly well for ambiguous analytical work.
You have probably:
- started with incomplete information
- researched unfamiliar topics quickly
- worked through messy data
- defended an interpretation
- presented to someone who knew more than you
Familiar?
There is a catch.
Consulting compresses the cycle and moves the endpoint.
In university, the goal may be to demonstrate that your analysis is rigorous.
In consulting, the analysis often has to answer a decision.
The client eventually asks, "So what do we do?"
That shift changes how you work.
The slide is not decoration... it is part of the thinking
Master's students sometimes imagine analysts spending all day in Excel and senior consultants doing the "strategy."
The boundary is blurrier.
Even junior team members often need to turn analysis into communication.
| What you may expect | What actually happens | Why it matters |
|---|---|---|
| Analyze the data | Decide which analysis matters | Prioritization starts early |
| Build a chart | Make the implication obvious | The slide carries an argument |
| Send work upward | Discuss and defend your logic | You are part of the synthesis |
| Learn the industry first | Learn while solving the problem | Speed matters |
You may spend an hour changing three words on a slide title because those three words determine what the reader takes away.
That can feel absurd.
Until you realize the title is the recommendation.
To see how this rhythm develops over a broader period, read What to Expect in Your First Year as a Consultant.
Then there is the part the job descriptions barely show
Feedback.
Your manager reviews the page.
The chart changes.
The hypothesis changes.
A client conversation makes yesterday's analysis less relevant.
You rebuild.
Good work is often rewritten work.
That is one of the biggest transitions from graduate study.
You are no longer optimizing a piece of work primarily around your own analytical process.
You are contributing to a team product that keeps moving.
So what does an entry-level consultant actually do?
Analyze, yes.
But also prioritize, synthesize, communicate, revise, and repeatedly ask what the work changes.
Your master's may have trained you to find the answer.
Consulting adds another question.
What happens because you found it?