Three Horizons retrospective template
Three Horizons asks the team to place each topic by when it matters: in the next sprint or two, over the next few months, or a year or more out. A retro usually fills up with near-term problems, and this format makes room for the slower ones that never feel urgent enough to raise.
Try it free
Free to start. Your team joins with a link.
When to use it
- Teams whose retros only ever cover the last two weeks
- Planning around a roadmap change or a reorganisation
- A quarterly retro, when there is time to look further ahead
The columns
Near Term
What needs attention in the next sprint or two?
For example
- The release checklist keeps getting skipped
- Nobody owns the flaky test suite
Middle Term
What is starting to show and will matter in a few months?
For example
- Onboarding takes new joiners three weeks
- The design system is drifting between teams
Long Term
What should we be working towards in a year or more?
For example
- Moving off the legacy billing service
- Every team able to deploy on its own
Facilitator tip
Vote within each horizon rather than across the board, or the near term will win every time.
Other formats
- Three Little Pigs retrospective
- 4Ls retrospective: Liked, Learned, Lacked, Longed For
- Anchors and Engines retrospective
- Drop, Add, Keep, Improve retrospective
- Lean Coffee retrospective
- Mad, Sad, Glad retrospective
- Mountain Climber retrospective
- Original 4 questions retrospective
- Sailboat retrospective
- Starfish retrospective
- Start, Stop, Continue retrospective
- SWOT retrospective
- What Went Well retrospective
- Genie in a Bottle retrospective
- Curse, Blessing, Quest retrospective