--- title: "Keep Problem Try (KPT) Retrospective" description: "Team members sort recent project reflections into three categories: successful practices to Keep, obstacles identified as Problems, and concrete experiments to Try. The group clusters similar points, discusses key issues, and agrees on concrete action items for their next work cycle." last_updated: "2026-09-07" canonical: "https://unitedwetransform.com/exercises/keep-problem-try-kpt-activity/" --- # Keep Problem Try (KPT) Retrospective Team members sort recent project reflections into three categories: successful practices to Keep, obstacles identified as Problems, and concrete experiments to Try. The group clusters similar points, discusses key issues, and agrees on concrete action items for their next work cycle. **Time:** 45 minutes. UWT 45-minute standard for a full 4 to 24 person retrospective; source documents note rapid template use without fixed time bounds. **People:** 4 to 24. Individual silent writing followed by full-group clustering or small-group breakouts (4 to 6 people) for discussion if group size exceeds 8. ## Choose this exercise **Purpose:** Identify stable team practices, clarify current operational blockers, and agree on practical experiments for the upcoming work period. **Use it when:** Use at the end of a sprint, milestone, or short delivery cycle when a team needs a straightforward, actionable reflection without complex metaphors. **Skip it when:** Skip when a project requires broad strategic replanning, deep emotional conflict resolution, or when leadership cannot support process adjustments. ## Materials and tools - Wall space or whiteboard marked into three columns: Keep, Problem, Try - Sticky notes (at least 15 per person) - Dark writing pens (1 per person) - Timer - Dot-voting stickers or markers (optional, 3 dots per person) ## Before participants arrive 1. Draw or project three distinct columns labeled 'Keep', 'Problem', and 'Try' on a shared board. 2. Ensure each seat has a writing pad or sticky notes and a pen. 3. Confirm the exact project or time window under review. ## Say this to open Today we will run a Keep, Problem, Try retrospective. In 'Keep', write down practices and habits that helped us and should continue. In 'Problem', write concrete difficulties or bottlenecks we faced. In 'Try', write actionable experiments or changes we can test in our next cycle. You may write as many notes as you need, or choose to submit none. ## How to run it ### 1. Introduce prompts and review period (5 minutes) State the specific sprint or time frame being reviewed. Point out the three categories: Keep (working habits to preserve), Problem (specific impediments experienced), and Try (experiments or actionable steps for next cycle). Explain that personal medical, private, or personnel issues should remain optional and private. ### 2. Silent reflection and writing (8 minutes) Participants write individually on sticky notes. One idea per note. Remind everyone to keep notes concise. Participants post their notes into the appropriate column as they finish, or place them face down if they prefer facilitator posting. ### 3. Cluster and review items (10 minutes) The facilitator or group clusters duplicates and related notes within each column. Read the themes aloud. If group exceeds 8 people, give each person 3 votes to highlight which Problem or Try clusters require immediate discussion. ### 4. Discuss and define experiments (15 minutes) Work through the top-priority clusters. For each key Problem, examine paired Try proposals or brainstorm concrete tests. Ensure each selected Try has a clear scope, owner, and review date. Cap discussion at 3 minutes per cluster to cover the top items. ### 5. Confirm action items and close (7 minutes) Read back the agreed Try experiments and assign designated point people for follow-up. Collect any remaining cards for project documentation. ## Debrief questions - Which existing practice in Keep gave us the most operational stability this cycle? - Does our selected Try experiment directly address the root of our biggest Problem? - How will we know by our next review if the Try experiment worked? **Finished output:** A documented list of ongoing practices to maintain and 1 to 3 assigned 'Try' experiments with defined owners for the next cycle. ## Remote Use a shared online whiteboard with three columns (Keep, Problem, Try). Run step 2 with cameras optional and silent writing. Have participants move cards into groups. Use digital voting dots or reaction stamps during step 3. Document action owners directly into the digital board. ## Hybrid In-person participants write on physical sticky notes, while a co-facilitator transcribes them onto the shared digital board where remote participants add their notes in parallel. Cast all votes digitally on personal devices so remote and in-room votes carry identical weight. ## Access and participation choices - Participants may type, speak, write on paper, or submit ideas through a facilitator proxy. - Contributing notes or sharing aloud is entirely optional; participants may observe or focus solely on reviewing others' proposals without disclosing personal difficulties. ## If the session gets stuck **Participants list vague complaints without actionable details under Problem.** Ask the author or group: 'What specific event or task slowed us down, and what was the observable impact?' **Try proposals turn into massive, unmanageable project overhauls.** Prompt the group to shrink the proposal to a 1-week or 2-week reversible experiment before committing to full changes. ## Terms used here - KPT: Keep, Problem, Try: a three-part retrospective structure focusing on continuity, obstacles, and new experiments. - Retrospective: A structured meeting where a team inspects their recent work cycle to identify workflow improvements. ## Sources and adaptation Observed in Parabol and EasyRetro retrospective template libraries. Sources attribute the technique either to Alistair Cockburn or to Toyota production practices. Retained the three core prompts (Keep, Problem, Try) and the practical focus on continuous improvement from the Parabol and EasyRetro sources. UWT added explicit step-by-step timings, cluster mechanics, hybrid parity guidelines, and privacy-preserving access rules to make it fully runnable across 4 to 24 participants. [Parabol](https://www.parabol.co/templates/sprint-retrospectives/keep-problem-try/) [Parabol](https://www.parabol.co/templates/sprint-retrospectives/keep-problem-try) [EasyRetro](https://easyretro.io/templates/keep-problem-try-kpt/) Current run sheet: https://unitedwetransform.com/exercises/keep-problem-try-kpt-activity/