A junior consultant’s first engagement counts more than they think. It shapes their internal reputation, feeds into their first review and influences their next assignments. Yet a manager’s expectations of a junior are rarely spelt out: reliability, file management, quality of notes, the ability to flag a problem early. They are often discovered by getting them wrong. This article gathers these implicit expectations, describes the first days at the client, and lists the mistakes that cost dearly, so that you can approach your first engagement with a few solid reflexes.
What the manager expects from a junior
A manager does not ask a junior to have brilliant ideas in the first week. Above all, they expect to be able to trust them. In practice, this covers five expectations.
Reliability. A figure passed on by the junior must be correct, or come with a clear caveat. An analysis announced for Tuesday must arrive on Tuesday, or a delay must be flagged on Monday.
Reasonable autonomy. The manager does not have time to explain everything. They expect the junior to look for the answer themselves first (in documents, with a colleague, in the data), then ask precise questions.
Rigour in form. Aligned slides, consistently rounded figures, sources stated, files named properly. These are details, but they save the manager from rereading everything.
Transparency. A problem flagged early gets solved; a hidden problem turns into a crisis the day before a committee.
Attitude. Availability, good humour in tense moments, respect for the client’s teams. An engagement team lives together for weeks, and the atmosphere matters.
These expectations echo what our article on a junior consultant’s week describes: reputation is built in daily work, much more than at the steering committee.
The first days at the client
The first days of an engagement are dense, and a few simple reflexes save a lot of time.
Read everything that exists before you arrive. The proposal, documents sent by the client, notes from kick-off meetings. The manager will appreciate that you know the scope and vocabulary from day one.
Understand the engagement’s question. Ask the manager what central question the engagement must answer, and which part falls to you. Write it down in one sentence at the top of your notebook.
Identify the stakeholders. Who at the client provides the data? Who decides? Who can block? A map of stakeholders, however rough, avoids many missteps.
Set yourself up properly. Access to the client’s tools, to shared folders, to security and confidentiality rules. Follow these rules strictly: a confidentiality incident on your first engagement is hard to recover from.
Observe the codes. Hours, dress, tone of exchanges, meeting customs: every client has its culture. The manager and more senior consultants are the best guides.
Keeping your files and notes
This is the least glamorous aspect of the job, and the one on which juniors are most often judged.
Files. An engagement produces dozens of files: data extracts, Excel models, successive versions of slides. A few rules avoid chaos:
- an explicit, dated file name, following the team’s convention;
- a working version and a validated version, clearly distinguished;
- in models, a tab documenting sources and assumptions;
- readable formulas, without hard-coded values pasted in the middle of calculations.
The goal is that a colleague can pick up your file without calling you. If you fall ill the day before a committee, the team must be able to carry on.
Interview notes. After each interview with the client, write the minutes the same day: participants, key points, figures quoted, documents promised, next steps. Share them with the team. These notes often become the raw material of the analyses.
Tracking requests. Keep a list of data requested from the client, with the request date, the contact and the date received. This table will let you chase at the right time and explain a delay.
Holding useful check-ins
Check-ins with the manager, often daily, are a key moment. A useful check-in is short and helps the manager decide.
A simple structure works well:
- What has been done, in one or two sentences, with the main result.
- What it suggests: a first conclusion, even a provisional one.
- What is blocking: a data problem, an unanswered question, a disagreement with a stakeholder.
- What you propose to do next, and what you need.
Bring material: two or three working slides, even imperfect, are better than a long account. And note the manager’s feedback during the check-in, so as not to ask for it again.
Asking for help without losing face
Many juniors hesitate to ask for help, for fear of seeming less competent. It is a mistake: a manager prefers a question asked early to a wrong analysis delivered late.
A few rules for asking effectively:
- look for the answer yourself first for a reasonable time, and note what you tried;
- ask a precise question, with your hypothesis: “I think the gap comes from a change of scope during the year; should I restate the data or flag it?”;
- choose the right person: a more senior consultant for a technical question, the manager for a question of direction;
- group non-urgent questions for the daily check-in;
- say thank you and reuse: an answer obtained must serve you afterwards.
Flagging a mistake you made follows the same logic. Say so quickly, explain the impact and propose a fix. Managers remember how a junior handles a mistake much more than the mistake itself.
What the end-of-engagement review looks at
At the end of the engagement, the manager, and sometimes the partner, writes a review. Our article on reviews in consulting and the up-or-out rule describes the full cycle; for a first engagement, the criteria considered are mainly:
- the quality and reliability of analyses;
- the quality of deliverables: slides, notes, models;
- autonomy and the ability to improve over the engagement;
- the relationship with the client and the team;
- involvement, particularly in crunch times.
Ask for feedback halfway through, without waiting for the final review. An informal fifteen-minute chat lets you correct course in time. And at the end, note for yourself what you learnt and what you want to work on in the next engagement: it will serve in the discussion with your mentor and for your staffing preferences, described in the article on assigning consultants to engagements.
Also remember to keep a record of the engagement for your CV: the client’s industry, the scope, your workstream, the results obtained, in anonymised form. The strategy consultant CV template shows how each engagement is summed up in one bullet, and the AMOA consultant template how to describe a long engagement step by step. The ConseilCV editor lets you add these lines as you go, without touching the layout, with a PDF ready for a review or an application.
Frequently asked questions
Should you work late from your first engagement to make a good impression?
No. What matters is the quality and reliability of the work. Staying late for no reason impresses no one; being available in crunch times, on the other hand, shows your involvement.
What if you do not understand the engagement’s question?
Ask the manager to rephrase it, in the first days. A question at the start is better than a week of work in the wrong direction.
Can you give your opinion to the client on your first engagement?
On your workstream and in working meetings, yes, carefully and after discussing it with the manager. Important messages to the client generally go through the manager or the partner.
How do you handle a disagreement with your manager?
Express it one to one, with facts, and propose an alternative. If the manager keeps their position, apply it. Well-expressed disagreements are generally appreciated.