If you want to prepare for your performance review, you usually run into the same problem: the year was packed, yet your memory holds mostly the last few weeks. That tricky bug in October, the bumpy release in September. Whatever went really well in February has long since faded. And that is exactly the picture you take into the meeting.
Yesterday I wrote about how managers prepare an annual review. Today I am flipping the perspective. This guide is for you if you sit on the other side of the table as a developer or any other team member and do not want to simply sit through your next review. You get a template for a brag document, wording tips for your self-review, questions for the meeting and a plan for the case where you disagree with your rating.
In short
If you want to prepare for your performance review, evidence beats memory: a brag document you keep up to date, an honest self-review and two or three concrete development wishes. Your manager only sees part of your work, and you can help them see the whole picture. The biggest pitfall is reacting on the spot to a rating instead of asking for examples and time to think.
What you will learn in this article
- How a brag document helps you collect evidence from the whole year
- How to write a self-review that neither brags nor sells you short
- How to phrase development wishes so they turn into agreements
- What you can do when you disagree with your rating
Why you should prepare for your performance review
Your manager only sees part of your work. They notice which tickets get closed and which releases ship. Much less visible: you spent three weeks onboarding a new colleague, your review prevented an expensive mistake, or the on-call runbook is finally correct. The bigger the team, the smaller that slice.
On top of that comes a well-known rating error, recency bias: whatever happened last weighs more than the rest of the year. It affects your manager just as much as it affects you. Walk in unprepared, and both of you will mainly be rating the autumn.
So preparation has little to do with self-promotion. You provide information that would otherwise be missing from the conversation. Your role shifts as well: instead of waiting for a verdict, you bring your own topics. That changes the mood noticeably, even when the meeting happens over video.
What rights do you have in a performance review in Germany?
A quick look at the legal framework in Germany, because many people are not aware of it. If you work elsewhere, the details will differ, but the ideas behind them are still useful. I am not a lawyer, and this is not legal advice. The rules are in the German Works Constitution Act (Betriebsverfassungsgesetz, BetrVG), the law that covers employee rights at the workplace and co-determination through the works council.
Under Section 82 (2) BetrVG, you can ask for the assessment of your performance and your career development options within the company to be discussed with you. In other words, you do not have to wait for someone to schedule a meeting. The same paragraph also lets you ask for an explanation of how your pay is calculated and made up. If there is a works council, you may bring one of its members, who is bound to confidentiality.
Section 83 BetrVG gives you the right to inspect your personnel file. This matters if a written appraisal ends up there: your own statements about its content must be added to the file at your request. Finally, Section 84 BetrVG covers your right to complain if you feel treated unfairly. Filing a complaint must not lead to any disadvantage for you.
In day-to-day work you rarely need these sections. Knowing them still gives you peace of mind: you have a right to the conversation and to your own view in the file.
Prepare for your performance review with a brag document
The most effective tool is a simple document you maintain throughout the year. Julia Evans described the idea in 2019 as a “brag document”. Despite the name, it is not about showing off. You keep a running record of what you worked on, what your contribution was and what came out of it.
If you are now thinking “too late, my review is in three weeks”: start anyway, because you can still prepare for your performance review at short notice. One evening with your calendar, your pull request history, closed tickets and old chat threads brings back a surprising amount. After that, 15 minutes every two weeks are enough, for example on Friday afternoon.
What belongs in your brag document
I would structure the document by month and capture three things per entry: the goal, your contribution and the impact. You will often add the impact later, once it becomes visible. Besides projects, include the things that are quickly forgotten:
- Support within the team, such as onboarding, pairing or reviews that prevented a problem
- Documentation, architecture decisions and runbooks
- Improvements to how you work, for example a faster build or better onboarding
- What you learned and where you already apply it
- External visibility such as talks, blog posts or open source contributions
Write honestly. A brag document is not a job application, and entries like “didn’t work out, what I learned was …” are just as valuable as the wins.
Describe impact instead of listing tasks
The most common mistake in self-reviews is a list of activities. “Worked on the checkout” says little about your contribution. The pattern goal, action, impact works much better. Here are a few fictional examples from an online bookshop:
| Weak | Stronger |
|---|---|
| Worked on the checkout. | The goal was to reduce checkout drop-offs. I moved the address check into a background job, and the step now loads in under one second instead of about three. |
| Onboarded new colleagues. | I supported two new colleagues during their first six weeks. Both shipped their first feature in week three. |
| Wrote documentation. | I reworked the on-call runbook. Since then, there have been no more questions about the three most frequent alerts. |
Numbers help, but they are not a must. If nothing was measured, describe what you observed: who benefited, and what is easier now than before?
From brag document to review: five steps that repeat every year
Write a self-review without bragging
Anyone who has to prepare for a performance review is often handed a self-review form in advance. Even if your company has none: write one, if only for yourself. Your brag document now turns into a single page with three parts.
Three sections on one page
The first part lists three to five contributions you are proud of, each with its impact. The second part describes where you grew: a new technology, more responsibility or a difficult conversation you handled well. The third part covers what did not go well and what you take away from it.
I consider this third part the most important. It shows that you see yourself realistically. Leave it out, and you hand all the critical points to the other side, which means reacting in the meeting instead of naming them yourself.
Wording that works
I often see two traps. One is playing things down: “I helped a bit with the migration”, although you planned it. The other is the “we” that swallows everything. Teamwork is right and important, but the review is about your share. So write “I created the migration plan, and the team implemented it” instead of “We migrated”.
Sentence starters like “My contribution was …”, “This led to …” or “Next time I would …” help. They force you to make concrete statements without sounding like an advert.
Share it before you talk
Send your self-review to your manager about a week before the meeting. That way they can compare their view with yours instead of hearing about it for the first time in the room. Julia Evans points out exactly this effect: a manager with concrete evidence finds it easier to advocate for you. This matters most in calibration meetings, where managers align their ratings with each other and you are not present.
Phrase your development wishes concretely
Looking back is only half of it. At least as much time in the meeting should go to the coming year. Many people stumble here because their wishes are too vague. “I want to develop myself” is always true and leads nowhere.
I use a simple template with three sentences:
- In twelve months, I want to … for example make and document architecture decisions for our service on my own.
- For that, I need … for example ownership of a smaller design, regular feedback from an experienced architect and time for training.
- How we will know it works: for example two architecture decision records that the team adopted without much rework.
Keep performance goals and development goals apart. Performance goals describe what you are expected to deliver. Development goals describe what you want to learn or be able to do. Mix them up, and every learning goal becomes a test, so nobody dares to try something new anymore. If your manager wants to tie a development goal to your rating, feel free to ask how failure would be handled.
Two or three wishes are plenty. Anything beyond that will not be followed up in everyday work anyway.
What questions can you ask in a performance review?
A review goes better when you do more than answer. The following questions have proven useful. Pick three or four that fit your situation.
Questions about your rating
- From your perspective, what was my most important contribution this year?
- Where did you see me differently from how I described myself?
- What would I need to do for you to rate my work even higher next year?
Questions about your development
- Which skill would help me most next year?
- Which task in the team could I take on to grow?
- What does the next career step look like here, and what am I still missing for it?
Questions about working together
- What can I do to make your work easier?
- How often would you like to talk with me about my progress?
The questions about working together are also a chance for feedback in the other direction. I described how to prepare that in Giving feedback to your manager.
What to do if you disagree with your rating
Sooner or later it happens: you hear an assessment that feels wrong. The urge to push back right away is understandable. A different sequence works better.
First, ask for concrete examples. Good feedback describes a situation, a behaviour and its impact, the so-called SBI model (Situation, Behavior, Impact) from the Center for Creative Leadership. If that is missing, a simple question helps: “Can you name a situation where this happened?” Sometimes the misunderstanding clears up right there.
If you still disagree, you do not have to settle it in the meeting. Ask for a few days to think and a follow-up appointment. Afterwards, you can set out your view in writing, backed by evidence from your brag document. If a written appraisal goes into your personnel file in Germany, Section 83 BetrVG lets you demand that your statement is added. The formal route via a complaint or the works council is the last step and rarely needed as long as both sides stay fair.
One thing I would avoid: pointing at other team members during the meeting. It moves the topic away from your work and leaves an impression that lasts longer than any rating.
Should you bring up salary in a performance review?
Whether salary is on the agenda varies from company to company. Some deliberately separate pay talks from development talks, others cover both in one meeting. Ask beforehand instead of springing it on your manager. If salary is part of it, prepare it like everything else: with your contributions, your increased responsibility and a clear idea of what you are asking for.
Regardless of that, Section 82 BetrVG gives employees in Germany the right to have the calculation and make-up of their pay explained. This helps especially when variable components or allowances are hard to understand.
After the review: write down your agreements
Even the best conversation fizzles out if nobody thinks about it afterwards. Within one or two days, send a short summary: what you agreed on, who does what by when and when you will look at it again. It takes ten minutes and prevents both of you from remembering something different next autumn.
After that, the topic belongs in your regular one-on-ones. A quick look at your development goals every six to eight weeks is enough. Your brag document simply keeps running, so you do not start from zero again next year.
My take
I am not a fan of a person’s development depending on a single meeting per year. Ideally, an annual review brings nothing new, because everything important has already been discussed in one-on-ones. Reality often looks different, and then good preparation is your strongest lever.
There is an imbalance worth naming honestly. People who talk confidently about their own work are often rated higher than those who achieve just as much but are more reserved. A brag document evens this out to some extent, because it delivers facts instead of self-promotion. As a manager, I explicitly welcome this kind of material, because it corrects my own perception.
Where I would push back, though, is on the idea of scripting the whole meeting. If you have pre-written every answer, you stop really listening. Come with evidence, questions and wishes, and leave room for what the other side brings.
FAQ
How do I prepare for a performance review?
Collect evidence from the whole year, condense it into a one-page self-review, phrase two or three development wishes and note three questions for your manager. Ideally, share the self-review about a week before the meeting.
What should I say about my weaknesses in a performance review?
Name one or two real things that did not go well and what you learned from them or have already changed. Concrete examples are more credible than clichés like “I am too much of a perfectionist”.
Can I bring a works council member to my review in Germany?
If the meeting is about the assessment of your performance or your development options, Section 82 (2) BetrVG allows it, provided there is a works council at your workplace. The member is bound to confidentiality unless you release them from it.
Do I have to sign an appraisal I disagree with?
That depends on your company’s rules. Often a signature only confirms that the meeting took place. Ask what it means, and if you disagree, request that your statement is added to your personnel file (in Germany under Section 83 (2) BetrVG).
Your next step
If you want to prepare for your next performance review, create a document called “brag document” today and add three things from the last four weeks, each with goal, contribution and impact. Also put a recurring reminder every two weeks in your calendar. And I am curious: what is harder for you when preparing, talking about successes or about what did not go well? Feel free to tell me in the comments.
Sources
- Section 82 BetrVG: employee’s right to be heard and to discuss (gesetze-im-internet.de, German)
- Section 83 BetrVG: inspection of personnel files (gesetze-im-internet.de, German)
- Section 84 BetrVG: right to complain (gesetze-im-internet.de, German)
- Julia Evans: Get your work recognized: write a brag document
- Center for Creative Leadership: Use Situation-Behavior-Impact (SBI) to Understand Intent
- Wikipedia: Recency bias
This post was created with AI assistance.
👉 Next step: Preparing a first one-on-one? My question cheat sheet puts the best questions on one printable page.
📬 Stay updated: New articles on serverless, AI and leading tech teams via RSS, browser push or the weekly newsletter (in German).
Originally published on sascha-ms.de. More articles on serverless, AI in everyday development and leading tech teams: sascha-ms.de/en


