Cameron ConawayFeedback Literacy for All

The Feedback Guide

Performance Reviews: A Guide for Managers and Employees, with 100 Examples

A performance review is a structured conversation, usually paired with a written evaluation, about how someone’s work went over a set period and what should happen next. This guide covers both seats at the table: how to prepare, write, deliver, and receive a review, with 100 examples to adapt, 22 questions to ask, and the research on what makes reviews work.

By Professor Cameron Conaway, Penn State Smeal College of Business

Start where you are

A review asks different things of you depending on your seat and your deadline. Pick the row that matches today.

If you areStart with
Writing
Writing your self-evaluationHow to write a self-evaluationA five-part structure and 10 examples.
Writing a review for someone on your teamHow to write a performance reviewThe four parts of a useful comment, and eight rewrites.
Stuck on the wording for one skillExamples by skill48 comments across 12 skills, covering strengths and growth areas.
Writing the overall summaryOverall summary examplesSix summaries for six kinds of year.
Asked for feedback about your managerHow to review your managerThree rules and eight examples.
In the conversation
Walking into your own review this weekWhat to say as an employee14 lines for the moments that decide how the meeting goes.
Unsure what to askQuestions to ask12 for your manager and 10 for the people you manage.
Delivering a review that includes challenging feedbackHow to give challenging feedbackSix steps, and six lines for the hardest moments.
Finished with the meeting and unsure what comes nextWhat to do after a reviewThe first two weeks, for both people.
Running the process
Deciding how often to hold reviewsHow often to hold reviewsWhat each cadence is good for, and what it risks.
Deciding whether pay belongs in the same meetingPay, raises, and promotionsWhy many organizations hold two conversations.
Checking reviews for fairnessMistakes and bias to avoidNine patterns, with a fix for each.
Making the case that your reviews need to changeDo performance reviews work?Six findings, with sources.

What is a performance review?

A performance review is a structured conversation between an employee and their manager about how the employee’s work went over a set period, what it achieved, and what should happen next. Most organizations pair the conversation with a written evaluation, and many add a rating. You will also hear it called a performance appraisal, a performance evaluation, or an annual review.

What a performance review is for

A review has two jobs. The first is to evaluate: to put on record how the period went, often as an input to decisions about pay, promotion, and staffing. The second is to develop: to help the person do better work in the period ahead.

The two jobs pull against each other. Someone waiting to hear a rating or a raise is in a poor position to explore a weakness. Researchers at General Electric documented that tension in a 1965 study, and it explains much of what goes wrong in reviews today. The sections on the research and on pay return to it.

The five feedback skills inside every review

Most advice treats a review as something a manager gives and an employee gets. In practice, both people use all five skills of feedback literacy before the review is over.

SkillIf you are being reviewedIf you are giving the review
SeekingAsk colleagues for input before you write, and ask your manager questions during the meeting.Gather input from people who worked with the employee, and ask for the employee’s own account first.
GivingWrite your self-evaluation and, when asked, feedback for your manager and your peers.Write and deliver the review: specific, balanced, and tied to the work.
ReceivingListen, take notes, and ask for examples before you respond.Take in the employee’s response, including what they say about how you manage.
ProcessingSort what you heard: what fits, what doesn’t, and what needs more information.Check your own judgment for bias before the review is final.
UsingTurn one or two points into a plan, then report back on your progress.Do what you committed to, and adjust how you manage.

Types of performance reviews

“Performance review” covers several formats. Most organizations combine two or three of them.

TypeWho gives the inputBest for
Manager reviewThe direct managerThe standard evaluation of goals and results
Self-evaluationThe employeeEvidence and context the manager may not have
Peer reviewColleagues at a similar levelCollaboration and day-to-day behavior a manager is rarely present for
Upward reviewDirect reportsHow a manager manages
360-degree reviewManager, peers, direct reports, and sometimes customersDevelopment, more than pay decisions
CalibrationA group of managersApplying one standard across teams before ratings are final
Check-inManager and employeeCourse corrections between formal reviews

Do performance reviews work?

As most organizations run them, often not. They can, when the feedback in them is specific, frequent, and fair. Six findings explain both halves of that answer.

  1. Few employees say their reviews help them improve.

    Gallup reports that only 14% of employees strongly agree their performance reviews inspire them to improve. In a 2024 Gallup study, 22% of U.S. employees strongly agreed that their review process is fair and transparent, and 2% of Fortune 500 chief human resources officers strongly agreed that their system inspires employees to improve.

  2. A rating says as much about the rater as about the work.

    In a study of two large sets of ratings in the Journal of Applied Psychology, Steven Scullen, Michael Mount, and Maynard Goff found that a rater’s own tendencies accounted for more than half of the differences in ratings (62% and 53%). The performance of the person being rated accounted for about a quarter (21% and 25%).

  3. Feedback can make performance worse.

    Avraham Kluger and Angelo DeNisi’s 1996 meta-analysis found that feedback improved performance on average, and that in more than a third of cases it lowered it. The post on feedback intervention explains the finding.

  4. Criticism without a way forward backfires.

    In the General Electric study, published in 1965 as “Split Roles in Performance Appraisal,” Herbert Meyer, Emanuel Kay, and John French found that criticism made employees defensive, and that the more criticism a review contained, the more performance declined afterward. They recommended setting goals together and holding the salary discussion apart from the discussion about improvement.

  5. Vague feedback is common, and it is not evenly shared.

    Stanford researchers Shelley Correll and Caroline Simard analyzed more than 200 reviews at a technology company. Women were more likely than men to receive vague praise (57% compared with 43%), and men were more likely to receive developmental feedback tied to business outcomes (60% compared with 40%). Textio’s 2024 analysis of 23,000 reviews found that high performers received the lowest-quality feedback.

  6. Removing reviews doesn’t solve the problem.

    A CEB survey of nearly 10,000 employees in 18 countries found that at firms that eliminated reviews, measures of engagement and performance fell by 10%, and managers spent less time in conversation with their people, as Knowledge at Wharton reported. Frequency helps more than removal. In Gallup’s 2024 study, employees with quarterly progress checks were 90% more likely to be engaged.

