Love - Want - Hate - Learn
An emotionally honest format that gives feelings a clear place in the retrospective. Participants finish four sentences — I love, I want to, I hate and now I know that — to surface what energizes them, what they wish for, what frustrates them and what they've realized. The personal phrasing invites genuine, first-person reflection.
What you genuinely enjoy about how the team works
Roman
I love that reviews come back the same day now
Maria
I love having a real staging environment
Changes you want, phrased as your own wish
Anna
I want to spend a sprint day on tests, not features
Daria
I want to see the roadmap before planning, not during
What frustrates you — the honest, unfiltered version
Maria
I hate reruns of flaky tests to get a green build
Kirill
I hate finding out about scope changes in a meeting
Discoveries from this sprint the whole team should share
Daria
Now I know the export times out over 10k rows
Roman
Now I know support has a workaround doc we never read
This retrospective template is a simple and effective way for your team to share their experiences and insights from the iteration phase. The idea behind the template is to encourage open and honest feedback by giving team members the opportunity to express what they love, want, hate, and have learned.
I love ...
- This section is for team members to share what they really enjoyed about the iteration phase.
- This could be anything from a specific task or project, to a team member's contribution, to a tool or process that made a difference.
I want to ...
- This section is for team members to express what they want to see more of in the future.
- This could be a specific change or improvement, a new tool or process, or a continued focus on something that was particularly effective.
I hate ...
- This section is for team members to share what they didn't like about the iteration phase.
- This could be a specific task, process, or tool that didn't work well, or a behavior or attitude that was disruptive or unproductive.
Now, I know that...
- This section is for team members to share what they have learned during the iteration phase.
- This could be a new skill or knowledge, a better understanding of a challenge or issue, or a realization about the team or project that they didn't have before.
Similar templates
Other formats teams pair with this one — open any of them as a board in one click.
Kudos Retrospective
A retrospective that opens with gratitude before getting down to business. Kudos lets the team recognize each other first, then it reviews what went well, what to improve and the action items to follow up on. Starting with appreciation sets a positive, psychologically safe tone for the harder parts of the conversation.
Pros and Cons
The simplest possible way to weigh a decision, a change or the sprint as a whole. The team lists the pros on one side and the cons on the other, making trade-offs visible at a glance. Its bare-bones structure makes it a versatile choice whenever a balanced view is needed quickly.
Sprint Diagnostics
A diagnostic format that combines a quick rating with focused discussion. The team scores the sprint on dimensions like communication, collaboration, quality and pressure, then names a standout like or dislike and what could be done differently before agreeing on actions. The numbers give an easy way to track how the team's health changes over time.
3 L's
A lightweight three-column retrospective for teams that want quick, honest feedback. Participants capture what they liked, what they learned and what they lacked during the sprint. Stripped down to the essentials, it's an easy starting point for teams new to retrospectives or short on time.
DAKI
DAKI gives the team four clear levers for change in a single view. Participants decide what to drop because it no longer helps, what to add that's missing, what to keep that works well and what to improve. The crisp structure makes it easy to leave the session with a concrete, balanced set of adjustments.
SWOT Analysis
A strategic format borrowed from business analysis and adapted for team reflection. The team maps its strengths and weaknesses against external opportunities and threats to see the bigger picture. It works especially well for longer horizons — a quarter, a release or a project — where strategy matters as much as day-to-day fixes.
