Your First Year in Consulting: What Actually Matters and What Doesn't

The first three months of consulting are the most disorienting part of the career. You are sitting in a high-prestige seat, getting paid well, and feeling — most of the time — like the least-prepared person on the team. The skills that moved you through case interviews are not the skills that move you through your first six months. The interview is a closed test with one interviewer; the job is an open-ended test with five judges, none of whom will tell you exactly what they are looking for.

Most of the public advice on first-year consulting is some version of "work hard, be humble, take feedback." That is correct and useless. What follows is the version that matters — what your review actually gets scored on, what causes the most weak reviews, and how to make staffing decisions when nobody will tell you that staffing decisions are the lever they look like.

What first-year reviews actually score

The official rubric varies by firm and tenure but the substance overlaps heavily. Five things drive the bulk of your rating:

1. Reliability — does work come back when you said it would, in the shape it should

This is the single largest driver of first-year ratings and it is almost entirely under your control. A first-year who delivers a competent analysis on the morning it was promised, in the format the manager asked for, outscores a first-year who delivers something more brilliant two days late or in a different format than requested. Reliability compounds. Unreliability compounds faster.

2. Clarity — can the manager read your work without rewriting it

A clean exhibit, a tight summary, a half-page memo that lands on the question your manager asked. The opposite — work that requires the manager to do interpretation labor on top of review labor — is the most common cause of "needs development" comments in first-year reviews. Managers will not say "your analysis was fine but I had to rewrite the deck." They will say "needs to improve communication."

3. Ownership — do you proactively close loops

The shift from analyst to consultant is the shift from "I did what you asked" to "I did what you asked, I noticed the implication for the next question, I checked with you on whether to pursue it, and I have a draft." Ownership is the skill that distinguishes a strong first-year from a competent one.

4. Judgment under ambiguity

Most first-year work has at least one moment where the right next step is not specified. The choice in that moment — push forward with a decision, ask the manager, escalate to the partner, slow down to check — is what your manager is reading whether they say so or not. Defaulting to "ask the manager" every time is a weak signal. Defaulting to "decide and proceed" every time is a different kind of weak signal. The judgment is reading which mode the moment actually calls for.

5. Team presence

Are you the person the team is glad to staff again. This sounds soft and is rated hard. Team presence covers everything from showing up prepared to meetings to being calm when the client is hostile to not creating drag inside the team. A first-year with perfect technique and bad team presence will get rated lower than a first-year with average technique and strong team presence.

The most common first-year failure modes

Asking when you should have proposed

Every first-year does this. You hit an ambiguous point and you Slack the manager. The instinct feels safe — you are checking before going off in the wrong direction. From the manager's side, it reads as "this person makes me do their thinking." The fix is to draft a proposal first, then ask. "I think we should approach this by X. Reasoning: A, B, C. Are you aligned, or would you push a different direction?" same question, completely different signal.

Proposing when you should have asked

The opposite failure. You hit a genuinely ambiguous point, decide it on your own, and spend three days going in a direction the manager would have redirected if asked. The trigger for asking instead of proposing is usually a non-obvious one: when the cost of going the wrong direction is more than half a day's work, ask; when it is less, propose.

Over-engineering early work

First-years routinely build a 40-cell Excel model when a back-of-envelope number would have answered the question. The manager wanted to decide whether to pull a thread. They got a deliverable that takes 25 minutes to interpret. The work was excellent. The work was wrong for the moment.

Treating reviews as a black box

Reviews are a noisy signal but they are not random. Ask explicitly: "What is one thing you would have me change before our next checkpoint?" And then change it visibly. Showing motion between feedback and the next deliverable is worth more than the average first-year realizes — it is the most direct signal that you are coachable, and coachable is the most undervalued word in the rubric.

Imposter syndrome in the first six months

Almost every first-year goes through it. The usual shape is "everyone here is smarter than me, I'm faking it, the next deliverable will expose me." The feeling is real. The information content is close to zero — it appears in candidates who are objectively doing well and in candidates who are objectively struggling at roughly the same rate.

The fix is not affirmations. The fix is to calibrate against artifacts. Pull up the work you actually produced last month. Compare it to the work you produced in week one. The delta is the data; the feeling is not. If the artifacts say you are getting better, you are getting better, regardless of how the inside of your head currently sounds.

Staffing decisions in your first year

When you have optionality, use it

At most firms, your first one or two staffings are assigned. After that you have at least some choice. The candidates who consistently land good year-end reviews tend to pick deliberately:

• One project where the manager is a known developer of first-years — ask your buddy or mentor, the names are widely known inside the firm.
• One project in a sector you might want to specialize in — early exposure shapes which partners pull you onto future work.
• One project that stretches a skill you are weakest at — controlled difficulty in a year where mistakes are forgiven is high-value.

When you don't have optionality, protect your time

Some first-year staffings are non-negotiable and some are bad. The bad ones — over-staffed teams, partners with no time to develop you, topics with no obvious next-engagement upside — are not career-ending, but they are also not your job to optimize. Deliver reliably, do not over-invest, and protect sleep. The next staffing matters more.

The one-sentence summary

Most of what determines a strong first year is habits that are easy to describe and hard to execute: do the work on time in the shape requested, close loops without being asked, match your "ask vs propose" mode to the moment, calibrate against artifacts not feelings, and pick your staffing when you can. None of this is glamorous. All of it is what the rubric is actually scoring.