What the findings add up to

The review itself is rarely the problem. Three habits are: feedback that arrives once a year, feedback that describes the person instead of the work, and feedback that ends without a next step. The rest of this guide is organized around fixing those three.

Reviews are also expensive, which raises the cost of running them poorly. When Deloitte counted, it found that completing forms, holding meetings, and creating ratings consumed close to 2 million hours a year, as Marcus Buckingham and Ashley Goodall wrote in Harvard Business Review.

How often to hold performance reviews

Hold a formal review at least twice a year, check progress on goals at least quarterly, and give feedback far more often than either. An annual review on its own asks one conversation to carry a year of feedback, and by then most of it arrives too late to use.

The evidence points the same way. Gallup recommends progress reviews at least every six months. In its 2024 study, 56% of employees said they formally review their goals with their manager once a year or less, and those with quarterly progress checks were 2.1 times as likely to say the process is fair and transparent. In 2016, Peter Cappelli and Anna Tavis described in Harvard Business Review how companies including Adobe, Deloitte, Microsoft, and General Electric were replacing annual reviews with frequent, informal check-ins.

CadenceGood forRisk
Once a yearPutting pay and promotion decisions on one calendarRecent events crowd out the rest of the year, and feedback arrives too late to use
Twice a yearA mid-year correction and a year-end summaryStill slow for fast-changing work, unless check-ins fill the gaps
QuarterlyGoals that shift with the business, and people who are new in a roleBecomes form-filling if every quarter requires a full write-up
Monthly or weekly check-insCourse corrections, recognition, and removing obstaclesLeaves no written record on its own for pay and promotion decisions

Factors to weigh when choosing a review cadence

  • How fast goals change. If priorities shift every quarter, a yearly review measures goals that no longer exist.
  • How new the person is. New hires and people in new roles need shorter cycles. Many organizations add reviews at 30, 60, and 90 days.
  • How pay and promotion decisions are timed. The formal review that feeds them needs a fixed place on the calendar.
  • How many people each manager reviews. A manager with twelve direct reports cannot write twelve careful reviews every quarter. Keep the frequent ones light.
  • Whether one-on-ones already happen. Regular one-on-one meetings carry most of the feedback, which lets the formal review be a summary.

What a simple review cycle includes

A simple cycle has six parts: goal setting, regular check-ins, a mid-year review, the self-evaluation, the manager’s evaluation, and the review conversation. The first two do most of the work. When goals are clear and check-ins are regular, the last four hold few surprises.

The best time of year for reviews

Many organizations tie reviews to the calendar or fiscal year, which places them in the busiest weeks. If you have a choice, schedule the main review after the period’s results are known and before the next period’s goals are set. Keep the mid-year review far enough from it to change something.

How to prepare for a performance review

Preparation decides most of a review’s quality. Both people should arrive with evidence, and neither should hear anything important for the first time.

If you are being reviewed

  1. Keep a running record.

    Add to it all year: results, numbers, thanks from colleagues and customers, and feedback you received. A simple document is enough. If you haven’t kept one, rebuild it from your calendar, your sent messages, and your project tools.

  2. Reread your goals and your last review.

    Your manager will measure the year against them. Note what you did about each piece of feedback from last time.

  3. Ask two or three people for input.

    Asking before you write is the seeking skill at work, and it lowers the odds of a surprise. One question is enough: “What is one thing I did this year that made your work easier, and one thing I could do differently?”

  4. Write your self-evaluation from the evidence.

    Follow the five-part structure below, even if your form asks for less.

  5. Decide what you want from the meeting.

    Choose one topic you want feedback on and one request to make, such as a stretch assignment, training, or clarity on promotion. Then pick three questions to ask.

If you are giving the review

  1. Gather evidence from the whole period.

    Reread your one-on-one notes, the goals, and the results. Memory favors the last few weeks, and a review written from memory will too.

  2. Ask for input from people who worked with the employee.

    Ask for examples, not ratings: “What did they do that helped the project, and what would have made working with them easier?”

  3. Read the self-evaluation before you write.

    Where your account differs from theirs, write the difference down as a question to ask, not a point to win.

  4. Write each comment around a situation, a behavior, and its impact.

    The section on how to write a performance review breaks down that structure.

  5. Remove the surprises.

    A review should summarize feedback, not introduce it. If your draft contains a concern the person hasn’t heard, raise it with them before the meeting.

  6. Plan the meeting.

    Book enough time and a private place, share the written review a day ahead if your process allows it, and plan to ask for the employee’s account first. If you can, hold the pay conversation separately.

How to write a self-evaluation

A self-evaluation is your written account of the review period: what you achieved, what fell short, what you learned, and what you want next. Write it from evidence, put numbers on results where you can, and treat your shortfalls the way you would want a manager to treat them: specifically, and with a next step.

It is also the one part of the review you control. Your manager works from an incomplete record of your year, and the self-evaluation is where you fill it in.

A five-part structure for a self-evaluation

Results

What you delivered against your goals, with numbers where they exist.

Contribution

What you did for the team beyond your own goals: helping, teaching, covering, and removing obstacles.

Shortfalls

What didn’t go to plan, why, and what you changed as a result.

Growth

What you learned or got better at, including feedback you acted on.

Next

What you want to take on, and the support you need to do it.

