01
Collect feedback before the meeting
Share the board link with your team and ask everyone to add cards to What Went Well and What Didn't before the retro starts. This gives introverts equal voice and saves meeting time.
// Team Retrospective
Reflect, then act.
Capture what went well and what didn't, then convert insights into action items your team actually follows through on. Retros that drive real change, not just discussion.
What Went Well
3Shipped the billing revamp two days ahead of schedule
Process
Daily standups kept everyone aligned on blockers
Communication
New CI pipeline cut build times by 40%
Technical
What Didn't
2QA found 12 regressions in the final release candidate
Technical
Stakeholder feedback arrived too late to incorporate
Communication
Action Items
3Add integration test suite for payment flows
Technical
Schedule mid-sprint stakeholder check-in every Tuesday
Process
Create shared Slack channel for cross-team dependencies
Communication
In Progress
2Document on-call runbook for the new billing service
Technical
Trial async standup format for the next sprint
Process
Done
2Migrated team wiki to Notion - all docs consolidated
Process
Set up automated regression alerts in Datadog
Technical
02
Discuss and group themes
During the retro, use labels - Process, Communication, Technical - to categorize cards. Patterns emerge quickly when you can filter by label and see which category has the most issues.
03
Turn insights into Action Items
For each theme, create a concrete action item card with an assignee and a due date. Vague commitments die; assigned tasks with deadlines get done.
04
Track follow-through across sprints
Action items move to In Progress and then Done as teams execute. At the next retro, review what shipped and what stalled. Flux keeps the history so accountability compounds.
01 How is a retro board different from a regular kanban board?
+
A retro board starts with reflection columns (What Went Well, What Didn't) instead of workflow stages. The goal is to surface insights first, then convert them into trackable action items. The board bridges the gap between discussion and execution.
02 Can remote teams use this for async retrospectives?
+
Yes. Share the board link before the meeting and let team members add cards on their own schedule. Flux updates in real time, so by the time you meet, the board is already populated with feedback from every timezone.
03 How do I keep retro action items from being forgotten?
+
Assign each action item to a specific person and set a due date. The card stays visible on the board until it moves to Done. At the next retro, filter for stalled items and discuss blockers - the board holds you accountable.
// Start improving
Your retros, with teeth.
No credit card. Capture insights and track action items with real-time sync and full activity history.