How to Write an Actually Honest Year-End Retrospective

Retro Season Is Here Again

December rolls around and timelines flood with retrospective posts. "Best decisions this year," "goals for next year," "how I grew." I write one too. Third year running. But this time I want to try something different. I reread last year's retro and cringed. (Genuinely cringed.)

Let's Look at What I Wrote Last Year

"This year I deeply studied TypeScript and contributed to improving our team's code quality." Reality? I bought one TypeScript book and read three chapters. The rest I solved by Googling as needed. "Deeply studied" should've been "looked things up when I had to."

"Completed 2 side projects." One was actually completed. Total users: 3, including me. The other one? I created a repo and wrote a README. Last commit was in March.

Why Retrospectives Turn Into Self-Justification

There's something we do unconsciously when writing retros. We write "what went well" first, then minimize or sugarcoat "what didn't." We write "didn't have enough time" when we actually binge-watched Netflix. We write "reprioritized" when we actually just didn't feel like it.

Publishing it publicly makes it worse. Knowing others will read it, you naturally package things nicely. The desire to show "look how much I grew this year."

What It Looks Like When I'm Actually Honest This Year

What went well: I barely missed any work days. (Calling this an achievement feels pathetic, but last year I had 7 absences, so technically it's progress.)

What went wrong is a longer list. Out of 5 January goals, I achieved 1.5. Solve an algorithm problem daily? Quit by the third week of February. Study English? Duolingo streak died at day 17. Blog once a week? Wrote nothing from July through October.

Here's How to Write an Honest Retro

First, only write facts with dates. Instead of "studied hard," write "read the React 19 docs in March and gave one team seminar about it." Specific dates and counts. No emotions or assessments.

Second, include numbers. Instead of "blogged consistently," write "published 14 blog posts. Goal was 52. Achievement rate: 26.9%." Numbers don't lie.

Third, write specific regrets. Not vague stuff like "there were some disappointments," but concrete things like "got a job offer in August, rejected it without even interviewing, and I still wonder about it."

What's the Real Purpose of a Retrospective?

It's not for showing others. It's comparing who you were a year ago with who you are now. Hopefully you grew, but there are definitely areas where you regressed. Acknowledging that is where retrospection starts.

My retro this year won't look impressive to anyone. But that's correct. The goal isn't writing a polished retro -- it's writing an honest one and deciding what to actually change next year.

...Though writing that makes me wonder if this whole post is just packaging myself as "the honest guy." There's no escape.