Year in Review Template for Product Strategy

The written document should be thorough enough that someone who was not involved can understand the year's outcomes. A 10-15 page document is typical. The presentation version should be 15-20 slides, focusing on the executive summary, metric trends, top wins and misses, lessons learned, and forward recommendations. Appendices can hold supporting data.

Start data collection in the last two weeks of the year. Draft the document in the first week of January. Aim to present the review to leadership by mid-January. The best reviews are prepared quickly while the year's context is still fresh.

Acknowledge the original goal, explain why it was changed, and evaluate against the revised goal. Changing goals mid-year is not a failure. It shows strategic adaptability. But if goals change every quarter, that signals a planning problem worth addressing.

No. The year in review is a product and team-level document. Individual performance belongs in 1:1s and formal performance reviews. The year in review should recognize contributions by name but not evaluate individuals publicly.