KALM Retrospective

Choose what to keep, add, do less and do more.

Try this retrospective live

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 asks your team to sort its work practices into four categories: Keep, Add, Less and More. You hold on to what's working, add something new where there's a gap, and adjust the rest. Start Stop Continue gives you three choices: begin something, end it or leave it alone. KALM swaps the hard stop for 'less' and adds 'more', so a practice can be turned up or down without being dropped. Your team gets to fine-tune how it works instead of making dramatic changes. The format suits teams that want gradual, steady improvement. Most of the conversation is about what to keep and adjust, and little is about what to cut entirely, so the tone stays positive and the discussion stays practical.

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?

Ask for new ideas and approaches that could help the team. Keep the suggestions practical, so you can put them in place 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 small, steady improvements instead of a big change.
  • When the team is performing well and needs fine-tuning, not an overhaul.
  • When you want to protect good practices while adjusting the ones that have drifted.

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?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Start by reviewing the actions from your last retrospective.
  • Ask for specific examples. 'Code reviews take three days' is easier to act on than 'reviews are slow'.
  • If ideas pile up, use dot voting to pick the ones worth discussing.
  • Steer complaints toward a suggested change before they go on the board.
  • Give each of the four categories its share of discussion time.
  • Finish by turning the top-voted items into actions with owners.

Frequently asked questions

What does KALM stand for?
KALM stands for Keep, Add, Less and More, the four categories your team uses to sort its practices.
How is KALM different from Start, Stop, Continue?
KALM uses 'Less' and 'More' where Start Stop Continue has a hard 'Stop'. Many practices don't need to go entirely. They need turning up or down, and KALM gives you a place for that.
How long does a KALM Retrospective take?
Most take 45–60 minutes, including time to brainstorm, group, vote and agree on actions.
When should I use the KALM Retrospective?
Use it when your team has the basics in place and wants to fine-tune how it works. It's a good next step if you've outgrown simpler formats.
How many people can take part in a KALM Retrospective?
It works best with a single team. For a larger group, split into breakout groups and merge the themes afterward.

Related templates

Four Ls Retrospective

Reflect on what your team Liked, Learned, Lacked and Longed for

What? So What? Now What? Retrospective

Go from what happened to what you'll do next.

Agile Retrospective

Four questions to review your last sprint and plan changes.

Start Stop Retrospective

Two questions: what to start, and what to stop

Ready to run this retrospective?Try this retrospective live