Login

Retrospective Template: Good, Bad, Learned, and Learning

A learning-focused format that adds a forward-looking twist to the classic review. The team reflects on what went well and what didn't, then looks at what it wanted to learn this sprint — and whether it did — before naming what it wants to learn next. The emphasis on continuous learning makes it a great fit for teams investing in their own growth.
What went well?

Successes worth repeating on purpose

Roman

Roman

The migration finished early with no data loss
Maria

Maria

Two juniors took over review duty and it stuck
What didn't go so well?

What went wrong or cost the team time

Anna

Anna

We missed the sprint goal by two tickets again
Daria

Daria

The environment nobody owns cost us two days
What did I want to learn this sprint and did I?

Learning goals you set for this sprint and how they went

Maria

Maria

I wanted to learn the deploy pipeline and I did — I ran two releases
Kirill

Kirill

I meant to learn the billing domain but never got time
What do I want to learn next sprint?

What you want to learn next and what you need for it

Daria

Daria

Next sprint I want to write my first migration end to end
Roman

Roman

I want to shadow an on-call rotation
Try Template

What is the Good, Bad, Learned, Learning retrospective?

The Good, Bad, Learned, Learning retrospective is a sprint review format that goes beyond simple wins and problems. It deliberately adds a learning lens, asking the team not only what happened, but what each person set out to learn and what they want to grow into next. This makes it a strong fit for teams that treat every sprint as a chance to build skills, not just ship features.

  • What went well?
  • What didn't go so well?
  • What did I want to learn this sprint and did I?
  • What do I want to learn next sprint?

What went well?

Capture the wins, smooth deliveries, and moments of strong collaboration. Naming what worked reinforces good habits and gives the team a positive starting point before tackling harder topics.

What didn't go so well?

Surface blockers, friction, and disappointments honestly. The goal is not blame but clarity: spotting the patterns that slowed the team down so they can be addressed.

What did I want to learn this sprint and did I?

Each person revisits the learning goal they had at the start. Reflecting on whether it was met turns vague intentions into accountable, visible growth.

What do I want to learn next sprint?

Set the next learning intention. This column connects one sprint to the next and keeps personal development on the team's radar.

Benefits of this retrospective

  • Combines delivery review with explicit skill growth
  • Holds learning goals accountable sprint over sprint
  • Encourages honest reflection in a safe structure
  • Builds a culture of continuous improvement
  • Gives quieter team members a clear place to contribute

How to run the Good, Bad, Learned, Learning retrospective

  1. Create a board in QRetro using the Good, Bad, Learned, Learning template.
  2. Invite your team and give everyone a few minutes to add notes silently.
  3. Group similar cards and review each column together.
  4. Discuss the learning columns to confirm progress and set new goals.
  5. Vote on the most important topics to focus the conversation.
  6. Turn decisions into action items with clear owners.

Similar templates

Other formats teams pair with this one — open any of them as a board in one click.
Halloween Retrospective Template - Spooky Sprint!
A spooky, themed retrospective that walks the team through the full retro flow in costume. Halloween Treats set the scene, Ghost Stories gather the data, Trick or Treat generates insights and Pick a Door decides what to do, before the Spook of the Sprint closes things out. The playful theme makes a structured retrospective feel like a celebration.
Plus Delta Template
One of the simplest and fastest retrospective formats there is. The plus column collects everything going well that should be repeated, while the delta column gathers what the team wants to change or improve. Its minimal structure makes it perfect for quick check-ins and teams that want to retrospect often without overhead.
Energy Levels
A check-in format that focuses on the team's energy rather than its tasks. Participants place themselves between fully charged, medium power and low battery, then reflect on what drained or fueled the sprint's energy. Tracking it over time helps spot burnout early and keep the team's pace sustainable.
Weather Forecast Retrospective
A vivid metaphor that describes the sprint as a weather forecast. Stormy stands for the turbulent issues, rainy for the troublesome challenges, cloudy for the things that turned out rosy and sunny for what felt bright and successful. The imagery makes it easy to express how the sprint felt and to spot patterns across several retrospectives.
ESVP (Explorers, Shoppers, Vacationers, Prisoners)
An opening activity that gauges how people feel about being in the retrospective itself. Anonymously, everyone places themselves as an explorer eager for new ideas, a shopper open to one useful takeaway, a vacationer glad for a break or a prisoner who'd rather be elsewhere. The result helps the facilitator read the room and adjust the session to the team's real mood.
SOAR Analysis
A strengths-based alternative to SWOT that keeps the conversation positive and ambitious. The team examines its strengths and opportunities, articulates its aspirations and defines the results that will show those goals were met. By focusing on potential rather than problems, SOAR is well suited to strategy sessions and teams setting a bold direction.
Try Template