Keep

What should we keep doing?

Our daily standups have been really effective at keeping everyone aligned
The technical documentation process we implemented last sprint is working great
I appreciate how we're handling code reviews with the two-person sign-off
Add

What should we start doing?

We should introduce pair programming sessions for complex features
Could we add a monthly tech debt cleanup day?
Let's create a shared knowledge base for common issues
Less

What should we do less of?

We should reduce the number of concurrent projects per person
Less time spent in unnecessary meetings would help productivity
Could we decrease the amount of context switching between tasks?
More

What should we do more of?

We should spend more time on code review feedback
More regular updates to our documentation would be helpful
I'd like to see more pair programming sessions

What is the KALM Retrospective?

The KALM retrospective is a structured approach that helps teams reflect on their work practices through four key dimensions: Keep, Add, Less, and More. This format encourages teams to maintain effective practices while identifying areas for improvement and optimization. Unlike traditional start-stop-continue formats, KALM provides more nuanced options for change by separating increase and decrease decisions from binary choices. This allows teams to fine-tune their processes rather than making dramatic changes. This retrospective format is particularly effective for teams seeking gradual, sustainable improvements. By focusing on what to keep and adjust, rather than what to completely eliminate, KALM promotes a more positive and constructive dialogue about team practices.

KALM Retrospective Format

Keep

What should we keep doing?

Focus on identifying successful practices that contribute to the team's effectiveness. Encourage participants to provide specific examples of what's working well and why these elements should be preserved.

Add

What should we start doing?

Encourage innovative ideas and new approaches that could benefit the team. Focus on practical suggestions that can be implemented within the next iteration.

Less

What should we do less of?

Guide the discussion toward constructive criticism of processes or behaviors that may be hindering productivity. Focus on specific actions rather than personal criticism.

More

What should we do more of?

Focus on existing positive practices that could be amplified or expanded. Help the team identify opportunities to build upon current successes.

When to use this retrospective

  • When you want to make incremental improvements rather than dramatic changes
  • During periods of stable team performance where fine-tuning is more appropriate than major overhauls
  • When the team needs a balanced approach to maintaining good practices while identifying areas for adjustment

Suggested icebreaker questions

  • What's one small change you made recently that had a positive impact?
  • If you could instantly master one new skill that would help the team, what would it be?

Ideas and tips for your retrospective meeting

  • Start by reviewing the previous retrospective's action items to maintain continuity
  • Encourage participants to provide specific examples rather than general statements
  • Use dot voting to prioritize items if you receive many suggestions
  • Keep the focus on actionable improvements rather than complaints
  • Ensure each category gets equal attention during the discussion
  • End the session by creating concrete action items for the highest-priority items

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