Performance Reviews
Overview
Performance reviews are formal reflections on impact, growth, and behaviors over time.
Why It Matters
Good review material helps you tell the story of your work accurately and usefully.
Core Concepts
- Focus on impact.
- Capture examples throughout the cycle.
- Separate results from effort.
Mental Models
Think in evidence. Strong reviews use concrete outcomes, not just claims.
Best Practices
- Keep a work log.
- Record the problem, action, and outcome.
- Include collaboration and leadership impact.
Common Mistakes
- Waiting until review time to remember your work.
- Listing tasks without outcomes.
- Underselling cross-functional impact.
Trade-offs
Regular tracking takes a little effort, but it makes review season much easier and more accurate.
Decision Framework
| Evidence type | Example |
|---|---|
| Delivery | Shipped feature or fix |
| Impact | Reduced incidents or cycle time |
| Leadership | Helped unblock others |
Examples
- “Reduced bug recurrence by adding a shared fix and regression test.”
Checklists
- Do I have concrete examples?
- Did I capture impact, not just activity?
- Did I include collaboration and growth?
Senior Engineer Notes
Senior engineers keep a running record so performance conversations are grounded in reality, not memory drift.