Loading WorkLenz...
Run a structured sprint retrospective - async or live - no account needed. Guided 5-step process: Gather, Group, Vote, Discuss, Act.
From Insights to Sprint Tasks
Stop letting retro action items disappear. Turn insights into tracked tasks that get done - in your next sprint.
Gather โ Group โ Vote โ Discuss - keeps retros focused and productive
Each person gets 3 votes to prioritize the highest-impact improvements
Extract action items with owners and due dates from any sticky note
Hide notes during async collection, reveal when the team meets
Share the full board via URL for async team participation
Download as Markdown or CSV. Print-ready for physical boards.
Pro Tip
In Worklenz, retro action items become sprint tasks automatically - assign owners, set due dates, and track completion across sprints.
Our retro board uses the proven What Went Well / Wrong / Improve format with dot voting to keep retros focused on actionable outcomes, not just discussion.
Pro Tip
Limit to 1โ3 action items per retro. Too many actions means nothing gets done. Review them at the start of your next retro.
Free trial โข No credit card required โข Easy setup
Everything you need to know about running effective sprint retrospectives
The board follows a proven 5-step process: (1) Gather - team members add sticky notes to three columns: What went well, What went wrong, and What could improve. (2) Group - the facilitator reads notes aloud and groups similar items. (3) Vote - each person gets 3 votes to prioritize the most impactful themes. (4) Discuss - the team discusses the top-voted themes, focusing on root causes and solutions. (5) Act - define 1โ3 specific action items with owners and check-in dates.
Facilitator Mode blurs all notes on the board so team members can contribute asynchronously without being influenced by others' input. When the retro meeting starts, the facilitator clicks 'Reveal All' to show everything at once. This prevents groupthink and ensures independent thinking.
Click 'Start Dot Voting' to open the voting phase. Each team member gets 3 votes (โฒ button on each note). They can distribute votes across any notes - all on one or spread across several. Notes are automatically sorted by vote count so the team's top priorities rise to the top. This ensures the retro focuses on the changes that will have the highest impact.
Click the ๐ฏ button on any sticky note to create a linked action item, or add standalone items at the bottom of the Action Items section. Each action item has a description, owner, due date, and done checkbox. Action items linked to notes show their source column (๐/๐/๐ก) for traceability. We recommend limiting to 1โ3 actions per retro - too many means nothing gets done.
Click the 'Share' button to generate a URL with the full board state encoded in it. Send this link to your team members. When they open it, they can add notes, upvote, and create action items. If they already have local data, they'll be prompted to merge or keep their local board.
Yes. All data is stored only in your browser's localStorage. Nothing is sent to any server. The shareable URL encodes the board state in the URL itself - no server storage involved. Your retro data never leaves your device unless you explicitly share the link.
Yes. Export as Markdown for Confluence, Notion, or GitHub wikis. Export action items as CSV for spreadsheets or project tracking. You can also use your browser's print function to get a clean, formatted version of the full board - perfect for archiving or sharing with stakeholders.
At the start of each retro, review the action items from the previous one: Did we complete them? What changed as a result? This creates a feedback loop that makes each retro more effective. The 'Next Retro Reminder' section on the board gives your team a simple 3-step checklist to follow.