KoruWhat to Say in a Performance Review When You Want to Sound Specific
A practical guide to what to say in a performance review: how to discuss wins, missed goals, growth, feedback, and next steps without sounding vague or scripted.
The hardest part of a performance review is rarely the meeting itself. It is the moment before it, when you are trying to decide what to say without sounding defensive, vague, or like you memorized a career-advice script.
Here is the simplest version: say what happened, why it mattered, what you learned, and what you want to do next.
That is enough for most review conversations. The problem is that people skip the middle. They say, "I worked hard this year" or "I want to keep growing," and hope their manager fills in the evidence. Sometimes they do. Often they cannot.
Vague
"I think I had a strong year and contributed to a lot of important projects."
Specific
"I led the onboarding workflow cleanup, cut the average setup time from 4 days to 2, and used what we learned to document the support handoff."
The second version is not louder. It is just easier to use.
Start with the point of the meeting
A performance review is not a monologue. It is a structured conversation about four things:
- What went well
- What did not go as planned
- What you learned
- What should happen next
If you prepare one sentence for each of those, you are already ahead of most people.
What went well
"The strongest part of my year was the customer onboarding work. The main result was reducing setup time from 4 days to 2, and the bigger lesson was that our handoff process needed clearer ownership."
What did not go as planned
"The Q3 reporting project took longer than expected. I underestimated the data cleanup work, but I documented the blockers earlier in the Q4 project and the timeline was much more accurate."
What I learned
"I am better at spotting operational risk now. I want to keep building that into how I plan projects, not just how I recover from them."
What I want next
"I would like to take on one project next cycle where I own the planning process end to end, with feedback from you at the midpoint."
Do not copy those lines word for word. Use the shape: result, context, learning, next ask.
What to say about achievements
When you talk about achievements, do not start with adjectives. Start with the work.
"I was proactive" is hard to evaluate. "I created the release checklist after two customer-facing bugs and it is now used by 3 teams" gives your manager something concrete to discuss.
| Situation | Say this |
|---|---|
| You shipped something | "I delivered [project] by [date], and the measurable result was [outcome]." |
| You improved a process | "The old process caused [problem]. I changed [specific thing], which led to [result]." |
| You helped another team | "I supported [team/person] by doing [work]. The part I owned was [specific contribution]." |
| You handled ambiguity | "The unclear part was [constraint]. I made [decision], then checked it by [evidence]." |
| You grew into more scope | "Compared with last review cycle, I now own [larger scope]. The clearest example is [project]." |
What to say about missed goals
Do not pretend every goal went well. Your manager already knows. A better move is to separate the miss from the pattern.
Bad version
"The timeline slipped because other teams were slow to respond."
Better version
"The timeline slipped by 3 weeks. Part of that was dependency lag, but I also waited too long to escalate the risk. For the next cross-team project, I want to set dependency checkpoints in week one instead of reacting when the deadline is already tight."
That answer does three useful things. It names the miss. It owns the part you controlled. It gives your manager a way to evaluate improvement next time.
What to ask your manager
Most people prepare statements and forget questions. That is a mistake. The questions you ask tell your manager what kind of feedback you can handle and what kind of work you want next.
To clarify expectations
"What would make my work clearly stronger next cycle?"
"Where do you see the gap between my current level and the next one?"
To test your self-assessment
"Does my view of the year match yours?"
"Which accomplishment do you think mattered most from the team's perspective?"
To ask for more scope
"What would you need to see before trusting me with a larger project?"
"Is there a project next quarter where I could own the planning, not just the execution?"
To make feedback actionable
"Can we pick one behavior to focus on for the next 60 days?"
"What would good progress look like by our next 1:1?"
You do not need to ask all of these. Pick two. A review with two honest questions is usually better than one packed with prepared talking points.
What to say if you want a raise or promotion
You can bring up compensation or promotion in a performance review, but do not bury it at the end like an awkward surprise. Name the topic clearly and tie it to evidence.
Too vague
"I was hoping we could talk about a raise because I feel like I have been doing more."
Clearer
"I would like to discuss what it would take to move toward the next level. Since the last cycle, I have taken ownership of the partner launch, mentored 2 new team members, and become the main point of contact for the support escalation workflow."
This does not guarantee the answer you want. It does make the conversation easier to continue. Your manager can respond to scope, examples, and next-level expectations. They cannot do much with "I feel ready."
What not to say
Some phrases sound harmless but make the conversation weaker.
| Avoid | Use instead |
|---|---|
| "I helped with a lot of things." | "The most useful thing I owned was..." |
| "I think I did pretty well." | "The evidence I am most confident in is..." |
| "I want to grow." | "The skill I want to build next is..." |
| "I did not get enough support." | "The support gap was..., and next time I would raise it by..." |
| "I am ready for more." | "The larger scope I want to test is..." |
The pattern is simple: replace feelings with evidence, and replace vague ambition with a specific next step.
If your review is soon, prepare in 20 minutes
If the meeting is today or tomorrow, do not try to reconstruct the whole year. You will panic and end up with a messy document.
Use the short version:
- 01
Pick 3 work moments
Choose one win, one hard problem, and one thing you learned. Use your calendar, sent messages, tickets, or project tool if memory is blank.
- 02
Add one detail to each
For each moment, add a date, number, stakeholder, constraint, or outcome. One detail is enough to stop the example sounding generic.
- 03
Write 2 questions
Pick one question about expectations and one question about next scope. The meeting should give you information, not just a rating.
Where a career journal helps
The best review language comes from notes you wrote before you needed them. A weekly entry does not need to be polished. It only needs to preserve the details that disappear first: numbers, names, constraints, decisions, and feedback.
That is the difference between:
"I worked on onboarding."
and:
"In April, I rewrote the onboarding handoff after 6 support tickets exposed the same missing step. Setup time dropped from 4 days to 2, and Support stopped reopening the same ticket category."
One sounds like a task. The other sounds like a contribution.
Koru is built around that second version of the story: capture the work while it is fresh, then turn it into material for reviews, interviews, CVs, and career planning. You can do the same thing in a notes app if you are consistent. The important part is not the tool. It is having the facts before the meeting asks for them.
Say less than you think. Make it specific. Then ask for the next piece of feedback.
Related reading
Comparison
Notion Career Journal Template vs Koru
Compare a Notion career journal template with Koru for career tracking, brag documents, STAR stories, and interview preparation.
Comparison
Koru vs Spreadsheets for Career Tracking
Compare Koru with Google Sheets and Excel for tracking career achievements. Learn why free spreadsheets often fail for career journaling and what makes purpose-built tools stick.
Career Development
Best Career Journal Apps in 2026
Compare the top career journaling apps for tracking achievements, preparing for interviews, and building your professional narrative. Tested and reviewed by career development experts.
Professional Development
Best Achievement Tracking Tools in 2026
Compare the best tools for tracking work accomplishments, building brag documents, and preparing for performance reviews. Reviews include AI-powered trackers and traditional methods.