The Year in Review
An annual summary that hands the user a story about themselves.
The problem it solves
Twelve months of use leaves no impression. An annual recap converts accumulated data into something the user recognises as a record of their year, which renews the relationship and the subscription.
The year in review reads a user's own data back to them as narrative. Top items, totals, firsts, changes from last year. It works because the data is about them, it is specific, and it arrives at a moment when people are already inclined to look back.
It also does quiet commercial work. A user who has just seen what a year inside your product looked like is a user who understands their own switching cost for the first time. That is legitimate, as long as the numbers are real.
What makes one land
- 1Lead with a number only this user could have. Specific beats impressive.
- 2Give the number a comparison: last year, or the first month, or a plain-language reference point.
- 3Include at least one thing the user forgot, because recognition is the emotional payload.
- 4Keep it short enough to finish in one sitting on a phone.
- 5Make sharing available and optional, and do not gate the ending behind a share.
Avoid the rank framing unless the product is genuinely competitive. Telling someone they were in the top 2 percent of listeners is a statement about how much time they spent, and dressing volume as an achievement is the part of these recaps people have started to find uncomfortable.
Handle thin years with care. A user who barely used the product will get a recap that says so, and a cheerful summary of almost nothing is worse than no email. Set a floor of activity below which the recap does not send.
Worked example
Two framings of one number
A reading app can say: you read 41 books, more than 96 percent of readers. Or it can say: you read 41 books, and the one you went back to three times was this one. The first ranks the user against strangers. The second tells them something true about themselves, and it is the one they screenshot.
When it fits
- The product holds at least a year of data that is genuinely about the user's behaviour or taste.
- There are surprising details in that data, not only totals.
- The category has an annual rhythm, like music, fitness, finance, or reading.
- You can suppress the recap for users whose year was too thin to summarise kindly.
When it backfires
- The data is thin, so the recap is padded with generic filler and the user learns their year was unremarkable to you.
- Volume is framed as achievement. Congratulating someone for being in the top percentile of hours spent celebrates the exact behaviour a healthy product should be neutral about.
- The summary is sensitive. Spending recaps, health recaps, and dating recaps can arrive in a bad year and land as an unwanted audit of someone's life.
- Sharing is compulsory to see the ending, which converts a personal moment into a growth mechanic and users notice immediately.
Products using it
Spotify
Publishes an annual listening recap built from per-user play data, delivered as a short sequence of cards with share assets.
Strava
Produces an annual activity summary covering distance, elevation, and time by sport for each athlete.
Monzo
Sends an annual spending summary broken down by category and merchant from the user's own transaction history.
The psychology under it
The takeaway
An annual recap works when it tells the user something true and specific about themselves, and curdles when it congratulates them for volume.
Finished the teardown? Bank it and the day counts toward your run.