How to Ace the Annual Review Season and Give Feedback Like a Pro

Track your daily wins and give specific, meaningful feedback to your colleagues

From a blank page to a full work log, how to bridge the gap during review season. (AI-generated image)

Not a Medium Member? Read this story via my “Friend Link” here.

It’s that time of year again. The “Review Season” notification pops up in your inbox, and suddenly, a cold shiver runs down your spine. You sit down to write your self-assessment, staring at a blank document, and realise with a sinking feeling that you can’t remember a single thing you did before last Tuesday.

We’ve all been there. We suffer from Recency Bias, the tendency to only remember the fires we fought or the wins we had in the last 30 days. But your annual review is supposed to cover twelve months, not four weeks.

If you’re relying on your memory (or your manager’s) to capture a year’s worth of impact, you aren’t just doing yourself a disservice; you’re likely leaving a promotion or a bonus on the table.

If you’re a developer, you might think, “I’ll just look at my closed Jira tickets and merged PRs.” If you’re a TPM or a Senior Tech Lead, you might not even have that.

But here is the reality: The most impactful work often happens outside of a ticket. It’s the comment you left on a design doc that steered the project away from a $50k mistake. It’s the Slack thread where you unblocked three different teams. It’s the email you sent to a stakeholder that kept a project from being cancelled. Because of retention periods and the sheer noise of “searchable” systems like Quip or Slack, these “invisible” wins vanish into thin air.

If you can’t remember them, don’t expect your manager to. They are managing five to ten other people; they aren’t your biographer.

The Solution: The “Minimum Effort” Work Log

I’ve tried the complex, colour-coded, heavily structured productivity systems. You know what happened? I stopped using them after three days.

The key to a work log isn’t the structure; it’s the consistency. And to stay consistent, it has to be dead simple. Here is the playbook for your Daily Work Log:

1. Keep it Open, All Day

Don’t wait until 5:00 PM to “recap” your day. You’re already tired by then. Keep a simple document open alongside your email. Every time you finish a meeting, send a major email, or get a “thanks!” on Slack, drop it in.

2. Low Friction is King

Don’t write essays. Write one sentence. Put a link/screenshot and move on.

• Wrote the V1 of the Roadmap Doc [Link]
• Feedback to Sarah on the API design [Link to Quip comment]
• Resolved the conflict between Team A and B regarding the database migration [Screenshot of email]
• Sent the team on the correct path for root-causing high-severity issue [Link to the ticket comment]

3. Focus on the Habit, Not the Streak

If you skip a day, don’t sweat it. I’ve seen people give up on tracking entirely because they missed a Wednesday. In the grand scheme of a 365-day year, one missing day doesn’t matter. Just pick it back up on Thursday.

Peer Feedback Like a Pro

We also have to write feedback for our colleagues. Usually, we write something generic like, “They’re great to work with!” because we can’t remember the specifics.

Don’t be that person. Have a separate document for your peer feedback. When someone does something awesome (or something frustrating), jot down their name and a single line. When review season hits, you can give them high-quality, actionable feedback that actually helps their career.

Pro-Tip: When you ask someone for feedback, don’t just send a blank request. Remind them of what you did together. Use your work log to say: “Hey, It’s annual review time! Remember when we collaborated on the Q3 Migration and I helped resolve those three blockers?” It makes their life easier and ensures your best work is highlighted.

Leveraging the “AI Era”

We live in the age of AI tools, so let’s use them. At the end of the year, you don’t have to manually summarise 200 pages of notes.

1. Categorise: Group your notes by project or workstream.
2. Prompt: Feed your log into an AI (ensuring you follow your company’s data privacy policies!) alongside your Role Guidelines.
3. Refine: Ask the AI to: “Based on these role guidelines for a Senior TPM, summarise my impact from these notes, focusing on leadership and technical complexity.”

You’ll be amazed at how much “lost” work resurfaces. Suddenly, your self-assessment isn’t a work of fiction; it’s a data-backed record of a successful year.

Key Takeaways for Your Success:

• Stop trusting your memory: Recency bias is the enemy of career growth.
• Track the “Invisible”: Slack, emails, and doc comments are where the real impact lives.
• Simplicity = Consistency: If the system is hard to use, you won’t use it.
• Help others help you: Give specific peer feedback and remind others of your wins.

How do you currently track your wins? Do you have a “Brag Document” or are you still relying on your memory? Let me know in the comments!

Disclaimer: The core ideas presented in this article are solely from the author. A generative AI model (Gemini) was used to enhance the structure and speed of drafting and editing. The final article has been thoroughly reviewed and edited by the author.