Good Bad Better Best

A four-column format that turns reflection into a ladder of improvement. The team names what was good and what was bad, then pushes further to what could be better and recognizes the very best results, performances and people. Ending on the high note of best keeps the energy positive and celebrates standout contributions.
Good

Went well

Roman

Roman

Zero rollbacks this sprint
Maria

Maria

Review turnaround under a day
Bad

Went poorly

Anna

Anna

Two tickets rolled over for the third sprint
Daria

Daria

The hotfix went out without a test
Better

Improvement opportunities

Maria

Maria

Split anything estimated over two days
Kirill

Kirill

Move refinement to Monday so planning is short
Best

Recognize outstanding results, performances, actions, people

Daria

Daria

Ana's incident write-up became the runbook we now use
Roman

Roman

The team held the release date without overtime

A retrospective is an essential tool for a team that allows you to evaluate the past period, identify strengths and weaknesses, and determine paths for improvement. In this template, we will consider four key aspects: Good, Bad, Better, and Best. This will help you structure the discussion and make it more productive.

Good

In this section, we will focus on what went well. These can be both small successes and significant achievements. It is important to note all positive moments so that the team can feel its effectiveness and motivation.

  • Processes and Methods: Which processes or methods worked particularly well?

  • Communication: Were there moments when the team communicated particularly effectively?

  • Results: What results were achieved and exceeded expectations?

  • Individual Achievements: Who among the team members stood out with their achievements?

Bad

In this section, we will look at what did not go so well. It is important to be honest and open to identify problems and find ways to solve them.

  • Problems and Difficulties: What problems arose during the work process?

  • Communication: Were there moments when communication was ineffective?

  • Results: Which results did not meet expectations?

  • Individual Difficulties: Who among the team members faced particular difficulties?

Better

This section is dedicated to opportunities for improvement. Here we will discuss what can be done better in the future to avoid repeating mistakes and increase the overall effectiveness of the team.

  • Processes and Methods: Which processes or methods can be improved?

  • Communication: How can communication within the team be improved?

  • Results: What steps can be taken to improve results?

  • Individual Opportunities: How can team members be supported to work better?

Best

In this section, we recognize outstanding results, achievements, and actions. This is important for maintaining high morale and motivation within the team.

  • Processes and Methods: Which processes or methods were so effective that they should be implemented into daily practice?

  • Communication: Were there moments when communication was so effective that it should be taken as an example?

  • Results: Which results were so outstanding that they should be particularly noted?

  • Individual Achievements: Who among the team members performed so outstandingly that their merits should be particularly noted?

Conclusion

A retrospective is not just a formality but an important tool for improving the team's work. Remember that honesty and openness are key elements of a successful retrospective. Discuss both positive and negative moments, look for ways to improve, and recognize outstanding achievements. This will help your team become stronger and more effective.

Example of Using the Template

Good

  • Processes and Methods: The new task management system significantly improved our productivity.

  • Communication: Weekly meetings helped us understand each other better.

  • Results: We completed the project a week ahead of schedule.

  • Individual Achievements: Anna exceeded all expectations in her role.

Bad

  • Processes and Methods: Issues with suppliers delayed our project.

  • Communication: Lack of information led to confusion.

  • Results: Some tasks were not completed on time.

  • Individual Difficulties: Ivan faced difficulties working with the new system.

Better

  • Processes and Methods: We need to improve interaction with suppliers.

  • Communication: Daily short meetings should be introduced for information exchange.

  • Results: It is necessary to plan tasks more carefully.

  • Individual Opportunities: Support Ivan in mastering the new system.

Best

  • Processes and Methods: The new task management system should become the standard for all projects.

  • Communication: Weekly meetings should continue and be improved.

  • Results: Completing the project ahead of schedule is an outstanding achievement.

  • Individual Achievements: Anna deserves special recognition for her work.

Use this template to conduct a retrospective, and you will see how your team becomes more cohesive and effective.

Similar templates

Other formats teams pair with this one — open any of them as a board in one click.
Likes / Wishes / Wonders
A concise, exploratory format that blends feedback with curiosity. Participants share what they liked, what they wish were different and what they wonder about going forward. The wonders column invites open questions and fresh ideas, making it a great fit for teams exploring new ways of working.
OKR Template
A goal-focused format that ties reflection to objectives and key results. The team reviews its objectives, examines the key results that measure progress and aligns on the initiatives that will drive them forward. It's a strong choice for connecting day-to-day retrospectives with the bigger goals the team is accountable for.
Retrospective Template: WWW
A nuanced take on the classic what-went-well format that adds a middle ground. Instead of a strict worked-or-didn't split, the team also captures what kinda worked — the partial successes and half-measures. That extra shade often holds the most useful insights, where small adjustments can turn a near-miss into a win.
Safety Check for Retrospective
A short anonymous poll that measures how safe people feel to speak openly before the real retrospective begins. Everyone rates their comfort from 1 to 5, and the aggregated result tells the facilitator whether the team is ready for candid conversation. It's a valuable warm-up for new teams or after tense periods, where psychological safety can't be taken for granted.
Fishbone Analysis Retrospective Template
Also known as the Ishikawa diagram, this format helps the team trace a problem back to its root causes. Possible causes are grouped across categories like people, process, tools, program and environment before the team converges on solutions. It's a methodical choice when a recurring issue needs a structured investigation rather than a quick fix.
WRAP Retrospective
WRAP gathers four kinds of input that together give a rounded view of the sprint. The team shares its wishes, voices appreciations, names the risks it sees and surfaces the things that still puzzle it. Mixing gratitude with concern keeps the conversation both supportive and honest.
Try Template