How to Prepare for a Performance Review When You Hate Talking About Your Own Work

There is a particular kind of discomfort that comes with being asked to describe your own work, and if you feel it, you are not unusual and you are not lacking confidence. Most of the people I have worked on this with are perfectly confident about the work itself. What they find difficult is the part where they have to say it out loud to someone who decides what they earn.

So this is not going to be advice about believing in yourself more. It is going to be about assembling a document, because a document is easier than a feeling and it works better.

Say your review is in three weeks. You have had a good year, in the sense that you know you have, but when you sit down to write the form you find you have about four lines and two of them are about the team. You know you put out a fire in March and you cannot remember what it was. You know somebody thanked you properly in an email and you cannot find it. By the time you have stared at the blank box for twenty minutes you have decided you just did your job, which is the conclusion almost everyone reaches at that point, and it is the wrong one.

Why is it so hard to talk about your own accomplishments?

The main reason is that the work you do best costs you the least effort, so it stops registering as an accomplishment at all. Whatever you are good at feels easy from the inside, and anything that feels easy feels like it should not count.

That is worth sitting with for a second, because it has a consequence that runs the wrong way. The things you would most want a manager to know about are precisely the things you are least likely to write down, and the things you struggled with are the ones that feel significant enough to mention. So the list you produce from memory is close to the opposite of the list you need.

The second reason is that most of us were taught that describing your own contribution is immodest. I want to separate two things that get tangled together here. Boasting is claiming something that is not true, or claiming more of it than was yours. Documenting is saying what happened. "I rebuilt the onboarding process and setup time went from fourteen days to five" is not a boast, because either it happened or it did not. If it happened, you are reporting it, and the discomfort you feel is about the reporting rather than about the truth of it.

What should you actually prepare for a performance review?

Prepare a written list of specific things you did, what each one changed, and the numbers attached where numbers exist. That is the whole preparation, and almost nobody does it, which is why doing it works so well.

Here is the structure I use for each item, and it has three parts.

Situation. What was the problem, the challenge or the opportunity in front of you?

Action. What did you specifically do about it? Not the team, you.

Result. What changed, and by how much?

The result is the part that does the work, because numbers are hard to argue with. Compare these two sentences about the same piece of work.

The first is "improved the customer onboarding process." The second is "redesigned the customer onboarding process, which brought average setup time down from fourteen days to five and cut support tickets by about a third." The first could describe almost anything, and your manager has no way to weigh it. The second gives a person who has to justify your pay to somebody else exactly what they need to do it.

You do not need perfect figures. An honest estimate stated as an estimate is far better than nothing, and if you saved the team five hours a week, that is a real number even if you worked it out roughly.

What four questions find the work you have forgotten?

Most of your accomplishments are not missing, they are just not where you are looking. Asking yourself "what did I achieve this year" produces a short and oddly humble list. These four questions come at it sideways and they find much more.

Set aside half an hour and answer them on paper. Paper matters here, because you cannot do this in your head.

The Crisis Question. What would have gone badly wrong if you had not been there to handle it? Think about the emergencies, the tight deadlines, the things that broke, the misunderstandings you caught before they became problems. These are often your most valuable contributions and the ones least likely to appear in any plan.

The Money Question. How did you help the business make money or avoid spending it? This feels impossible if your job is not obviously commercial, and it is usually answerable anyway. A client who stayed because you handled something well is revenue. A process you fixed that stopped eating three hours a week is cost. You do not need to work in sales for your work to touch money, because almost all work does.

The Invisible Labor Question. What would fall through the cracks if you were not paying attention to it? This is my favorite of the four, because it finds the work that never appears anywhere. You are the one who notices a client has gone quiet. You remember that the contract renews in March. You keep a running sense of who is struggling and you quietly adjust around it. None of that is in your job description and all of it is holding something up.

The Recognition Question. What has somebody already said about your work? Search your email for thank-yous. Read your last review. Look at the messages where a colleague said you saved them. Other people's words are the easiest evidence to use, because you are not the one making the claim.

