DAKI Retrospective (Drop, Add, Keep, Improve)

Four dials instead of three — the only format that separates a brand-new experiment from tuning what already exists.

Use this template free

Free · No credit card · Guests join by link

The board

01

DROP

What should we get rid of entirely?

02

ADD

What should we introduce that we don't do yet?

03

KEEP

What's working and shouldn't change?

04

IMPROVE

What exists but needs tuning?

DAKI is Start-Stop-Continue's more precise cousin. Where Start-Stop-Continue crams two different kinds of change into one column — a brand-new experiment and a small tweak to something that already exists both land in "Start" — DAKI splits them into Add and Improve. The distinction matters more than it sounds: a new experiment needs a hypothesis and an owner; a tuning fix just needs someone to make the change.

The fourth column also changes what Drop means. In a three-column format, "stop" quietly absorbs both hard removals and things that just need to be dialled down. DAKI's Drop is reserved for full removals — the Improve column catches everything that's not broken enough to kill, just imprecise enough to fix.

When to use Drop · Add · Keep · Improve

  • Your Start-Stop-Continue retros keep piling unrelated ideas into "Start" — new experiments and small tweaks tangled together
  • The team is mature enough to distinguish "kill this" from "adjust this" and wants a format that respects the difference
  • You report retro outcomes to stakeholders and a four-way action taxonomy is easier to track than three
  • Coming off a Starfish retro and ready to also entertain hard removals, not just dial adjustments

How to run it in Retromik

  1. 1

    Split Add from Improve while writing

    Before the write phase, remind the team: Add is something you don't do at all today; Improve is something you already do but imperfectly. When in doubt, ask 'does this already exist in some form?' — if yes, it's Improve.

  2. 2

    Vote on what matters

    Each person places a limited set of voting tokens on the cards they think deserve discussion. Limited tokens force real prioritization.

  3. 3

    Discuss the top cards

    Walk through the highest-voted cards one by one. The facilitator steers the focus; anyone can comment on any card.

  4. 4

    Reveal and group themes

    Authors are revealed and the facilitator drags related cards into named themes, turning scattered notes into patterns.

  5. 5

    Commit to action items

    Convert the discussion into specific, owned action items with due dates — the part most retrospectives skip.

Frequently asked questions

What does DAKI stand for?

Drop, Add, Keep, Improve. It's a four-column retrospective format that extends Start-Stop-Continue by splitting 'Start' into two more precise categories: entirely new ideas (Add) and improvements to existing practices (Improve).

How is DAKI different from Start, Stop, Continue?

Start-Stop-Continue has three columns and blends new experiments with small process tweaks into a single 'Start' column. DAKI keeps them separate, which produces a cleaner action list — new initiatives need owners and hypotheses, while tuning fixes just need someone to make the change next sprint.

What's the difference between Keep and Improve?

Keep is working as-is and should be protected from well-meaning tinkering. Improve is directionally right but has friction — the mechanism works, the execution doesn't quite. If a card describes something that's actively good, it's Keep; if it describes something with a 'but,' it's Improve.

How long does a DAKI retro take?

Plan for 60-70 minutes with a team of 5-8 — one extra column means slightly more writing and discussion time than a three-column retro. Retromik is free to run it: create a board with the DAKI template and share the link; guests can join without an account.

Related templates

Run your next retro with Drop · Add · Keep · Improve

Create the board in under a minute, share the link, and your team joins anonymously — no accounts needed for participants.

Start free