Keep / Problem / Try Retrospective Template for Agile Teams

Keep / Problem / Try focuses the team on retaining what works, naming pain, and proposing experiments. It is a reliable default for mid-length retros when SSC feels too shallow and Starfish feels too wide. On a shared online board everyone adds cards in parallel, groups similar notes, and votes without waiting for a round-robin. RetroEP is purpose-built for this flow: one open board, five anonymity modes, dot voting, threaded comments, emoji reactions, an anonymous sprint survey, archive with 12-month retention, and CSV / Markdown / PDF export. The room header shows a live HH:MM:SS countdown so the timebox stays honest.

Pick Keep / Problem / Try when you want a compact board that always ends with experiments. Rotate templates across sprints so the team does not stagnate on a single lens. If psychological safety is low, start with anonymity mode F or similar on RetroEP, then reveal authors later. If the room is large, lower the vote budget and keep action items to three or fewer. Hybrid teams benefit from a single link instead of chatting screenshots of sticky notes.

Typical columns: Keep, Problem, Try.

• Write one idea per card — short and specific beats vague essays.
• Group duplicates before voting so tallies reflect themes, not wording variants.
• Discuss only the highest voted themes; park the rest for a future board.
• Convert winners into SMART actions with an owner and due date on the same board.

Facilitators should model good card hygiene in the first two minutes. Remind the team that RetroEP cards are session-focused: do not paste passwords, personal data, or confidential customer identifiers.

1. Create a room at retroep.com — type kpt or “Keep / Problem / Try” in the template picker.
2. Share the invite — teammates join with a display name; optional room password for private teams.
3. Silent writing — 5–10 minutes of parallel card creation while the HH:MM:SS timer runs.
4. Group and vote — cluster themes, then dot-vote with clear limits.
5. Discuss and decide — timebox talk per theme; capture actions immediately.
6. Survey and archive — optional anonymous sprint survey, then archive/export for the sprint record.

No sign-up is required. Rooms work through many corporate firewalls via lightweight sync, and the UI is available in 12 languages with a mobile-responsive layout.

• Timebox strictly — visible countdown beats verbal “five more minutes”.
• Rotate the room manager so facilitation skill spreads across the team.
• Limit actions to what will actually fit next sprint.
• Use celebrations lightly at the end to close on appreciation, not only problems.
• Compare with related guides: retrospective templates and sprint retrospective.

Healthy retros emphasize systems and collaboration, never public blame. If a theme is sensitive, keep authors hidden until the group agrees to reveal names.

Open RetroEP, enter your name, choose Keep / Problem / Try (or the closest built-in template), and click Create room. Share the link — your team can run a full Keep / Problem / Try retrospective in the next sprint without accounts, installs, or credit cards.