Workspace
Retrospective — The Good, the Bad & the Ugly
The Retrospective is a facilitator's board for running a Good / Bad / Ugly retrospective. It works in any phase — reach for it after an experiment wraps, when a sprint plan finishes, or whenever the team wants to reflect. Open it from the workbench or from Next or Not?. A Loop badge in the header shows which loop the sitting — and every learning you register in it — belongs to.
It's designed to steer the conversation. You ask a question, the team talks, and you capture the takeaway — which is saved as a Retrospective learning in the Learnings Matrix, a kind all its own alongside Metrics and Risks.
The three facets
Each takeaway reads as a sentence — the tag · the question · what to do:
| The question | What it means | Colour | |
|---|---|---|---|
| 🟢 The Good | What went well? | Continue doing this | green |
| 🔴 The Bad | What went less well? | Stop doing this | red |
| 🟡 The Ugly | What could have gone better? | Improve doing this | amber |
How a sitting works
- As the team discusses each facet, type the takeaway into that column.
- Register a single note on its own, or Register all notes to save every filled column at once — whatever fits the flow of the conversation.
- Everything you register in one sitting is tied together as a group, so the responses stay related and can be grouped and ordered (Good → Bad → Ugly) in the Learnings Matrix.
- Start a new sitting to begin a fresh, separately-grouped retrospective.
You can register one response at a time as the conversation moves, or capture several and register them together — both produce the same grouped result.
Good to know
- This is the only way to create a Retrospective learning. The Learnings Matrix's manual Register form only creates Metrics and Risks; retrospective takeaways always come from here, so they're always well-formed and grouped.
- Retrospective learnings don't carry the metric/risk lifecycle (no Escalate/Mitigate) — they're reflections, not items to track to mitigation.
- The grouping tie is fixed once a response is registered, which keeps a sitting's responses reliably together.