🔄 Retrospective Board
Capture a retro in three columns, what went well, what to improve, actions, and upvote the notes that matter most.
😀 What went well · 0
🤔 What to improve · 0
✅ Action items · 0
Add notes to each column and upvote the ones the team cares about. They sort to the top. Saved in this browser only.
How the retrospective board works
A retrospective is a regular look back at how work went, so a team can keep what's working and fix what isn't. This board gives you three columns, What went well, What to improve, and Action items, to fill with notes. Upvote the notes the group cares about most and they float to the top, focusing the discussion on what matters. Everything is saved in your browser and can be exported or printed to share. The three-column layout is the classic "Went well / To improve / Actions" format, but the same board fits related variants such as Start / Stop / Continue or Mad / Sad / Glad, just rename the columns in your head and use them the same way, gathering notes first and voting second.
The output that actually changes anything is the Action items column, a retro that surfaces problems but ends without owned, specific actions just becomes a complaints session that repeats next time. Keep the tone blameless (the goal is better systems, not culprits), timebox it, and carry the top action items forward. All stored on your device.
Frequently asked questions
What is a retrospective?
A recurring session, common in agile teams, to reflect on a period of work: what went well, what could be better, and what to change. The point is continuous improvement, done regularly rather than only after something goes wrong.
How does voting help?
Upvoting notes surfaces what the group collectively cares about, so a limited discussion focuses on the highest-impact items rather than whatever was mentioned last. Voted notes sort to the top automatically.
Why is the Action items column the important one?
Because insight without action changes nothing. A retro that ends without specific, owned action items tends to raise the same issues again next time. Capture concrete next steps and carry them forward.
Can the whole team use it together?
It's a local, single-device board, great for a facilitator sharing a screen. Everyone's input goes on one board; export the JSON to archive it. There's no live multi-user sync, by design (it stays private and account-free).
What formats can I run on this board?
Any three-bucket retro: Went well / To improve / Actions (the default), Start / Stop / Continue, Mad / Sad / Glad, or Liked / Learned / Lacked. They all separate observations from decisions, which is what the three columns and the vote-then-act flow support.
How long should a retrospective take?
For a two-week sprint, keep it to roughly 45-60 minutes: a few minutes gathering notes, a round of voting, focused discussion on the top-voted items, and time reserved to write concrete action items. Timeboxing each phase stops the session sprawling into an unfocused vent.
Is it saved and shareable?
Auto-saved in your browser, exportable as JSON, and printable to PDF. Nothing is uploaded.