Self-evaluation examples

  1. Results: a goal you met“My goal was to cut invoice processing time from nine days to five. By September the average was 4.6 days, and it has held there for three months. The biggest gain came from the shared intake form I built with the purchasing team in April.”
  2. Results: a goal you exceeded“I committed to 24 qualified renewals this year and closed 31. Nine of them came from the lapsed-account outreach I proposed in the first quarter, which the team has since adopted as a standing practice.”
  3. Results: work that is hard to count“Much of my year went to work without a number attached. I rewrote the onboarding guide, and the last four new hires each finished setup in their first week without filing a help ticket. The four before them filed eleven tickets in total.”
  4. Contribution: beyond your own goals“From March to June I spent about two hours a week pairing with Dana while she learned our reporting tools. She now runs the monthly close report on her own, which has freed a day of my time each month.”
  5. Shortfalls: a goal you missed“I did not launch the partner portal by June. I underestimated the security review, and I raised the risk in May, which was too late to recover the date. It launched in August. I now schedule the security review at the start of every project plan, and I report a risk in the week I find it.”
  6. Shortfalls: a mistake“In February I sent a customer a pricing sheet with last year’s rates. The account manager caught it within a day, and no contract was affected. Since then, a second person checks anything of mine that goes to a customer, and there has been no repeat.”
  7. Growth: feedback you acted on“Last year’s review said my updates ran long and buried the decision I needed. I now open every update with the decision or the request. Two directors have told me the new format saves them time, and I get answers the same day far more often.”
  8. Growth: a skill you built“I finished the SQL course in May and have since built six reports myself instead of requesting them from the analytics team. The weekly churn report is now mine from end to end.”
  9. Next: what you want to take on“I would like to lead a project from start to finish next year. The warehouse relabeling project in the second quarter is a good fit: it crosses teams, it has a fixed date, and I know the systems involved.”
  10. Next: the support you need“To take on vendor negotiations, I need two things: to sit in on your next two contract renewals, and to know how far I can go on price before I check with you.”

Four mistakes to avoid in a self-evaluation

  • Listing duties instead of results. “Managed the vendor relationship” describes a job. “Renegotiated the vendor contract and saved $40,000 a year” describes a year.
  • Hiding behind “we.” Credit the team, then say what you did. Your manager cannot evaluate a contribution you never name.
  • Skipping what went wrong. Your manager already knows. Naming a shortfall first, with what you changed, earns more trust than leaving it out.
  • Grading effort. Long hours are not a result. Say what the hours produced.

If your form asks you to rate yourself, write the evidence first and choose the rating it supports.

How to write a performance review

Write each comment about something the person did, at a moment you can name, with the effect it had. Then say what you want next. That is the difference between a comment someone can use and a comment they can only react to.

A simple structure for the written review

If your organization has no form, or the form is an empty box, use six parts.

Summary

Two or three sentences that name the year. Write it last.

Results

Each goal, what was delivered, and the evidence.

Strengths

Two or three, each with an example and its impact.

Growth areas

One or two, each with an example, its impact, and a next step.

Goals

What the person will aim for in the next period, agreed together.

Support

What you will do to help: training, access, time, or introductions.

The four parts of a useful comment

Situation

Name the project, the meeting, or the period.

“During the March system migration,”

Behavior

Describe what the person did or said, without interpreting it.

“you documented every step and ran two practice runs with the support team.”

Impact

Say what it led to for the team, the customer, or the result.

“Support handled launch day without a single escalation, a first for a release of this size.”

Next step

Say what to continue, change, or try.

“I’d like you to lead the planning for the next two releases.”

The first three parts are the SBI model, developed by the Center for Creative Leadership. The fourth turns an observation into a direction. The feedback models page compares SBI with 35 other frameworks.

Eight rewrites, from vague to specific

  1. Instead of“Great team player.”Try“When the Denver office lost two analysts in May, you took over their weekly reporting for six weeks on top of your own. Their clients never missed a report, and two of them renewed in June.”
  2. Instead of“Needs to improve communication.”Try“In your last three project updates, the change to the launch date came in the final paragraph. Two stakeholders missed it and planned around the old date. Please open each update with what has changed and what you need from the reader.”
  3. Instead of“Exceeds expectations.”Try“Your goal was to reduce customer wait time by 10%. You reduced it by 22% by redesigning the triage queue, and the change has held for two quarters.”
  4. Instead of“Has a negative attitude.”Try“In the last two planning meetings, you raised objections to the new schedule after the decision had been made, and each meeting ran 20 minutes over. Your concerns about coverage were valid. Raise them at the proposal stage, when they can still change the plan.”
  5. Instead of“Lacks attention to detail.”Try“Four of your last ten client reports went out with formula errors that the client found. Each one cost us a correction and a call. Starting this month, run the audit checklist before you send a report, and ask Priya to check the first three.”
  6. Instead of“Not strategic enough.”Try“Your project plans are thorough on tasks and dates. They don’t yet say which business goal the project serves, or what we will stop doing to make room for it. Add both to your next plan, and we will go through it together before it reaches the leadership team.”
  7. Instead of“Should be more confident.”Try“In the October client meeting, you had the answer on integration timelines and waited for me to give it. When you have the facts, give them. I will back you up.”
  8. Instead of“A strong leader.”Try“You held a 30-minute one-on-one with each of your seven direct reports every week this year. Nobody left your team, and three of them told me your feedback is a reason they stayed.”

Words that weaken a review

  • “Always” and “never.” One counterexample ends the conversation. Count instead: “four of the last ten.”
  • Personality labels. “Abrasive,” “lazy,” and “not a natural leader” describe a person. Describe what the person did and what it led to.
  • Guesses about motives. “Doesn’t care about quality” is a guess. “Shipped without running the tests” is an observation.
  • Comparisons with coworkers. Measure the work against the goals and the role, not against a named colleague.
  • Praise with nothing in it. “Great year” gives the person nothing to repeat. The research above found that empty praise is also handed out unevenly.

Five checks before you send a review

  • The whole period. Does the evidence come from all of it, or from the last few weeks?
  • The swap test. Would you write the same comment about someone of a different gender, age, or background who did the same thing?
  • The next step. Does every growth comment say what to do differently?
  • The surprise. Is there anything here the person hasn’t heard? Tell them before the meeting.
  • The rating. Does it match the comments? If the words describe a strong year and the number says average, the person will believe the number.

Performance review examples by skill

Each example below follows the same pattern: a situation, a behavior, its impact, and, for growth areas, a next step. They are written to the employee, which is how a review reads best. If your form uses the third person, change “you” to the person’s name.

