LinkedIn — shipped, learned, next
[Company] in [year]: What we shipped: - [Release or milestone] - [Release or milestone] - [Release or milestone] What did not work: - [Honest miss and what it taught you] What we learned: - [Lesson] What is next in [next year]: - [Plan, without dates you cannot keep] Thank you to [customers, team, community]. We would not have made it through [hard moment] without you.
X — 6-post recap thread
1/ [Year] for [Product], in 5 posts. 2/ Shipped: [top 3 releases]. 3/ Grew: [metric you can share] from [start] to [end]. 4/ Missed: [goal you did not hit] and why. 5/ Learned: [one lesson]. 6/ [Next year]: [one priority]. Thanks for being here.
Mastodon — community recap
[Project] in [year]: [Number] releases [Number] contributors, [number] of them first-time [Number] issues closed Favorite moment: [moment]. Thanks to everyone who filed a bug, wrote docs, or answered a question. #[ProjectTag] #YearInReview
Bluesky — personal recap
My [year]: [one-line summary]. Best decision: [decision]. Worst decision: [decision]. Next year, more [thing], less [thing].
Tips
- Include at least one miss. A recap of only wins reads as a press release and is quickly scrolled past.
- Use numbers you can verify and have shared before. Year-end posts are often quoted back to you.
- Link each shipped item to its release notes or post so the recap doubles as an index.
- Post before the last week of December or right after New Year, when feeds are quieter but attention is lower; test both.
Frequently asked questions
When should I publish a year in review post?
Mid to late December or the first week of January are common. Pick a date when your team can respond to comments rather than a day everyone is offline.
Can an agent gather the year's releases into a draft?
Yes. An agent can pull the year's published posts and releases, fill this template, and send the draft to SocialHandoff for you to edit and approve before it goes out.