2 tips for the DAKI retrospective incl. examples
You are an Agile Coach or Scrum Master looking for the “DAKI drop add keep improve retrospective”? Great, then you’ve come to the right place - the DAKI retrospective is one of my personal favorites (I’ll get to that later). But let me briefly explain it👆🏽
DAKI (Drop Add Keep Improve)
The 4 questions to ask at a DAKI retrospective:
First things first: DAKI is a simple acronym for “drop add keep improve” - who would have thought? 😂 All kidding aside. The DAKI retro is one of the more unspectacular retrospectives with its 4 fairly simple questions (but you’ll see, these questions pack a punch).
This is what the retrospective usually looks like on a digital whiteboard or on paper:

<figure> <figcaption><em>Whiteboard Vorlage - DAKI (Drop Add Keep Improve) Retrospektive</em></figcaption> </figure>
As you can see, even the design is kept rather simple. But as we all know, the devil is in the details (or should I say the strength?)👀
Here are some quick examples for all four questions in advance: “Drop? - Add? - Keep? - Improve?”
Drop: [Optional: Looking at the last sprint / weeks] What should we leave out?
✅Example: E.g., You were not satisfied with this new tool that is supposed to help you prioritize the product backlog. Let’s stop using it.
Add: What should we start with?
✅ Example: You have the feeling that not everyone in your team dares to speak up, there is a lack of so-called psychological safety . So you could start by performing an agile team health check in 3 steps in your team. 👉🏽 More information on: psychological safety ” Team health check in 3 steps %E2%80%9C
Keep: What should we do as before?
✅Example: You changed your daily, asking only one question. This produced better results, so you should keep it.
Improve: What should we do more of?
✅ Example: It’s good to look at agile metrics, such as your team’s velocity, from time to time - this hasn’t happened much lately! We should get better at keeping an eye on our metrics.
👉🏽More information on: agile metrics %E2%80%9C
By the way, you can also find this retrospective in our Echometer tool and conduct it online with your team (without registration)🎉
DAKI Retro: How the retro works
-
Random Icebreaker (2-5 minutes)
Echometer provides you with a generator for random check-in questions.
-
Review of open actions (2-5 minutes)
Before starting with new topics, you should talk about what has become of the measures from past retrospectives to check their effectiveness. Echometer automatically lists all open action items from past retros.
-
Discuss retro topics
Use the following open questions to collect your most important findings. First, everyone does it themselves, covered. Echometer allows you to reveal each column of the retro board individually in order to then present and group the feedback.
- Drop: What should we drop?
- Add: What should we add?
- Keep: What should we keep?
- Improve: What should we improve?
-
Catch-all question (Recommended)
So that other topics also have a place:
- What else would you like to talk about in the retro?
-
Prioritization / Voting (5 minutes)
On the retro board in Echometer, you can easily prioritize the feedback with voting. The voting is of course anonymous.
-
Define actions (10-20 minutes)
You can create a linked action via the plus symbol on a feedback. Not sure which measure would be the right one? Then open a whiteboard on the topic via the plus symbol instead to brainstorm root causes and possible measures.
-
Checkout / Closing (5 minutes)
Echometer enables you to collect anonymous feedback from the team on how helpful the retro was. This creates the ROTI score ("Return On Time Invested"), which you can track over time.
DAKI Retro
**
**Daki Retrospective vs. KALM Retrospective🔍
You may have noticed that at first glance there is no big difference between the DAKI model and the KALM retrospective “keep add less more”.
But buckle up tight, because here’s why I’d choose the DAKI retrospective over the KALM retrospective any day.
Improve vs. More✨
At first glance, you might not see the difference here, but as I said before, the devil is in the details.
In my opinion, constant improvement is one of the secrets to personally or as a team “becoming the best version of yourself”. But improvement involves so much more than “doing more of something.”
For example, you can improve in things that are important but not yet as good as you would like them to be. And doing “more” of something is just a tiny fraction of what “improve” means to me.
And even if the word doesn’t seem that different at first glance - the unconscious processes that take place in you are significantly different. Therefore, “improve” takes home the victory for me here🏆
Less vs. Drop��
Now we can take a closer look at “Less vs. Drop”. When was the last time you did less of something and why? For me, it was reducing the time I spent in meetings.
Because meetings massively deteriorated my productivity. Nevertheless, there was a reason why I attended these meetings in the first place: “communication” or “exchange of information”.
In this case, I wanted to spend less time in meetings, but maintain the flow of information within the team. “Less” meetings were not the right way for me - I had to improve the way information was exchanged with my colleagues (improve according to the DAKI method)🗣
For me, “less” of something is always a sign that I need to improve in that area.
My credo: Either I improve in something (in this case, by exchanging the same amount of information in less time) or I leave it completely. And hey, that’s exactly what it’s all about - Less vs. Omission?💡
Conclusion - DAKI Retrospective**⚡**
I don’t know about you, but for me, the DAKI (Drop Add Keep Improve) retrospective is the clear winner and one of my favorite retrospective formats to reflect and become a better team week after week.
If you like the Daki retrospective, you’ll probably like this too: 54 retrospectives for beginners and professionals.
Do you want to start your first DAKI retrospective right away? Then try our Echometer tool for continuous improvement of agile teams:
DAKI Retro: How the retro works
-
Random Icebreaker (2-5 minutes)
Echometer provides you with a generator for random check-in questions.
-
Review of open actions (2-5 minutes)
Before starting with new topics, you should talk about what has become of the measures from past retrospectives to check their effectiveness. Echometer automatically lists all open action items from past retros.
-
Discuss retro topics
Use the following open questions to collect your most important findings. First, everyone does it themselves, covered. Echometer allows you to reveal each column of the retro board individually in order to then present and group the feedback.
- Drop: What should we drop?
- Add: What should we add?
- Keep: What should we keep?
- Improve: What should we improve?
-
Catch-all question (Recommended)
So that other topics also have a place:
- What else would you like to talk about in the retro?
-
Prioritization / Voting (5 minutes)
On the retro board in Echometer, you can easily prioritize the feedback with voting. The voting is of course anonymous.
-
Define actions (10-20 minutes)
You can create a linked action via the plus symbol on a feedback. Not sure which measure would be the right one? Then open a whiteboard on the topic via the plus symbol instead to brainstorm root causes and possible measures.
-
Checkout / Closing (5 minutes)
Echometer enables you to collect anonymous feedback from the team on how helpful the retro was. This creates the ROTI score ("Return On Time Invested"), which you can track over time.
DAKI Retro