Set clear goals, discuss progress, and turn review conversations into useful next steps.
The performance review invitation arrives, and the search begins.
Tickets. Documents. Messages. That project from March. The problem you helped another team solve. You remember working hard, but explaining what changed because of your contribution takes more effort than expected.
Meanwhile, the manager is preparing an assessment. Perhaps a recent success stands out more clearly than months of reliable work. Perhaps they have concerns they have never clearly discussed with the person.
By then, much of the opportunity to influence that year’s performance has passed.
A useful performance review draws on expectations, evidence, and feedback discussed throughout the year. It looks backward to assess contribution and uses that understanding to choose the next goals, support, and adjustments.
Preparing the document matters. So does the work that should happen before there is anything to write.
Agree on what good performance means
Individual performance means fulfilling a role and creating the impact expected from it. Outcomes matter, alongside judgment, collaboration, and how the work gets done.
That definition needs to become specific between a person and their manager.
An engineer asked to improve reliability needs more than “take more ownership.” Which problem should improve? What decisions can they make? What support is available? What evidence would show progress?
I have experienced both strong performance and periods when I struggled. I believe clear priorities matter enormously: knowing what I am trying to achieve, why it matters, and how today’s work connects with a longer-term direction.
My recommendation is to keep that direction focused, with no more than three prioritized longer-term objectives. Translate the relevant ones into goals for the next six to twelve months, connected to the team’s needs and reviewed at shorter intervals.
Goals also need an agreed meaning.
A committed goal carries an expectation of completion. An aspirational goal sets an ambitious direction where full attainment is uncertain. Google’s OKR playbook makes this distinction explicit.
That differs from separating delivery goals from development goals. Improving a skill can be a firm commitment. A business outcome can be aspirational.
For development, replace “improve stakeholder communication” with an observable practice: lead the next project update, explain the decision and its business implications, request feedback, and apply it in the following update.
Then assess whether the communication became clearer: could the audience explain the decision, its implications, and what they needed to do next? Use their feedback to prepare the following update.
Agree on what progress would look like, when to discuss it, and what support the manager will provide. Revisit the agreement when priorities change.
Build a habit of evidence, feedback, and adjustment
A goal needs a place in everyday work.
If communication is the development priority, prepare the update before the meeting. If technical judgment is the priority, write down the options and trade-offs before asking for a decision. Put the practice into a routine you can repeat, especially when motivation is low.
Then keep a brief record, weekly or monthly. At least once a quarter, bring the notes together and examine the pattern.
For each meaningful contribution, capture:
- What was expected?
- What did I contribute, and what changed?
- What evidence or feedback supports that assessment?
- What did I learn, and what will I adjust?
Keep setbacks and changed priorities alongside achievements. This is a working record for learning and evaluation, so it needs to represent the period honestly.
In engineering, “implemented monitoring” describes an output. Evidence that the monitoring helped detect a problem earlier shows something about its usefulness. If that evidence is still missing, record what was enabled without claiming an outcome you cannot demonstrate.
Also distinguish your contribution from the team’s result. Explain the decisions you made, the work you owned, and how you helped others contribute.
Reflection is part of the work. Research described by Harvard Business School found benefits from deliberately reflecting on experience in experimental and training settings. It supports making room for reflection, rather than assuming that more experience automatically produces more learning.
Personal reflection still needs other perspectives.
Discuss meaningful observations while there is time to act. MIT’s guidance on coaching and feedback emphasizes year-round, two-way conversations and timely feedback about specific behaviors and their effects.
A leader who notices unclear technical updates should identify what was missing, explain the consequence, hear the person’s perspective, and agree on a next attempt. Waiting until the annual review leaves fewer opportunities to practice.
The same applies to strengths. Explain what worked and why it helped, so the person knows what to repeat.
For your own review, ask for a current assessment: “Where am I meeting expectations, and what needs to change?” For people you lead, take responsibility for making that assessment discussable. They should not have to discover an important concern by asking exactly the right question.
Use the review to assess and choose
The formal review brings the period together.
Compare contribution with the expectations that applied at the time. Consider results, behavior, feedback, constraints, and changes in priorities. A missed target deserves explanation; a completed target still needs context.
Keep three questions distinct:
- Performance: How well did the person fulfill their role during this period?
- Potential: What future responsibilities might they grow into, and what supports that expectation?
- Seniority: At what level of scope and complexity does the person consistently demonstrate sound judgment, autonomy, and influence?
Organizations combine these conversations differently. The distinction remains useful: enthusiasm for someone’s future should not replace an assessment of current contribution. Strong performance in the current role does not automatically establish readiness for a broader one. Years of experience alone answer neither question.
Prepare one concise page with five parts:
- Expectations: The role, priorities, and agreed goals, including changes during the period.
- Evidence: Meaningful contributions, outcomes, behaviors, and your part in shared results.
- Feedback: Strengths, concerns, differing perspectives, and what happened after earlier conversations.
- Learning: What improved, what remains difficult, and what you would approach differently.
- Next commitments: The next priorities, repeated practices, support, and dates to review progress.
Use the page to make the conversation concrete. Where perspectives differ, identify the specific evidence or expectation in question. Where support was promised, examine whether it happened.
The review should leave both people clearer about what to continue, change, or stop.
Start with the review ahead of you
If your review is approaching, begin with the evidence available. Reconstruct the important contributions, acknowledge gaps, and discuss unresolved expectations before the formal meeting.
If you lead others, raise concerns now. A late conversation cannot restore months of practice, and it would be unfair to assess the whole year against a standard introduced at the end.
Then put the next checkpoint on the calendar and choose one practice to repeat before it.
When the next review invitation arrives, you should have a record of work already discussed, lessons already applied, and decisions already revisited. The preparation becomes bringing that history together, with enough evidence to decide what comes next.