What Went Well
What Didn't / Actions

A no-nonsense retrospective format: celebrate wins, name problems honestly, and commit to concrete next steps. No metaphors, no fluff.

Run a free retro

No account required. Anonymous cards. Password-protected rooms.

What is this format?

What Went Well / What Didn't / Actions is a retrospective format that keeps teams focused on outcomes rather than feelings. The three columns force a complete picture: what worked and should be reinforced, what failed and needs to change, and what concrete actions the team commits to.

The format is deliberately sequenced. During the writing phase, only “What Went Well” and “What Didn't” are open - keeping that input anonymous and unbiased. Actions are added collaboratively after the reveal, once the team has seen the full picture and voted on what matters most. This prevents teams from jumping to solutions before the problems are properly surfaced.

The three columns

🟢

What Went Well

Things that worked well this sprint. Naming them explicitly reinforces good habits and gives the team something to build on rather than take for granted.

🔴

What Didn't

Problems, friction, and failures from the sprint. Honest answers here matter most. The goal is diagnosis, not blame.

🟡

Actions

Concrete, committed next steps. Each action should be specific, owned by someone, and achievable in the next sprint.

Why teams use it

🎯

Outcome-focused

Every column points toward action. There is no room for vague themes - problems get named and actions get committed.

🔒

Safe for honest feedback

Cards are anonymous until the host reveals. Team members can be candid about what failed without social pressure.

Simple to facilitate

The format needs no facilitation experience. Write, vote, discuss the top items, assign actions - done in under an hour.

🌱

Works for any team

New or experienced, co-located or remote - this format works for any team that wants structured, actionable retrospectives.

When to use it

Common moments in the sprint cycle where this format works well.

Regular sprint retrospectives

The format is well-suited to two-week sprint cycles. It is fast enough to run every sprint without fatigue, and structured enough to produce real actions rather than vague themes.

Teams new to retrospectives

No metaphors, no warm-up exercises. Three columns, clear intent. It is the easiest format to explain to a team that has never run a retro before.

After a difficult sprint

When something went wrong - a missed deadline, a production incident, a conflict - this format gives everyone a safe way to name problems honestly before jumping to solutions.

When previous retros produced no actions

If past retrospectives ended with discussion but no follow-through, the explicit Actions column forces the team to commit to specific next steps before closing the session.

Remote and hybrid teams

Async card writing + anonymous reveal removes the awkwardness of speaking up on a video call. Everyone contributes equally regardless of time zone or personality.

How it works

1

Host creates a room with an optional password and shares the code.

2

Everyone joins - no account needed.

3

Team members add anonymous cards to "What Went Well" and "What Didn't". Actions are locked at this stage.

4

When writing time is up, the host reveals all cards.

5

Everyone upvotes the cards that matter most. Cards sort by votes.

6

Team discusses the top-voted items. The Actions column opens - everyone adds action items together.

7

Actions are committed, owned, and tracked into the next sprint.

Run your next retro in minutes

Create a room, share the code, and let the team add cards. No account, no setup needed.

Start a free retro session