Go back to your three weeks and that blank box. If you answered those four questions you would not have four lines any more. You would have the fire in March with what it would have cost, the process nobody asked you to fix, the client who stayed, and two emails from people who were grateful. That is not a feeling about your value. It is a list, and a list can go in a form.

What does it cost you to walk in unprepared?

The immediate cost is that you get a smaller number than the work supports, and I want to be precise about why, because it is not that your manager is being unfair.

Your manager is usually making a case to somebody else, and that somebody else is looking at a budget and several names. A manager who has your specifics can argue for you, and a manager who only has a general sense that you are good has nothing to put in the argument. So when you walk in without the document, you are not failing to advocate for yourself. You are leaving your advocate without any material.

Then it compounds, and this is the part that matters more than the review itself. Future raises are usually calculated as a percentage of what you already earn, so a smaller increase this year makes every increase after it smaller too. Pension contributions are often a percentage of salary, so a lower base lowers that quietly in the background. And when you move jobs, the offer is frequently anchored to what you currently make, which means this year's number follows you out of the door.

The cost of doing nothing is not that things stay the same. It is that the gap between what you are paid and what your work supports gets a little wider each year, while you are being reasonable about it.

There is a quieter cost too. If you never say what you did, you slowly start to believe the short humble version, and that version is not accurate. Several people have told me the documenting changed how they saw their own year more than it changed their pay, which was not what they expected and is not a small thing.

Does doing your job well really count as an accomplishment?

Yes, and this is the objection that stops most people, so it is worth answering properly.

The thought goes "that was just my job, so it does not count." But consider two people in the same role with the same description. One does what is required. The other notices what is breaking, suggests the fix, takes it on without being asked, and delivers something better than what was specified. Both of them are doing their job. One of them is obviously worth more.

So the question is not whether something was in your job description. The question is whether you created value, and your list is how you show which of those two people you are. Nobody is paid for a job description. They are paid for what the job description turned into.

What do you do in the three weeks before the review?

Four things, in order, and none of them take long.

Block half an hour this week and answer the four questions on paper.
Turn the answers into five or six items using Situation, Action and Result. Five strong ones

beat fifteen vague ones.

Find the numbers for as many as you can. Check old emails and old dashboards. Where you

cannot find a figure, write your honest estimate and label it as an estimate.

Say them out loud. This is the step people skip and it is the one that makes the difference,

because a sentence you have said before is much easier to say to your manager than a sentence you are reading for the first time.

Start the list now rather than three weeks before the next one. Fifteen minutes on a Friday noting what you did that week is easier than reconstructing a year from memory, and the people who are good at this are not better at remembering. They just wrote it down as it happened.

One thing worth saying plainly, because I believe it and it is the whole point of the exercise. Preparing for a review is not about learning to sell yourself. It is about turning up with facts so that nobody in the room, including you, has to rely on an impression.

Common questions

What if my work genuinely cannot be measured?

Then measure what changed rather than what you produced. Fewer complaints, faster replies, a handover that went smoothly, a client who renewed, a new person who got up to speed quickly. If something is better than it was and you are part of the reason, that is the result, and you can say so without a percentage attached.

Is it bad to talk about team achievements in my review?

It is not, and the thing to avoid is letting the team absorb your part entirely. Name the project and then name what you did inside it. "The team delivered the migration, and I owned the data cleanup and the rollback plan" credits both without disappearing into the first half of the sentence.

How many accomplishments should I bring to a review?

Five or six specific items with results attached is plenty for most reviews. A long list dilutes itself, because the strong items get read at the same weight as the weak ones. Pick the ones with the clearest results and keep the rest in your own notes.

What if I forgot to track anything all year?

Then do the four questions now, and expect to be surprised by how much comes back once you are looking in the right places. Your sent email is a better memory than your memory. Then set up the Friday habit so next year is a shorter job.

*This article is education and coaching rather than financial, tax, legal or employment advice, and it cannot account for your own situation or the rules where you work.*

Nobody is paid for a job description. They are paid for what the job description turned into, and

the only person who can write that down is you.