Swap in your own facts. The pattern is what carries over, and a comment copied without its facts turns back into a vague phrase.

Communication

Comment on whether the message was clear, well timed, and reached the people who needed it.

  1. Strength“Your weekly project summaries in the second half of the year fit on one page and opened with the decisions you needed. Stakeholders answered within a day on average, down from about a week, and the redesign stayed on schedule.”
  2. Strength“During the August outage, you sent customers an update every 30 minutes in plain language, including when there was nothing new to report. Complaints were a third of what we received in the March outage, and two customers wrote to thank us.”
  3. Growth area“In the last three all-hands presentations, your slides carried more detail than the room could absorb, and the questions afterward told me the main request was missed. For the next one, state the request in your first minute and cut the deck to five slides. I’m glad to rehearse it with you.”
  4. Growth area“Twice this quarter, a teammate learned from a customer that a delivery date had moved. You had updated the tracker, and nobody was told. When a date changes, message the people affected the same day.”

Collaboration and teamwork

Comment on how the person shares information, credit, and workload with others.

  1. Strength“During the product recall in April, you set up a daily 15-minute call across legal, support, and logistics, and you kept the action list. Decisions that had taken days by email took minutes, and we finished the recall a week ahead of the regulator’s deadline.”
  2. Strength“When the two new analysts were struggling with the forecasting model, you offered them a weekly working session. Both now produce forecasts that need no review, and the team’s rework has dropped.”
  3. Growth area“On the pricing project, you finished your analysis early and sent it without checking how it fit the finance team’s model. They spent a week reconciling the two. Before you start your next analysis, agree on the format with the team that will use it.”
  4. Growth area“In retrospectives this year, you have often explained why a problem belonged to another team. That may be accurate, and it leaves the group without a next step. Come to the next one with one thing our team could change, whoever caused the problem.”

Quality of work

Comment on accuracy, completeness, and how much rework the work creates for other people.

  1. Strength“Your code reviews this year caught 14 defects before release, including the billing error in the June build that would have reached every enterprise customer. The team’s defect rate in production fell by half.”
  2. Strength“The grant application you prepared in September was approved without a single request for clarification, the first time that has happened in four cycles. The reviewers singled out the budget narrative.”
  3. Growth area“Three of the month-end reconciliations you prepared this half had to be reopened for errors in the accruals, and each one delayed the close by a day. For the next two months, check each reconciliation against the prior month before you submit it. We will go through the first one together.”
  4. Growth area“Your first drafts arrive fast, and the last two client proposals needed three rounds of edits to fix scope and pricing. Speed is costing time downstream. Take an extra day on the next proposal, and confirm the scope with the delivery team before it comes to me.”

Reliability and time management

Comment on whether commitments are kept, and how early the person warns you when one is at risk.

  1. Strength“You delivered all eleven of your quarterly milestones on or before the date, in a year when the plan changed twice. Other teams now build their schedules around yours because they trust your dates.”
  2. Strength“When you learned in March that the vendor would be late, you told me the same day and came with two options. We chose one within the week and kept the launch date.”
  3. Growth area“Five of your eight deliverables this quarter arrived after the agreed date, and I learned about each delay on the day it was due. Lateness is sometimes unavoidable. Silence isn’t. From now on, tell me as soon as a date is at risk, and bring a new date with you.”
  4. Growth area“You took on four projects this half and finished two. The two that stalled were the ones the sales team was waiting on. Before you accept the next request, tell me what it would displace, and we will decide together.”

Problem solving and judgment

Comment on how the person finds causes, weighs options, and decides.

  1. Strength“When returns spiked in July, you didn’t accept the first explanation. You pulled the shipping data, traced the problem to one packaging supplier, and had a replacement in place within two weeks. Returns are back to their normal level.”
  2. Strength“Faced with a budget cut in the second quarter, you ranked every campaign by cost per lead and proposed dropping the bottom three. We kept 94% of our lead volume on 80% of the budget.”
  3. Growth area“On the scheduling problem in the spring, you built a full solution before confirming the cause. It addressed staffing, and the issue turned out to be the booking software. Next time, write down the cause and your evidence for it, and check both with one other person before you build.”
  4. Growth area“You brought me six decisions this quarter that were within your authority, including the vendor credit in May. Each wait cost the customer a day or more. For anything under $2,000, decide, tell me afterward, and I will back your call.”

Initiative and ownership

Comment on what the person starts, fixes, or finishes without being asked.

  1. Strength“Nobody asked you to audit our software licenses. You did it during a slow week in February and found $18,000 a year in seats nobody was using. That paid for the team’s training budget.”
  2. Strength“When the handoff between sales and onboarding kept failing, you wrote a one-page checklist, tested it on five accounts, and brought it to both teams. Onboarding delays fell from an average of nine days to three.”
  3. Growth area“You raised the gap in our returns policy in January, and it was still open in June. Raising a problem is a good start. On the next one, bring a proposed fix and a first step you can take yourself.”
  4. Growth area“When the client changed the deadline, you waited two days for instructions, and the team lost that time. In that situation, draft a revised plan and send it to me for a yes or a no. You know the project well enough to make the first call.”

Adaptability

Comment on how the person responds when priorities, tools, or teams change.

  1. Strength“When we moved to the new scheduling system in May, you learned it in the first week and ran three lunchtime sessions for the rest of the floor. Our unit finished the switch a month ahead of the hospital’s target.”
  2. Strength“Your territory was redrawn twice this year. Both times, you had introduced yourself to every new account within two weeks, and you finished the year at 108% of quota.”
  3. Growth area“When priorities changed in the third quarter, you kept working on the retired project for three weeks because it was close to done, and the new priority started late. When direction changes, stop, and bring me what it would take to finish the old work so that we can decide together.”
  4. Growth area“You have told the team several times that the old approval process was better. You may be right about parts of it, and the complaints are slowing adoption. Write down the two changes that would fix the new process for you, and I will take them to operations.”

Customer focus

