the december problem
every year-end the feed turns into one long recap. "what a year it's been." "grateful for every single one of you." "2026, you were a rollercoaster." a hundred posts with the same skeleton, the same three emojis and the same closing line about the year ahead.
nobody hates year-in-review posts. people hate reading the same one forty times. the format is fine. the template is the problem.
pick one thread
the default recap is a list: new job, a trip, a launch, a course, a half marathon. lists are easy to write and hard to remember.
pick the one thing that actually changed this year and hang everything else off it. "this was the year i stopped saying yes to every meeting" gives the reader a story to follow. the launch and the trip can still appear, as evidence.
ask yourself: if a friend asked "so how was your year?" over coffee, what would you say first? that's the thread.
specific beats impressive
"grew the team" is forgettable. "hired four people, and two of them were people who had applied and been turned down the year before" is a post.
the details only you know are the ones that make the post yours, and they are what a recognizable voice is built from. numbers, names of places, the exact thing someone said. generic summaries are what everyone else is posting.
put one miss in it
an all-wins recap reads like a humble brag with a calendar attached. include one thing that went wrong: the project that got cancelled, the habit that lasted three weeks, the decision you'd make differently.
keep it short and skip the redemption arc. "i spent four months on a product nobody wanted. the next one started with ten customer calls instead" is enough. you don't need to turn every failure into a lesson in bold.
phrases to cut
these show up in so many year-end posts that readers skim past them:
- "what a year it's been"
- "a year of growth" / "a year of learning"
- "rollercoaster"
- "grateful for each and every one of you"
- "i'm so humbled"
- "here's to an even bigger 2027"
- "new year, new me"
if your draft leans on them, it probably has other tells too, like the staccato "no x. no y." fragments and the inspirational closer. paste it into the slop detector before you post. the blacklist has the full list of patterns we refuse to generate.
a simple structure
- the thread. one sentence that names what the year was about.
- three to five moments. specific, in order, each one a line or two.
- the miss. one honest thing that didn't work.
- the thanks, if you mean it. name people. "thanks to my network" thanks nobody.
- one line about next year. a plan, not a slogan.
example
this was the year i stopped writing for an audience i imagined and started writing for the 40 people who actually reply.
in march i deleted a post schedule i'd kept for two years. in june a short post about a bad client call got more replies than anything i'd planned. in october i turned those replies into a workshop, and 11 people paid for it.
the miss: i spent the summer on a newsletter i never sent. three drafts, zero issues.
thank you, sara and jon, for reading the ugly versions.
next year: one post a week, written for the 40.
no confetti, no "what a ride." and it's still a celebration.
timing
most recaps land in the last two weeks of december and the first days of january, which is exactly when the feed is fullest of them. a recap posted in early december, or a "what i learned" post in mid-january, competes with far fewer.
and if you write it and it still reads like everyone else's, that's information too. the ai post generator drafts a voice from one sentence about you and writes in it, so the recap starts from your year rather than a template.
