The performance review: making your case

It is the week before your performance review. Your manager sends the self-assessment template. The questions are the usual ones: what did you accomplish this year, how did you demonstrate the competencies at your level, what is your development plan. You open a blank document and stare at it.

You know you worked hard. You remember being busy, being stressed, solving problems at 11pm. But the specifics are gone. You vaguely recall fixing something with the data pipeline in April. There was a tricky stakeholder situation in Q3 that you navigated. You shipped that new dashboard in November. But you have no numbers, no names, no outcomes. So you write something like: “Led efforts to improve data pipeline reliability and delivered new reporting capabilities to business stakeholders.”

Your manager reads it, nods, and rates you “meets expectations.” You leave the room surprised. That is the gap this essay is about.

Why your manager does not know what you did

Your manager is probably running a team of six to twelve people. They have their own deliverables, their own reviews, their own politics. They attended some of your presentations. They saw some of your pull requests. They heard secondhand about a few things that went well.

The rest of your year is invisible to them.

This is not negligence. It is arithmetic. If you want your manager to evaluate you accurately, you have to supply the raw material. Hoping they noticed is a strategy that works about as well as hoping the interviewer remembers your resume.

The good news is that making your case is a learnable skill with a clear structure. It has three parts: a running record (the brag document), a translation step (impact not activity), and a framing move (connecting work to the level above).

Part one: the brag document

A brag document is a private, running log of things you did that are worth remembering. The name comes from a post by Julia Evans that circulated in engineering circles, and the idea is simple: write things down while you remember them, so you are not reconstructing the year from memory in one panicked evening.

The format does not matter much. A Google Doc, a Notion page, a plain text file — whatever you will actually maintain. What matters is cadence. Set a monthly recurring calendar block, thirty minutes, to add entries. Do not wait for the end of the year.

What goes in it? Anything that might be worth citing later. A feature you shipped. A bug you caught before it hit production. A document you wrote that got adopted by another team. A process you changed. A hard conversation you navigated. A junior team member you helped ramp up. Quantify when you can — runtimes, percentages, counts of people affected — and add context when you cannot. Date each entry.

The document has two jobs. First, it prevents forgetting. Second, it forces you to notice your own work at a granularity that the year-end panic never allows. Most people drastically underestimate how much they did, because the memory of Q1 is genuinely gone by Q4.

Part two: impact, not activity

This is the translation step, and it is where most self-assessments fail. Activity language describes what you did. Impact language describes what changed because you did it.

The difference looks like this.

The rewrite answers three questions that the original ignores: what changed, by how much, and for whom. Those three questions are the structure.

Not every bullet needs a percentage. Sometimes the impact is qualitative: “Wrote the onboarding guide for the data platform; it is now the standard resource used by all new analysts.” That is still better than “contributed to documentation.” What changed? There is now a standard resource. For whom? New analysts. Why does it matter? Onboarding is faster and more consistent.

When you do have numbers, use them even if they are imperfect. “Reduced average time-to-first-response from roughly four days to under one day” is far more useful than “improved response time.” Your manager is not going to audit your estimates. They are looking for evidence that you understand what your work was for.

A useful diagnostic: read your draft bullet and ask whether someone who had no idea what you worked on would learn something concrete from it. If the answer is no, keep rewriting.

Part three: connect work to the level above

This is the part that most people skip, and it is the part that most directly affects the outcome of the review conversation.

Every company with a career ladder has a definition of what each level does, how decisions are made, what scope is expected. Most of those definitions are public, or at least available to you if you ask. Before you write your self-assessment, read the rubric for the level above yours.

Then, for each significant piece of work you list, add one sentence that draws the connection explicitly. “This is an example of the cross-functional influence expected at senior level.” Or: “This project required me to own the technical direction without supervision, which is the core expectation at L5.”

You are not being presumptuous. You are making your manager’s job easier. When they write your review, they have to map your work onto the rubric. If you have already done that mapping, clearly and honestly, they just need to decide whether they agree. That saves time and produces a more accurate output.

If your work does not map well to the next level’s rubric, that is important information too. It tells you what you are missing and what to focus on in the next cycle. The goal is honest calibration, not spin.

The conversation itself

Walking into the review is not the end of the process — it is the middle of it. The conversation is where ambiguity gets resolved and where you can directly surface what you want.

Most people treat the review as a verdict to receive. The more effective posture is to treat it as a negotiation with evidence on the table.

Come in with your self-assessment prepared, your brag document mentally organised, and two or three specific questions. The most important one: “Based on what I shared and what you have observed, what do you see as the gap between where I am and where I need to be for the next level?” Ask it directly. Take notes. Do not be defensive — the answer is the most valuable career data you will get all year.

If you disagree with the rating, say so, calmly and with evidence. “I want to understand the reasoning here. The two outcomes I thought were strongest were X and Y. Can you help me understand how those were factored in?” That is not combative. It is the kind of conversation that people at senior levels have routinely. You are entitled to understand how you are being evaluated.

If the feedback is that your visibility was low — that your manager did not know about several things until you listed them — that is a managing-up problem for the next cycle, not a reflection of your actual performance. It means you ran a great race without updating the scoreboard.

Starting now, not in November

The performance review is not a November event. It is a year-long practice with a November summary.

The actual work is: update the brag document every month, rewrite bullets as impact before you forget the context, and do a quarterly check against the level rubric to see where you are tracking. That is three habits, none of which takes more than an hour a month combined.

If you do that, the self-assessment writes itself. You already have the evidence. You already have the framing. You walk in with a case instead of a memory. Your manager reads something substantive instead of something vague. They make a better decision.

The uncomfortable truth is that your manager is not failing you by forgetting your work. They are managing ten people, each doing dozens of things, across a year. Expecting them to carry a complete picture of your contributions without your help is expecting them to do a job they were never set up to do.

Your case is yours to make. The good news is it is entirely within your control.