
Performance reviews are most useful when they replace vague labels with specific evidence. “Communicates well” gives an employee little information, while “summarizes decisions and owners after cross-functional meetings, reducing missed handoffs” identifies both a behavior and its value.
The phrases below are starting points, not complete evaluations. Managers should adapt them to the employee’s role, expectations and documented results. Avoid copying a phrase that is not supported by observable evidence.
A useful performance statement often contains four elements:
Behavior: What the employee did or did not do
Context: Where, when or how often it occurred
Impact: The effect on customers, colleagues, quality or results
Next step: What to continue, change or develop
For example:
During the last two launches, Jordan documented decisions and owners within one business day, helping the team close dependencies before release. Continue using this approach and add a risk summary for high-impact changes.
Use neutral, job-related language. Performance standards and review processes should be applied consistently, and employment decisions must not be based on protected characteristics or retaliation.
Communicates project status clearly and gives stakeholders enough context to make timely decisions.
Adapts technical explanations to the audience without losing important accuracy.
Listens carefully, confirms requirements and asks useful follow-up questions before acting.
Documents decisions, owners and deadlines consistently, reducing confusion after meetings.
Would benefit from sharing risks earlier so colleagues have more time to respond.
Sometimes includes more detail than the audience needs; prioritizing the main decision would improve clarity.
Should confirm understanding after complex discussions rather than assuming all participants interpreted the plan similarly.
Can improve written updates by stating the outcome, owner and required action at the beginning.
Builds productive working relationships across functions and shares information that helps others succeed.
Contributes constructively during disagreement and keeps the group focused on the shared objective.
Offers support during high-demand periods while maintaining responsibility for individual commitments.
Recognizes colleagues’ contributions and creates space for different perspectives.
Could involve affected partners earlier instead of presenting a nearly completed solution.
Needs to follow through more consistently on commitments made to other teams.
Would benefit from separating disagreement with an idea from judgment about the person presenting it.
Should clarify roles and decision rights at the beginning of cross-functional work.
Produces accurate work that consistently meets the team’s quality standards.
Uses appropriate checks before delivery and catches issues that could affect customers.
Maintains complete records and makes source information easy for others to verify.
Balances careful review with deadlines, focusing attention on the highest-risk details.
Needs a more consistent final review process to reduce recurring formatting and data-entry errors.
Should verify source definitions before combining figures from different reports.
Can improve quality by documenting assumptions and obtaining review for high-impact work.
Sometimes spends excessive time perfecting low-risk details; aligning effort with consequence would improve efficiency.
Prioritizes high-impact work and delivers key commitments by the agreed deadline.
Breaks complex assignments into manageable milestones and communicates schedule changes promptly.
Uses repeatable processes to handle recurring work efficiently without reducing quality.
Manages competing requests effectively by clarifying urgency, value and dependencies.
Would benefit from planning intermediate milestones instead of concentrating work near the final deadline.
Needs to communicate capacity limits earlier when accepting additional assignments.
Should distinguish urgent requests from important long-term work when setting daily priorities.
Can improve delivery predictability by tracking dependencies and escalation dates more consistently.
Defines problems clearly before proposing solutions and distinguishes symptoms from underlying causes.
Uses relevant evidence to compare options and makes assumptions visible.
Knows when to act independently and when a risk requires specialist or leadership input.
Reviews results after implementation and adjusts the approach when evidence changes.
Can strengthen recommendations by comparing alternatives rather than presenting the first workable option.
Should gather input from people closest to the process before finalizing a solution.
Needs to document the reasoning and risks behind high-impact decisions more consistently.
Would benefit from defining success measures before implementation so results can be evaluated objectively.
Establishes clear outcomes and gives team members appropriate ownership of how to achieve them.
Provides timely, specific feedback and supports employees in applying it.
Makes difficult decisions transparently and explains the tradeoffs affecting the team.
Develops others through coaching, stretch assignments and recognition of their contributions.
Should delegate meaningful responsibility instead of retaining too many operational decisions.
Can improve team focus by reducing shifts in priority without clear explanation.
Needs to address performance concerns earlier and document expectations more specifically.
Would benefit from seeking dissenting views before decisions that affect multiple teams.
Seeks to understand the stakeholder’s underlying goal instead of responding only to the initial request.
Sets realistic expectations and communicates changes before they become surprises.
Resolves concerns respectfully while protecting organizational policy and long-term trust.
Uses recurring feedback to improve processes rather than treating each complaint as an isolated event.
Should confirm scope, timing and success criteria before committing to stakeholder requests.
Can improve follow-up by documenting actions and closing the loop after an issue is resolved.
Needs to balance responsiveness with feasibility instead of promising outcomes before checking capacity.
Would benefit from analyzing patterns in feedback to identify preventive improvements.
Learns new tools and processes quickly and applies them effectively to active work.
Remains constructive when priorities change and helps colleagues understand the revised plan.
Seeks feedback and demonstrates visible improvement in the targeted behavior.
Transfers lessons from previous projects to unfamiliar situations without assuming the contexts are identical.
Can respond more effectively to change by asking clarifying questions before focusing on lost work.
Should create a defined learning plan for the skills required by upcoming responsibilities.
Needs to apply feedback consistently across assignments rather than only immediately after review.
Would benefit from testing new methods on a small scale before rejecting or adopting them broadly.
Takes ownership of agreed outcomes and raises risks before they threaten delivery.
Identifies useful improvements without waiting for detailed instruction.
Acknowledges mistakes promptly, corrects them and shares lessons that prevent recurrence.
Follows through on commitments and keeps affected colleagues informed of progress.
Needs to distinguish ownership from working alone and involve others when their expertise is required.
Should provide progress updates before being asked, particularly for overdue or high-risk work.
Can demonstrate greater accountability by explaining corrective action rather than focusing on external causes.
Would benefit from confirming priorities before starting self-initiated work that uses significant team resources.
Applies role-specific knowledge accurately and follows relevant standards and procedures.
Troubleshoots complex issues systematically and documents solutions for future use.
Keeps technical knowledge current and shares practical learning with colleagues.
Recognizes the limits of personal expertise and engages the appropriate specialist when needed.
Should strengthen proficiency in [tool or method] to complete [task] with less support.
Needs to follow required documentation and review procedures more consistently.
Would benefit from practicing [specific competency] through a defined project with measurable outcomes.
Can improve technical recommendations by connecting them more clearly to customer, operational and financial impact.
Replace broad language with evidence. Add:
The project or time period
Frequency or consistency
Scope, such as customers, budget or team size
A verified metric
The relevant performance standard
A clear continuation or development action
Generic:
Demonstrates strong teamwork.
Customized:
During the billing-system transition, Priya coordinated testing across finance, support and engineering, documented unresolved issues and helped the team complete launch without a critical customer-facing defect.
The customized version explains why the rating is justified.
Describe what happened rather than assigning a personality label. “Updates arrived after the weekly deadline in four of six reporting periods” is more useful than “is careless.”
Connect the behavior to work. Explain how it affected customers, timing, quality, safety or colleagues.
The employee may have information the manager lacks. Ask what contributed to the result and what support would help.
Define the expected behavior, measurement, resources and review date. “Improve communication” is not an actionable plan.
Reviews should not contain surprises. Managers should discuss important strengths and concerns throughout the year and maintain accurate, job-related records.
Consistently delivers accurate monthly forecasts before deadline and explains material changes clearly. During the last two quarters, the forecasts helped operations revise capacity before demand peaks. Next cycle, build a reusable scenario model so other analysts can apply the method.
Completes assigned customer analyses accurately and on schedule. Communicates questions early and incorporates feedback reliably. The next development priority is presenting recommendations more concisely to senior stakeholders.
Produces accurate analysis after review, but three of the last five reports required deadline extensions because dependencies were identified late. Beginning next month, create a milestone plan at kickoff and escalate missing inputs at least three business days before delivery.
Required safety checks were not documented for four scheduled inspections despite prior coaching and written procedures. Complete retraining by [date], use the approved checklist for every inspection and review records weekly with the supervisor for the next 60 days.
Ratings, consequences and improvement plans must follow organizational policy and applicable law.
Avoid:
Personality attacks such as “lazy” or “difficult”
Absolute words such as “always” and “never” without evidence
Feedback based on rumor
Comments about protected characteristics
Different standards for comparable employees
Vague praise that provides no development information
Medical or family assumptions
Surprising criticism never discussed before
Promises about promotion or compensation without authority
AI-generated feedback that was not verified
Managers should work with HR or legal specialists when the review involves discrimination concerns, accommodations, protected leave, discipline or termination.
Review goals and role expectations.
Gather verified accomplishments and feedback.
Note challenges and what you learned.
Identify resources or decisions that affected results.
Prepare two development priorities.
Ask for specific examples when feedback is unclear.
Discuss future scope and expectations.
Confirm agreed actions and review dates.
A self-review should be accurate rather than artificially modest or exaggerated. Give credit to collaborators while explaining your individual contribution.

Managers and employees may need to organize goals, achievements, feedback and development actions for a review conversation. Dokie can help turn approved, non-sensitive information into an editable presentation with evidence, outcomes, examples and next-period priorities.
Dokie is an AI presentation maker, so verify every statement and remove confidential personnel, health and compensation data before using source material. Apply company policy consistently and have HR review sensitive employment decisions; an AI-generated deck should never determine a rating by itself.
A good phrase describes observable behavior, gives relevant context, explains impact and identifies what to continue or improve.
Use neutral, specific language, explain the job-related impact, invite the employee’s perspective and agree on an actionable next step.
Yes. Examples make expectations and ratings easier to understand and verify.
Adapt them to the employee’s actual role and documented performance. Do not use a phrase that evidence does not support.
Focus on the competencies central to the role and a manageable number of development priorities rather than commenting on every possible trait.
Avoid irrelevant personal information, protected-characteristic comments, rumors, unsupported conclusions and confidential information not needed for the evaluation.
Important feedback should be given throughout the year. The formal review should summarize an ongoing process, not introduce avoidable surprises.
AI may help organize manager-provided evidence, but a qualified person must verify the language, remove sensitive data and remain accountable for the evaluation.