Team and Culture · Published March 21, 2026
An Annual Review Worth Writing
An annual review should not be a log. It should answer one question: where did you get stronger?
For years our reviews were project lists: what you joined, what you achieved. They did little for growth. We gradually settled on a more useful structure, and everyone follows it now.
Four sections
What you shipped: no more than five items, focused on outcome and impact rather than process.
What you learned: concrete shifts in skill, method or perspective, ideally with an example.
What you got wrong: at least one, with cost and correction. A review without mistakes means reflection has not started.
Who you want to become next year: one capability or role, specific enough to act on.
How managers use it
Read every review and discuss parts three and four in the meeting, not numbers.
Aggregate common asks into team plans: if several people want architecture exposure, arrange the talks and projects.
Archive reviews and reopen last year's before writing; count what actually happened.
An annual review matters less for looking back than for choosing where the next year of time goes. Write it honestly and it repays the hours.
← Previous post
Retrospective: Translation Is Not Copy-Paste
Next post →
Education Procurement: Buyers Who Cannot Specify
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →