Skip to content
ToolDesk

KPT Retrospective

Organize retrospectives with Keep / Problem / Try. Saved in your browser; export and import as JSON. No upload.

Think & Plan

No upload, no data sent β€” everything runs in your browser.

About this tool

KPT is a framework for reflecting on an activity from three angles: Keep (what to continue), Problem (what went wrong), and Try (what to attempt next). At the end of a project or sprint, or when reviewing daily work, it surfaces what went well and what needs work and turns that into concrete improvement actions. Its simple three-way split makes it quick to run for teams or individuals.

To use it, write the good things you want to continue under Keep, the things that troubled you or did not go well under Problem, and then, informed by those, list concrete improvements to attempt under Try. Each item can be added as a card, and your changes are saved automatically to your browser localStorage. Nothing you enter is sent to a server.

The knack of KPT is to write Problems as issues with the system rather than blame on people, and to turn each Try into a concrete action you can try right away next time. By making the next step clear instead of ending on vague regret, the retrospective becomes a cycle of continuous improvement. It also helps to check whether a previous Try has grown into a current Keep or Problem.

The improvement actions from a retrospective are easier to act on if you prioritize them with an Eisenhower matrix or manage them as tasks on a Kanban board. You can export a KPT as JSON to save and reload it, keeping a record across sessions.

How to use

  1. Add items into the three columns β€” Keep, Problem, and Try.
  2. Edit any item inline or delete it. Your board is saved automatically in your browser.
  3. Use Export JSON to save a file, and Import JSON to restore or move it to another device.

FAQ

What does KPT stand for?

It is the initials of Keep (what to continue), Problem (what went wrong), and Try (what to attempt next). It describes a flow of retaining what went well, surfacing issues, and connecting them to the next improvement.

Is what I enter sent anywhere?

No. The content is stored in your browser localStorage and is not sent to a server, so you can safely write down team details or personal reflections.

How do Keep and Try differ?

Keep is what you already do and want to continue; Try is an improvement you have not done yet but want to attempt next. Thinking of Keep as maintaining the status quo and Try as a new step makes them easier to separate.

Any tips for a good retrospective?

The trick is to write Problems as issues with the system rather than blame on individuals, and to turn each Try into a concrete action you can do right away next time. Not ending on vague regret is what leads to continuous improvement.

Can I save my KPT?

Yes, you can export it as JSON. The exported file can be loaded to resume editing and works for keeping a record across sessions or moving to another device.

Does the content remain after I close the page?

Yes. It is saved automatically, so reopening the same browser lets you continue. Note that it is not retained after clearing browser data or in a private window.