Build performance conversations from the work
A dated evidence brief organizes outcomes, feedback, commitments, growth, and open context without generating a rating.
The problem
Performance reviews overweight the last few weeks, manager memory, and polished self-advocacy.
What you get
A working system with the steps, tools, checkpoints, and expected return made explicit.
- Setup
- 45 minutes
- Back each week
- 1 hours
- Difficulty
- assisted
Expected return
The working case
A planning estimate, not a guaranteed result. Measure the first four weeks against your own baseline.
48
hours returned per year
At 1 hours/week across 48 working weeks.
1
week to earn back setup
Compare the setup estimate with the weekly time returned.
Operating contract
Input
The source material, constraints, and examples a human would need to do this work well.
Checkpoint
A person reviews judgment calls, sensitive content, unfamiliar tools, and irreversible actions.
Success signal
Track time returned, corrections required, and exceptions. Keep it only if the measured result compounds.
Before you start
- ·Published role expectations
- ·Approved review evidence sources
The steps
- 01
Gather approved goals, delivered outcomes, dated feedback, prior commitments, and employee self-reflection.
- 02
Map evidence to the published role expectations and review period.
- 03
Draft a balanced evidence summary with missing context and recency checks.
Copy this prompt
Organize this evidence for a performance conversation. Separate outcomes, behaviors tied to published expectations, growth, feedback, and unresolved context. Cite dates and sources. Do not assign a rating, infer intent, or compare employees. Inputs: [evidence]
- 04
Manager validates the evidence and conducts the human conversation.
What it runs on
- Lattice
Controlled review and goal source.
- Google Docs
Private manager preparation.
Where this goes wrong
- Never infer sentiment, potential, or protected traits.
- Access must be restricted to the employee process and authorized reviewers.
Definition of done
Run it for four weeks. Then make it earn its place.
- □ Baseline the manual time before launch.
- □ Keep a human approval step for consequential output.
- □ Record corrections and exceptions, not just successes.
- □ Expand, revise, or retire it after the first review.
Build the system around it
Related workflows
If this one stops working, tell us. Three reports in a month and it leaves the library until a person has looked at it again.