Comment on how the person listens to customers, keeps them informed, and follows through.

  1. Strength“In March, a customer mentioned in passing that our invoices were hard to match to their purchase orders. You worked with billing to add the order number to every invoice. That customer’s payment time dropped from 52 days to 31, and billing has made the change standard.”
  2. Strength“Your satisfaction scores averaged 4.8 out of 5 across 600 cases this year, the highest on the team. Customers most often mention that you explain what will happen next and when.”
  3. Growth area“On three escalated calls I sat in on this quarter, you moved to the fix before the customer had finished describing the problem. Two of them called back because the fix addressed the wrong issue. Let the customer finish, then repeat the problem in your own words before you start.”
  4. Growth area“Two of your accounts learned about the price increase from their invoice. Both called me, and one is now reconsidering the contract. For any change that affects what a customer pays, call them before it takes effect.”

Job knowledge and technical skill

Comment on the person’s command of the tools and subject matter the role requires.

  1. Strength“You are the person the team asks about the tax code changes, and your March briefing kept us from misfiling for 40 clients. I’d like you to turn it into a guide for new staff.”
  2. Strength“You rebuilt the data pipeline in the second quarter so that reports refresh in 10 minutes instead of 3 hours. Analysts now run them during client calls.”
  3. Growth area“Since the platform upgrade in June, you have asked colleagues for help with tasks the new version handles differently, most recently the export on October 3. Set aside two hours a week this month for the vendor’s training modules, and tell me by the 30th which ones you finished.”
  4. Growth area“Your design work is strong. Your files often arrive without the specifications developers need, and they have had to come back to you on four of the last six handoffs. Use the handoff template for every file, starting now.”

Leadership and people management

Comment on how the person sets direction, gives feedback, and develops other people.

  1. Strength“You gave each of your six direct reports written feedback every month this year. In the engagement survey, your team scored 20 points above the company average on ‘I know what is expected of me.’”
  2. Strength“Two people on your team were promoted this year, both into roles you prepared them for by handing over the weekly operations meeting and the vendor reviews. You made yourself less necessary, which is what good development does.”
  3. Growth area“You rewrote your team’s work on four of the last six client deliverables instead of sending it back with comments. The deliverables were strong, and your team has stopped learning from them. For the next quarter, return drafts with feedback and let the author make the changes.”
  4. Growth area“Two of your direct reports told me they first heard about their performance concerns in their mid-year review. Nothing in a review should be new. Raise a concern within a week of the event, and keep a note of what you said.”

Learning and growth

Comment on what the person has done to get better, and whether it has changed the work.

  1. Strength“You asked to shadow the finance team for a week in April so that you could understand how your forecasts are used. Your forecasts since then have included the cash timing they need, and they no longer come back with questions.”
  2. Strength“After the spring product launch fell short, you wrote up what you would do differently and presented it to the team without being asked. Three of your five changes are now part of our launch process.”
  3. Growth area“We agreed in January that you would complete the project management certification by September. You have finished two of the six modules. Tell me by Friday what got in the way and what date you can commit to.”
  4. Growth area“You have run the onboarding session the same way for three years, and new-hire ratings of it have slipped from 4.5 to 3.9. Ask the last two groups what they would change, and bring me a revised outline next month.”

Feedback skills

Comment on how the person seeks, receives, uses, and gives feedback. These are the skills of employee feedback literacy, and few review forms ask about them.

  1. Strength: seeking“After every client presentation this year, you asked the room for one thing to keep and one thing to change, and you kept a running list. Your win rate on pitches rose from three in ten to five in ten.”
  2. Strength: using“In last year’s review, I said your handoff notes left the next shift guessing. You asked two colleagues what they needed, redesigned the note, and checked back a month later to ask whether it was working. There have been no handoff errors on your shifts since.”
  3. Growth area: receiving“When Priya raised a concern about the timeline in the September planning meeting, you explained why she was wrong before she had finished. She has not raised a concern since. Next time, ask one question about the concern before you answer it.”
  4. Growth area: giving“You describe problems with your team’s work to me and not to them. Sam’s last three reports had the same error, and he did not know until I told him. Give feedback to the person within a few days, and start with what you observed.”

Overall summary examples

The summary is the part of a review people reread. Name the year in one sentence, give the evidence, and end with what comes next.

  1. Exceeded expectations“This was an outstanding year. You beat all three of your goals by a wide margin, above all the 22% cut in customer wait time against a 10% target, and you did it while training two new team members. The triage queue you redesigned is now the standard across the region. Next year, I want you to lead the rollout to the other two regions, and I will recommend you for the senior role in the spring cycle.”
  2. Met expectations“You had a solid year. You met four of your five goals, kept every client deadline, and became the person the team turns to on the new billing system. The fifth goal, the certification, is half done. Your work is dependable, and the next step is range. I’d like you to lead one cross-team project next year, starting with the vendor consolidation in the second quarter.”
  3. Met expectations, with one growth area“Your results this year were strong: 104% of quota and two of our five largest renewals. One pattern held you back. Handoffs to the delivery team were incomplete on six accounts, and delivery spent time collecting information you already had. Fixing that is your main goal for next year, and it is what stands between you and the senior role.”
  4. Did not meet expectations“This year fell short of what the role requires. You met one of your four goals, and five of your eight quarterly deliverables arrived late. We discussed this in March, June, and September, so none of it is new. I know the reorganization made the year harder. Over the next 90 days, I need every deliverable on time or flagged early, and we will meet every two weeks to track progress. I want you to succeed here, and I will do my part.”
  5. New in the role“You joined in July, so this review covers five months. You finished onboarding ahead of schedule, took over the weekly reporting in your second month, and have already caught two errors in the legacy data. It is too early to rate your results against annual goals. For the first half of next year, the goal is full ownership of the monthly close.”
  6. A strong year without a promotion“You had a strong year, and I want to be direct about the promotion. You met every goal, and your project work was excellent. The senior role also requires leading work across teams, and you have not yet had the chance to do that. I am giving you the regional rollout in the first quarter so that you can. If it goes the way I expect, I will put your name forward in the fall cycle.”

