The ApprenticeRoute

Your first performance review

My first performance review lasted about twenty-five minutes. My manager was kind, slightly rushed, and told me I was doing well. I said thank you. I walked out with no idea whether that was true, what I should do differently, or whether "doing well" meant anything at all.

It took me two more cycles to work out that a review is not a thing that happens to you. It's a meeting you can shape, and at 19, in your first professional job, nobody expects you to know that.

How pay reviews and bonuses work covers the machinery — the annual cycle, calibration, how ratings and money actually get decided. This article is about the meeting itself, and about being 19 in it.

First, you have two review systems

The thing that confuses every apprentice in their first year: there are two separate review processes with your name on them, run by different people, for different reasons.

The employer's performance review. Run by your line manager, on the company's annual cycle, about your job. Feeds into ratings, pay and progression. Exactly the same process every other employee goes through.

The tripartite apprenticeship review. Run every couple of months by your training provider, with you and your manager, about your apprenticeship: your off-the-job hours, your progress against the standard, whether the job is giving you the experience you need. Explained properly in how work-based learning actually works.

They're easy to muddle, particularly because both involve your manager saying how you're getting on. The distinction that matters: the tripartite review is where you raise problems with the programme — not getting study time, work that's drifted away from your standard, drowning. The performance review is where your job gets assessed.

Raising an off-the-job hours problem in your performance review is a category error that makes it look like an excuse. Raising it in the tripartite review, where a provider with a funding interest is sitting at the table, gets it fixed.

Before the meeting

Most first reviews are underprepared on both sides. Yours doesn't have to be.

Have your year written down. Six to ten specific things you did, with outcomes attached. Not "helped with the monthly process" — "took over the reconciliation, which now takes half a day less". If you've been keeping a running note, this is a ten-minute job. If you haven't, it's a painful evening with your calendar and sent items, and it's the reason to start the note now.

Reread your objectives, if you have any. If nobody set you any, note that as something to fix rather than something to be defensive about.

Bring three questions. This is the part almost nobody does, and it changes the meeting completely. Mine, eventually, were versions of:

  1. What's the one thing I should do differently next year?
  2. What does someone a level above me do that I don't?
  3. Where would you like me to take more responsibility?

Those three turn a twenty-five minute "you're doing well" into something you can act on.

Know what you want to come out with. A specific piece of work, exposure to a particular area, a mentor, a project. If you don't ask, the answer is nothing, and reviews are the one meeting in the year explicitly designed for asking.

What actually happens in the room

Usually: your manager talks through their written assessment, mentions a few things you did well, raises one or two areas to develop, and asks if you have questions. Somewhere between twenty minutes and an hour.

Some are excellent. Plenty are rushed, vague, or clearly written the night before. If yours is one of the vague ones, you can steer it without being difficult:

That last question is the most valuable sentence in this article. Managers routinely soften feedback for junior people and almost always have something more specific in reserve. Asking directly, once, gives them permission.

The apprentice-specific problem: softened feedback

Here's a thing that took me two years to notice.

People adjust their feedback for your age. Not consciously, and not unkindly — but there's a real tendency to grade an eighteen-year-old on a curve, to be pleased that you turned up and were competent, and to hold back the developmental stuff because you're young and they don't want to knock your confidence.

That is a lovely instinct and it is bad for you. Feedback you don't get is feedback you can't act on, and the gap it creates only becomes visible later, when the curve disappears and you're being assessed as an ordinary employee.

The way to get the unsoftened version is to ask for it explicitly:

"If I were a graduate hire with two years' experience rather than an apprentice, what would you be telling me?"

I got noticeably better feedback from the moment I started asking some version of that. It signals that you can handle it, which is most of what's holding them back.

Taking criticism at 19

This is the genuinely hard part, and nothing prepares you for it.

School feedback is about work you produced. Work feedback feels like it's about you — how you come across, whether you're proactive enough, how you handle pressure. And you're hearing it at an age when your professional identity is about four months old, from someone whose opinion determines quite a lot about your life.

