Writing your first performance review as a manager is one of the more quietly stressful experiences in professional life. Nobody trains you for it properly. You are handed a form, given a deadline, and expected to produce written assessments that are fair, specific, useful, and legally defensible, all at once. This guide gives you performance review examples you can adapt immediately, with enough context to understand why each phrase works and when to reach for it.
The examples here are written for first-time managers handling their first full review cycle. They cover strong performers, inconsistent ones, technically excellent but interpersonally difficult people, and the awkward middle ground where someone is trying hard but not quite landing. They are also written to connect the formal review moment to the broader machinery of performance management, because a review that sits in isolation changes very little.
What makes a performance review example actually useful?
A useful performance review example is specific, tied to a real behaviour, and points to an outcome. It gives the person reading it enough information to understand what happened, why it mattered, and what should continue or change. Vague praise and vague criticism are equally useless because neither gives anyone a direction to move in.
The phrase "great communicator" tells no one anything. The phrase "during the Q3 product launch, you flagged a dependency issue two weeks before the deadline, which gave the engineering team time to adjust their sprint, preventing a delay" tells the reader exactly what the person did, when, and what it prevented. That is the difference that matters. The test for any performance review phrase is simple: could you defend it with a specific example if someone asked you to?
This matters more than many first-time managers realise. Gallup's research into workplace performance and engagement consistently finds that employees who receive specific, strengths-based feedback are more engaged, more productive, and less likely to leave. Generic feedback signals that a manager hasn't been paying attention. Specific feedback signals investment.
The format that tends to work across most competency areas follows a simple three-part structure: name the behaviour, give the example, state the impact. You do not need four paragraphs for most assessments. Two to four sentences, built around that structure, is usually enough.
How do you write performance review examples for a strong performer?
For a strong performer, the goal is to name what they are actually doing well and reinforce why it matters, not just affirm that they are good. Recognition without specificity feels hollow fast. The examples below are grouped by competency.
Delivery and reliability
"Over the last six months, you met every project milestone on time or ahead of schedule. In the case of the market analysis report, you delivered three days early and flagged two gaps in the brief that we were able to address before the client saw the output. This kind of proactive delivery has built real confidence with the team and with stakeholders."
Initiative
"You identified a gap in how we were onboarding new clients and proposed a revised checklist without being asked. You piloted it with two accounts, refined it based on what you observed, and shared the final version with the wider team. That is exactly the kind of ownership this team needs more of."
Collaboration
"When the design and engineering teams hit a communication breakdown in March, you stepped in without being asked and organised a working session that produced agreement on the disputed requirements. Feedback from both teams was positive. That kind of lateral coordination is rare and it noticeably accelerated the project."
Communication
"Your written updates to stakeholders are consistently clear and well-structured. You calibrate the detail level to the audience, which saves time in follow-up. Three senior stakeholders have specifically mentioned your update emails as a model of how they want project communication to work."
For company culture purposes, strong performer reviews matter as much as difficult ones. When people see that excellent work is named precisely and publicly valued, it reinforces what the organisation actually rewards. HR teams should pay attention to whether recognition in formal reviews is specific enough to carry that signal.
How do you write performance review examples for someone who is inconsistent?
Inconsistent performers are the hardest category to write about. They are not failing. They are not excelling. They cycle between genuinely strong work and frustrating lapses, often in ways that make a manager question whether the environment or the individual is the main variable.
The rule here is to name the pattern, not just the instances. One weak month is not a pattern. A recurring tendency to rush deliverables at the end of a cycle, produce strong work mid-cycle, and disengage when the work gets difficult is a pattern, and it deserves to be named as such.
"Your work on the competitor analysis in April was one of the strongest pieces of research the team produced all quarter. The methodology was sound, the synthesis was clear, and the recommendations were directly actionable. At the same time, the client-facing deliverables in May and June showed inconsistency in quality control. There were formatting errors in the May report and a factual error in the June presentation that required a follow-up. The gap between what you are capable of and what you are consistently producing is the development priority for next quarter."
This kind of framing is honest without being punitive. It holds the person to their own demonstrated standard rather than an abstract expectation. It also creates a foundation for the action plans that need to follow the review conversation.
According to Harvard Business Review's research on performance feedback, employees are more likely to respond constructively to feedback that is grounded in their own past performance rather than external benchmarks. Saying "you did this at a high level in April, so we know you can" is more effective than "you should be doing this at a high level."
For inconsistent performers, the review should also acknowledge any contextual factors that may have contributed. If workload was unmanageable in May, say so. If there was unclear direction from the manager side, own it. An honest review is a two-way assessment.
How do you write performance review examples for a technically strong but difficult colleague?
This is the category most first-time managers dread. The person produces excellent individual work. Their code is clean, their analysis is sharp, their deliverables are rarely late. But they make the team worse through how they operate. They dismiss others' ideas. They go around process when it inconveniences them. They create friction that the manager then has to spend time and energy managing.
The trap is to either ignore the interpersonal pattern because the technical output is good, or to over-correct and write a review that feels like a character indictment. Neither serves the person or the organisation.
Focus on the observable behaviour and its measurable cost to the team.
"Your technical contribution this half has been strong. The architecture work on the data pipeline was well-designed and the documentation you produced has become a reference point for the team. At the same time, there have been three instances where implementation decisions were communicated to stakeholders before the team had reviewed them. In two of those cases, the team identified issues that required rework after the communication had already been sent. The cost of that pattern is real: it creates rework, it erodes trust with stakeholders, and it undermines the team's confidence in process. This is the single most important development priority for next half, and it is a blocker to the senior role we have discussed."
Employee sentiments around this kind of colleague are often complex. People may admire the technical work while feeling undermined by the behaviour. Pulse surveys and continuous feedback gathered during the review period give a manager data to reference without making the assessment feel like hearsay.
How do you write performance review examples for someone who is new to the role?
New-to-role reviews require a different frame entirely. The person has not had enough time to demonstrate full-cycle performance. What you are actually assessing is trajectory, learning speed, cultural fit, and early signals of potential. The worst thing you can do is write a review that holds someone to standards they were never told applied to their first six months.
"You joined in September and within eight weeks you were handling the full client email workflow independently. You asked good questions early, acknowledged gaps honestly, and course-corrected quickly based on feedback. The early indicators of how you approach learning and ownership are strong, and they are the foundation the rest of your development here will build on."
For someone who is new but struggling, the review needs to be equally honest, and the action plan needs to be specific. Not "improve your time management" but "we will implement a weekly check-in on Tuesday mornings to review workload and priority, and you will flag any at-risk items by end of day Monday so we can address them before they slip."
This is where performance management systems earn their value. When continuous feedback has been happening throughout the cycle, the review is not a surprise. The person arrives knowing broadly where they stand. HR teams building review processes for first-time managers should design the cycle so that new employees receive formal mid-point check-ins well before the full review, giving them a chance to adjust.
How do you write development-focused performance review examples?
Not every review section is a verdict. Development sections are forward-looking and they should feel that way. The mistake is writing development goals so vague they become meaningless between the meeting and the next cycle.
Bad: "Continue to develop your leadership skills."
Better: "Over the next six months, take the lead on at least two cross-functional projects. After each one, we will review what went well and what you would do differently. By Q3, the goal is for you to be running those projects independently, including managing the stakeholder communication."
Bad: "Improve your written communication."
Better: "In Q1, all client-facing reports will be reviewed with me before they go out. We will use those sessions to work through structure and clarity together. By Q2, the goal is for you to need that review only on new formats or high-stakes outputs."
McKinsey's research on talent and development consistently points to the value of specific, time-bounded development goals over generic aspiration. The difference is accountability. When a goal has a defined timeframe, a defined output, and a defined review point, both the manager and the person can track it.
The development section of a review is also where workplace culture becomes visible. If an organisation says it values growth but the development sections of its reviews are all generic boilerplate, the culture claim is hollow. Real commitment to growth shows up in the specificity of the plan that follows the review conversation.
How do action plans connect to performance review conversations?
Action plans are what turn performance reviews from paperwork into behaviour change. Without them, a review is a moment. With them, it becomes a contract.
An effective action plan from a performance review includes three things: what will change, what support is in place to enable the change, and how progress will be measured. It does not need to be long. It needs to be clear.
For a mid-level performer working on delegation: "By end of Q1, you will have delegated the weekly reporting task to a junior team member. You will provide a brief, and we will review the first three outputs together. Success looks like you spending no more than thirty minutes a week on that task by week eight."
For someone developing stakeholder management: "You will take the lead on the next quarterly business review with the client. We will prep together the week before. After the meeting, you will write a one-page reflection on what you would do differently. We will use that to structure coaching for the following cycle."
The connection between action plans and employee engagement is documented. Gallup finds that employees who have a clear development plan are significantly more likely to be engaged, and engaged employees are more likely to stay. An action plan is not a management formality, it is a retention mechanism. HR teams that treat action plans as optional paperwork are leaving engagement value on the table.
Real time analytics tools can make this easier than it sounds. When managers have access to ongoing data about employee sentiments, goal progress, and engagement levels, the action plan becomes a living document rather than a filed PDF.
Frequently Asked Questions
What are good performance review examples for first-time managers?
Good performance review examples for first-time managers are specific, behavioural, and tied to outcomes. Phrases like "you consistently delivered reports two days ahead of schedule, which gave the wider team time to act on the data" work better than "you are organised." Specificity is what separates a useful review from one that feels generic.
How should a first-time manager open a performance review conversation?
Open with a direct statement of intent, something like "I want this to be a two-way conversation, not a verdict." Then anchor the discussion in the work, not the person. Starting with a specific example from the review period grounds the conversation immediately and reduces defensiveness.
What is the difference between a performance review and continuous feedback?
A performance review is a structured, periodic assessment of overall contribution, usually tied to goals, ratings, or development planning. Continuous feedback is ongoing, informal, and tied to specific moments or behaviours. Reviews summarise a period; continuous feedback shapes it in real time.
How long should performance review comments be?
For most competencies, two to four sentences is enough. One sentence names the behaviour, one gives a specific example, one states the impact, and an optional fourth points toward development. Longer comments rarely add clarity. They often dilute it.
How do you write a performance review for someone who is technically strong but hard to work with?
Focus on observable behaviours and their consequences, not personality. Instead of "you can be difficult," write "in three instances this quarter, feedback from collaborators indicated that design decisions were finalised before input was requested, which created rework." Name the pattern, cite the evidence, state the cost.
How do first-time managers avoid bias in performance reviews?
Anchor every assessment in documented examples collected throughout the review period, not just the last few weeks. Recency bias is the most common distortion in reviews. Keeping a simple running log of notable contributions and incidents across the full cycle is the most practical defence against it.
What should a performance review action plan include?
A good action plan from a performance review names one to three specific development priorities, identifies the support or resource attached to each, sets a timeframe, and names who is responsible for what. Vague plans like "improve communication" fail because they have no defined next step or success measure.
How do pulse surveys connect to performance reviews?
Pulse surveys give managers a continuous read on employee sentiments between formal review cycles. When review conversations arrive, managers who have been tracking pulse data can speak to trends rather than impressions, making feedback more grounded and reducing the risk that the review feels like a surprise.
The thing nobody tells first-time managers about reviews
Performance reviews are not primarily a documentation exercise. They are a communication act. The form matters less than the quality of the conversation it structures. A first-time manager who shows up with specific examples, an honest assessment, and a concrete plan for what comes next will do more for employee engagement in one thirty-minute meeting than months of vague encouragement.
The examples in this guide are tools, not scripts. Take the structure and rebuild the phrases around the actual people in front of you. A review that clearly reflects the specific person and their specific work is the highest form of recognition a manager can offer. It says: I was paying attention. I know what you did. It mattered.
That is rarer than it should be. And people notice.
Start writing reviews that actually move things forward
Kodecrew gives managers the infrastructure to make performance reviews count: continuous feedback loops, pulse surveys that track employee sentiments across the full review cycle, real time analytics to spot patterns early, and communication tools that keep action plans alive between conversations. When HR teams build review processes on top of ongoing data, the review itself becomes the easiest part of the cycle. Explore Kodecrew to see how it works in practice.