What to say in a performance review as an employee

Say what you achieved and bring the evidence. Ask for an example whenever feedback is unclear. Name what you want next. And when feedback is challenging, ask for time before you answer it. The lines below cover the moments that decide how the meeting goes.

14 things to say in your performance review

  1. To open the meeting“Before we go through the form, could I take two minutes on what I’m proudest of this year and where I’d most like your feedback?”
  2. To present a result“The goal was a five-day turnaround. We reached 4.6 days in September and have held it since. The intake form I built with purchasing did most of that.”
  3. To share credit accurately“The launch was a team effort. My part was the testing plan and the two practice runs, which is why launch day had no escalations.”
  4. To raise a shortfall before your manager does“One goal I missed was the portal launch date. I raised the risk too late. I’ve changed how I plan for security reviews, and I’d like your opinion on whether that is enough.”
  5. When you receive praise“Thank you. Which part of that mattered most to you? I want to make sure I repeat the right thing.”
  6. When feedback is vague“Can you give me a recent example, and tell me what you would have wanted me to do instead?”
  7. When feedback is challenging“That is hard to hear, and I want to take it seriously. Can I think it over and come back to you on Thursday with questions?”
  8. When you disagree with a point“I remember that meeting differently. Here is what I recall. Can we compare notes, so that I understand what you observed?”
  9. When you disagree with the rating“I expected a different rating, based on the results we just went through. Can you explain how it was decided, and what would have earned the next level?”
  10. To ask about growth“What is the one skill that would make the biggest difference to my work next year?”
  11. To ask for support“To hit the new target, I need access to the analytics tool and about four hours of training. Can we agree on that today?”
  12. To ask about promotion or pay“I’d like to talk about what it would take to reach the senior level. Where are the gaps, and what timeline is realistic?”
  13. When your manager asks for feedback“One thing would help me. When priorities change, tell me which task to drop. Twice this quarter I kept working on both.”
  14. To close the meeting“Let me check that I have this right. My priorities are the two we named, you will arrange the training, and we will check in on the first of each month. Is that your understanding too?”

What not to say in a performance review

  • “That’s not fair.” Ask for the example instead, then respond to the example.
  • “Everyone else does it.” Comparisons with coworkers move the conversation away from your work.
  • “I’ll leave if I don’t get a raise.” Say it only if you mean it and are ready to act on it.
  • “I had no idea.” If that is true, say what would have helped: “I would have wanted to hear this in June. Can we agree to raise things like this as they happen?”
  • Nothing at all. Silence reads as agreement. If you need time, ask for it.

How to receive feedback during the review

Take notes, ask one clarifying question before you respond, and keep two things separate: understanding the feedback, and deciding what to do about it. The meeting is for the first. The second can wait a day.

Cameron Conaway’s 4As of receiving feedback describe the stance: Aspire, Active, Ask, and Accept. Accepting feedback does not mean adopting it. It means you understand it well enough to start processing it. The lesson on how to receive feedback goes further.

Questions to ask in a performance review

Good questions turn a review from a verdict into a conversation. Bring three, and ask the one that matters most first.

12 questions to ask your manager

  • About this year
    • “What is one thing I did this year that had the most impact?”
    • “Where did my work fall short of what you needed, and what would you have wanted instead?”
    • “Is there feedback about me from other teams that I should hear?”
  • About expectations
    • “What does excellent work in my role involve over the next six to twelve months?”
    • “If I can fully deliver only one of my goals, which one matters most to you?”
    • “How will my performance be measured next cycle, and by whom?”
  • About growth
    • “What is one skill I should build next?”
    • “Where is my next opportunity to grow on this team or in the organization?”
    • “What would I need to demonstrate to be considered for the next level?”
  • About working together
    • “What could I do to make your job easier?”
    • “How do you prefer to get updates and bad news from me?”
    • “Is this review tied to compensation, and if so, how?”

10 questions for managers to ask

  • About the period
    • “What are you most proud of from this cycle?”
    • “Where did you feel most challenged, and what did you learn from it?”
    • “What got in your way this year that I could have removed?”
    • “Which goal would you set differently if we started the year again?”
  • About what comes next
    • “What part of your work gives you the most energy right now?”
    • “What is one area where you would like more support or coaching?”
    • “What do you want to be doing a year from now?”
  • About your own management
    • “Is there feedback you have been holding back, about the team or about me?”
    • “What is one thing I could do differently to help you succeed?”
    • “What did I miss in this review?”

Ask about behavior, not traits

A question about a trait invites a yes. A question about a specific event invites evidence.

  • Instead of “Are you a team player?” ask “Tell me about a recent time you worked across teams. What was the result?”
  • Instead of “Do you handle pressure well?” ask “Tell me about a week when several deadlines collided. How did you decide what came first?”

How to give challenging feedback in a review

Say it before the review, say it specifically, and say what you want next. Challenging feedback goes wrong in a review when it arrives as a surprise, as a verdict on the person, or without a way forward.

  1. Raise it before the review.

    If the person would hear a concern for the first time in the meeting, have that conversation first. The review should summarize it.

  2. Open with why you are raising it.

    People take in more when they know your intent. Cameron Conaway’s R-SBI-R framework starts with the relationship for that reason: “I’m raising this because I want you in the senior role, and this is in the way.”

  3. Give one issue, one example, and its impact.

    A list of six problems reads as a verdict. Pick the one that matters most, and describe a moment the person will remember.

  4. Ask for their account.

    “What was happening for you that week?” You may learn something that changes the feedback. Asking about intent is the fourth step of the SBII model.

  5. Agree on a next step and a date.

    One change, and one date to check on it. Write both down.

  6. Follow up in writing, and again in person.

    Send a short summary the same day. Then name progress when it happens. The first improvement is the one that most needs recognition.