What I'd tell my younger self:

Don't defend it in the room. The instinct is to explain the context — you were busy, the brief was unclear, someone else dropped something. Sometimes all of that is true, and saying it in the moment still reads as not listening. Ask questions instead of making arguments.

Ask for a specific example. Not defensively — genuinely. "Can you give me an example of when that came across?" Vague feedback you can't picture is unusable, and a concrete instance usually makes it obvious what to change.

Give it 24 hours before deciding what you think. Almost all critical feedback feels worse on the day and more reasonable on Thursday. Some of it will turn out to be wrong, and you'll be far better placed to say so calmly once you've sat with it.

Separate the signal from the delivery. Some managers are bad at giving feedback. A clumsily delivered point can still be a correct one.

And keep the proportion in mind: your first review is one person's assessment of four to twelve months of a career that will run for forty years, formed when you were nineteen and knew nothing. It is information, not a verdict.

The feedback apprentices actually get

Remarkably predictable, in my experience. Three things come up again and again, and all three are vague enough to be useless until you convert them.

"Be more confident" / "speak up more". The most common by far. What it usually means concretely: contribute at least once in meetings, share work before it's perfect, and stop prefacing everything with "this is probably stupid but". Convert it by asking: "In which meetings specifically? What would you have wanted me to say?"

"Take more ownership." Usually means: follow things through without being chased, flag problems early rather than hoping, and be the person who closes the loop. Convert it by asking which piece of work they'd like you to own end to end.

"You're doing great." The hardest one, because it's pleasant and empty. Convert it with the graduate-hire question above.

Whatever you get, the move is the same: turn adjectives into actions. "More confident" is an adjective. "Say one thing in the Tuesday meeting" is an action. You can do the second one on Tuesday.

Ratings, briefly

If your employer uses a rating scale, the thing to know is that the middle rating is the good one. It means you did your job well. These scales are designed so most people land in the middle most years, and the top band is deliberately rare.

At 18, coming from a school system where you were probably near the top of everything, "meets expectations" reads as failure. It isn't. It's the normal outcome for a competent professional, and getting it in your first year — in a real job you started months after sixth form — is a genuinely good result. The mechanics of how that rating gets decided, in a calibration meeting you're not in, are in how pay reviews and bonuses work.

Afterwards is where the value is

Almost everyone treats the review as the end of the process. It's the start.

Write it down the same day — what was said, in your words, while it's fresh.

Pick two things. Not five. Two specific, observable changes.

Tell your manager what you picked. A three-line message: "Thanks for yesterday. I'm going to focus on X and Y — I'll aim to have made progress by the mid-year check-in." Almost nobody does this. It takes two minutes, it demonstrates that you can take feedback and act on it, and it means your manager is now watching for improvement rather than for the same problem.

Revisit it at the mid-year point. Ask directly: "Have you seen a difference in X?" If yes, that's a documented improvement they'll remember at the next cycle. If no, you have six months to change approach rather than discovering it in November.

Closing the loop is the single highest-return habit around performance reviews, and it's almost entirely unoccupied territory for someone your age.

And then everyone will talk about it

The last complication. Your cohort will compare — ratings, feedback, and eventually money. You live together, so there's no version where it stays private.

Same advice as everywhere else on this site: don't ask, and be careful what you tell. Your rating is one manager's assessment, filtered through a calibration meeting and a budget, in a specific team with specific work. It says much less about you relative to your cohort than it feels like it does at 11pm in a shared kitchen. The full version of that problem is in when your colleagues, classmates and housemates are the same people.

The reframe that helped most

For two cycles I treated the review as an exam I might fail. It's much more useful to treat it as the one meeting a year where a senior person is contractually obliged to tell you how to get better at your job, and to spend the whole time extracting as much of that as you can.

Nobody in my cohort was ever damaged by their first performance review. Plenty of us wasted it. Bring three questions, ask the graduate-hire question, pick two things, and tell your manager what you picked. That's the whole method, and it works at 19 exactly as well as it works at 40.