Drop

What practices should we stop or discontinue?

We should drop the weekly status meeting since we now have a better way to track progress.
Let's stop using that outdated project management tool - it's more trouble than it's worth.
I think we can drop the requirement for two approvals on minor code changes. It's slowing us down unnecessarily.
Add

What new practices should we adopt?

We should add a quick daily standup to keep everyone in sync.
Let's start doing weekly knowledge sharing sessions to learn from each other.
I think we need to add some automated testing to catch regressions earlier.
Keep

What's working well that we should continue?

The pair programming sessions have really helped improve code quality - let's keep doing those.
Our regular retrospectives are so valuable for continuous improvement. We should definitely keep having them.
The flexible work hours policy has been great for work-life balance. I hope we keep that.
Improve

What could we do better?

Our code review process could be improved by having clearer guidelines and better tooling.
I think we need to improve how we prioritize and scope new features to avoid constant firefighting.
The onboarding process for new hires could be improved with better documentation and mentoring.

What is the Drop Add Keep Improve retrospective?

The Drop Add Keep Improve (DAKI) retrospective is a simple yet powerful way to review processes, projects, or team dynamics. It prompts participants to reflect on what should be dropped (stopped), added (started), kept (continued), and improved (enhanced). This format provides a structured approach to gather feedback and drive positive change. By focusing on these four key areas, teams can quickly identify strengths, weaknesses, and opportunities for growth. The DAKI retrospective originated in the Lean manufacturing principles but has been widely adopted in various industries, including software development, due to its effectiveness in continuous improvement.

Drop Add Keep Improve retrospective format

Drop

What practices should we stop or discontinue?

Encourage the team to be open about processes, tools, or behaviors that are no longer serving them well.

Add

What new practices should we adopt?

Encourage creativity and open-mindedness when suggesting new processes or ways of working.

Keep

What's working well that we should continue?

Reinforce the positive by highlighting processes and practices that are benefiting the team.

Improve

What could we do better?

Encourage constructive criticism and focus on actionable improvements rather than complaints.

When to use this retrospective

  • At the end of a project, sprint, or major milestone to review what went well and what could be improved.
  • When a team is struggling with specific processes, tools, or dynamics and needs to identify areas for change.
  • As a regular check-in (e.g., monthly or quarterly) to continuously improve and adapt team practices.

Suggested icebreaker questions

  • If our team was a vehicle, what kind would it be and why?
  • What's one thing you've learned or improved on since our last retrospective?

Ideas and tips for your retrospective meeting

  • Encourage open and honest feedback by creating a safe, blame-free environment.
  • Use anonymous or private voting techniques if the team is hesitant to voice concerns openly.
  • Prioritize the most impactful items in each category and create actionable next steps.
  • Follow up on agreed improvements in subsequent retrospectives to ensure continuous progress.
  • Consider rotating the facilitator role to get fresh perspectives and ensure shared responsibility.
  • Set a positive tone by starting and ending with items in the 'Keep' category to reinforce what's going well.

New to retrospectives? Read our guide on how to run a retrospective →