Six lines for the hardest moments

  1. To open a review that includes a concern“Most of this review is positive, and I will go through it. I also want to spend real time on the concern we discussed in June, because it is the main thing between you and the next level.”
  2. When the rating will disappoint“The rating is ‘meets expectations.’ I know you were hoping for higher, so let me explain how I got there. Then I want to hear your reaction.”
  3. When the person gets defensive“I can tell this is landing hard, and I’m not questioning your effort. Let’s stay with the one example. What do you remember about that week?”
  4. When the person goes quiet“I’ve said a lot. Take a minute. I’d like to hear what you’re thinking, including where you disagree.”
  5. When the person disputes your example“You may be right about that meeting, and I will check my notes. Leaving it aside, the pattern across the three reports still concerns me. Can we talk about the pattern?”
  6. When there is no promotion this cycle“There is no promotion for you in this cycle, and I’d rather tell you plainly than have you wait for it. Here is what the committee needs, and here is what I will do in the next six months to help you get there.”

For more wording, the constructive feedback page has 40 examples of constructive feedback.

How to review your manager

Describe what you experienced, connect it to your work, and ask for one change. Upward feedback follows the same rules as any other feedback, with one difference: the person reading it has a say in your pay and your assignments. That makes specifics more important, not less.

  • Write about your own experience. A statement that starts with “I” is accurate and hard to dispute: “I learned about the reorganization from another team.”
  • Tie it to the work. Say what the behavior made easier or harder for you to do.
  • Ask for one change. A request gives your manager something to do. A complaint gives them something to defend.

If the feedback is anonymous, write it as though it weren’t. On a small team, authorship is easy to guess, and feedback you would sign is usually feedback that is fair.

Examples of feedback for your manager

  1. Strength: clear priorities“When the product roadmap changed in May, you told us the same afternoon which two projects to pause. I never had to guess what mattered, and I lost no time on work that was about to be cut.”
  2. Strength: useful feedback“Your comments on my drafts arrive within a day and point to specific paragraphs. My second drafts need far fewer changes than they did a year ago.”
  3. Strength: advocacy“You put my name on the pricing analysis when you presented it to the leadership team, and two directors have since asked me for help directly. That did more for my career than anything else this year.”
  4. Strength: availability“You kept our weekly one-on-one every week this year, including during the audit. Because I can count on that half hour, I save small questions for it instead of interrupting you.”
  5. Request: priorities“I’m often unsure which of my projects comes first. Twice this quarter, I finished the one you needed second. A two-line priority list at the start of each week would fix that for me.”
  6. Request: timely feedback“I’d like feedback closer to the event. I heard about the March client call in our September review, and by then I couldn’t recall the details. A two-minute comment in the same week would help me more than a full discussion months later.”
  7. Request: room to do the work“On the vendor project, you rewrote my plan before I could explain the reasoning behind it. I’d learn more if you asked me questions about a draft and let me make the changes.”
  8. Request: better meetings“Our team meeting often runs past the hour and ends without decisions. An agenda sent the day before, with the decisions we need to make listed first, would give me back time each week.”

What to do after a performance review

Write down what you heard, let it settle, choose one or two things to act on, and schedule the follow-up. The review is the midpoint. What happens in the two weeks after it decides whether anything changes.

If you were reviewed

  1. Write down what you heard, the same day.

    Memory edits quickly, and it tends to keep the harshest sentence. Record each point as close to your manager’s words as you can.

  2. Let it settle before you decide.

    Sort each point: agree, unsure, or disagree. Cameron Conaway’s 6 Ps of Processing Feedback and Feedback Decision Tree are built for this step, and the lesson on how to process feedback explains it in full.

  3. Send a short follow-up note.

    Within two days, confirm the two or three main points and the next steps, including what your manager agreed to do. The note becomes the record you both work from.

  4. Turn one or two points into a plan.

    For each one, write the goal, the first action, the support you need, and a date. More than two is usually too many.

  5. Ask for feedback on the change.

    A month in, ask the person who gave the feedback whether anything is different. The Feedback GROWTH Model treats that check as part of using feedback.

If you gave the review

  1. Send the written summary within a few days.

    Include the next steps and the dates you agreed on.

  2. Do what you said you would do.

    If you promised training, a new assignment, or an introduction, arrange it this month. A forgotten commitment undoes much of what the review built.

  3. Put the check-ins on the calendar.

    Thirty, 60, and 90 days is a common rhythm for a development goal. Your one-on-ones can carry them.

  4. Name progress when it happens.

    Say what changed and what it led to, in the same week.

How to write a development goal

A development goal works when it names a behavior and a date. The best-known test is the SMART criteria. George Doran introduced them in 1981 as Specific, Measurable, Assignable, Realistic, and Time-related. Today the A and the R usually stand for Achievable and Relevant.

Instead of “improve communication,” write: “Lead the third-quarter project kickoff, and send stakeholders a weekly summary every Friday through September.”

If you disagree with your review

Start by asking for the examples behind the point you dispute. Then put your account in writing, with your evidence, and ask for it to be attached to the review. Most review systems have a place for an employee comment. If the disagreement is about fairness more than facts, human resources is the next step. Stay with specifics throughout.

Pay, raises, and promotions

Should a performance review decide pay?

In most organizations, the review is one input. Budgets, pay ranges, and open roles shape the decision as well, which is why a strong review does not guarantee a raise. If you don’t know how the two connect where you work, ask: “Is compensation tied to this review, and if so, how?”

Why separate performance reviews from pay reviews?

Because people stop taking in feedback once money is on the table. When a raise or a rating is coming, the person listens for the number, and the developmental half of the conversation is lost. The 1965 General Electric study recommended splitting the two discussions for that reason. Gallup suggests the same: one meeting for pay, and a separate one for performance and growth.

If your process combines them, you can still separate them in practice. Hold the development conversation first, and deliver the pay decision in a short meeting a week or two later.

How to ask for a raise or a promotion

  • Start before the review. Decisions are often made weeks before the meeting. Tell your manager what you are aiming for early in the cycle.
  • Learn the process. Ask who decides, when, and on what criteria.
  • Bring sustained evidence. One strong quarter is a start. A year of results at the next level is a case.
  • Talk about impact and scope. Say what you have delivered and what you are ready to take on.

