Performance reviews are usually rushed, generic, and not useful to the employee. The version that works requires structured thinking that managers rarely have time for. Claude accelerates the synthesis. The judgment stays human. Here is the workflow.
Most managers do reviews under time pressure, write generic feedback, and the employee leaves the conversation without specific direction. Net effect on performance: minimal.
A useful review has 3 elements: specific examples (not generalizations), forward-looking development (not just retrospective), and a clear next-period focus. Claude helps with each.
I am writing a [QUARTERLY / ANNUAL] performance review for [EMPLOYEE NAME, ROLE].
Review period: [DATES]
Goals at start of period: [PASTE]
Measurable outcomes: [PASTE]
My observations as their manager (raw notes): [PASTE]
Peer feedback (anonymized): [PASTE]
What they said they wanted to learn this period: [PASTE]
Draft the review:
1. Overall rating with 2-paragraph justification (specific examples, not generalizations)
2. 3 strengths with specific moments demonstrating each
3. 2-3 development areas with specific examples and a forward growth path
4. Goal performance — for each goal: status, what happened, what we learned
5. Goals for next period (3-5, SMART, connected to their growth interests)
6. Career conversation: where they want to go and what would unlock it
Voice: direct, specific, balanced. Equal parts honest about gaps and clear about strengths. Do not use platitudes ("great team player"). Calibration with peers. Comparing this person to others on the team requires manager judgment.
Difficult conversations. Performance issues that may lead to termination — manager and HR own this.
Compensation decisions. Tied to review but separate decision.
The actual delivery. The conversation is the thing that matters; the doc supports it.