How to respond to a raise or promotion request

Don’t promise what you can’t deliver, and don’t leave the request unanswered. If the decision isn’t yours, or isn’t possible now, explain the process and name what would strengthen the case: “Here is what I would need in order to advocate for you.” Then agree on when you will come back to it.

What is a typical raise?

U.S. merit increases have held at a little over 3% in recent years. In a July 2026 Mercer survey of about 1,000 U.S. employers, planned merit increases averaged 3.2%, within total salary increase budgets of 3.5%, the fourth straight year of similar figures. Promotions and market adjustments usually come from a separate and smaller budget. Figures vary by industry, location, and role, so check a current salary survey for yours.

Mistakes and bias to avoid

Most review errors are predictable, which means they can be planned for. Nine patterns come up again and again.

PatternWhat happensFix
Recency biasThe last six weeks outweigh the ten months before them.Keep notes all year, and reread them before you write.
Halo and hornsOne strength, or one mistake, colors every category.Rate each area on its own evidence.
Leniency and severityEveryone on the team gets high marks, or low ones.Compare your ratings with other managers’ in calibration.
Central tendencyEveryone lands in the middle of the scale.Use the ends of the scale when the evidence supports it.
Similarity biasPeople who resemble the reviewer get the benefit of the doubt.Ask the same two questions of every review: what did they do, and what did it lead to?
Proximity biasWork done remotely or quietly goes uncounted.Review results, and ask each person for a record of theirs.
Personality feedbackThe review describes who the person is, not what they did.Rewrite each label as a behavior and its impact.
Narrative fallacyOne tidy story explains the whole year.Test the story against the record.
The surpriseFeedback is saved up for the review.Give it when it happens.

On proximity bias, the evidence is reassuring when performance is measured with care. In a randomized trial of 1,612 employees published in Nature in 2024, Nicholas Bloom, Ruobing Han, and James Liang found that working from home two days a week had no effect on performance grades over the next two years of reviews, and they found no evidence of a difference in promotions.

Mistakes employees make

Four are common on the other side of the table: arriving unprepared, defending instead of asking, asking no questions, and doing nothing with the review afterward. The sections on preparing, what to say, and what to do afterward address each one.

Questions and answers

What is a performance review?

A performance review is a structured conversation between an employee and their manager about how the employee’s work went over a set period, what it achieved, and what should happen next. It is usually paired with a written evaluation and often a rating. It is also called a performance appraisal or a performance evaluation.

What is the purpose of a performance review?

A review has two purposes. It evaluates the past period, often as an input to pay and promotion decisions, and it develops the person for the period ahead. The two can conflict, which is why many organizations hold the pay conversation separately.

How often should performance reviews be held?

Hold a formal review at least twice a year, and check progress on goals at least quarterly. Gallup recommends progress reviews at least every six months. Feedback itself should come far more often, in weekly or monthly one-on-ones, so that the formal review holds no surprises.

What should I say in a performance review as an employee?

Say what you achieved, with evidence. Raise your own shortfalls and what you changed. Ask for an example when feedback is unclear, ask for time when it is challenging, and name what you want next, such as a skill to build, a project to lead, or clarity on promotion. Close by confirming the next steps.

How do I write a self-evaluation for a performance review?

Cover five things: your results against your goals, your contribution to the team, what fell short and what you changed, what you learned, and what you want next. Use numbers where they exist, describe results instead of duties, and write about shortfalls specifically.

What makes a good performance review comment?

A good comment names a situation, describes what the person did, states the impact, and gives a next step. For example: “During the March migration, you documented every step and ran two practice runs with the support team. Launch day had no escalations. I’d like you to lead the planning for the next two releases.”

How do you write a negative performance review in a positive way?

Don’t soften the facts. Make them useful. Describe the specific behavior and its impact, leave out labels for the person, and end each concern with what you want done differently and how you will help. A critical review is constructive when the person finishes it knowing exactly what to change.

What should a manager not say in a performance review?

Avoid “always” and “never,” personality labels such as “abrasive” or “lazy,” guesses about motives, comparisons with coworkers, and anything the person is hearing for the first time. Each one moves the conversation from the work to a defense of the person.

Should performance reviews be tied to pay?

Reviews usually inform pay, and the two conversations work better apart. When a raise is on the table, people listen for the number and miss the feedback. Many organizations hold a development conversation and a separate, shorter pay conversation.

Are annual performance reviews outdated?

The annual review as the only feedback of the year is outdated. Many organizations now add quarterly or more frequent check-ins, an approach often called continuous performance management. Dropping reviews entirely has not worked well either: in a CEB survey, engagement and performance fell at firms that eliminated them.

How does remote or hybrid work affect performance reviews?

It raises the risk of proximity bias, where work done away from the office goes uncounted. Measured with care, hybrid work does not hurt reviews. A 2024 randomized trial published in Nature found that working from home two days a week had no effect on performance grades, and it found no evidence of a difference in promotions. Review results, and ask employees to keep a record of theirs.

Can AI write a performance review?

AI tools can help draft a review, tighten it, and check it for vague or biased language. They cannot supply the evidence, which has to come from the manager’s notes and the employee’s results, and the judgment remains the manager’s. Follow your employer’s rules before entering employee information into any tool.

Practice the skills behind the review

A review asks for five feedback skills in a single hour. They are easier to build before the meeting than during it.

The five-minute feedback practice

Free

Fifteen real situations. One page of feedback that is yours to keep and share.

Start the practice

The Feedback Deck

$29

50 evidence-based cards across the five skills of feedback literacy, each with a three-minute companion video.

Explore the deck

Feedback Literacy Certification

$199

Establishes your competency across all five feedback literacy skills. Self-paced, with an exam and a LinkedIn credential upon completion.

Explore the certification

Feedback training for teams

By quote

Keynotes, workshops, and audits with Professor Cameron Conaway.

Explore feedback training