Keep

What is working well that we should continue doing?

Our daily standups have been short and focused — let's keep them that way.
Pair programming on tricky tickets is really helping knowledge sharing.
The new definition of done has reduced bugs slipping through to QA.
Add

What is missing that we should introduce or start doing?

Let's add a short risk-check at the start of each sprint.
We should introduce a shared on-call runbook so handovers are smoother.
Add automated test coverage reports to our pull requests.
Less

What should we reduce because it's draining time or value?

Less context switching between projects in a single day.
We're spending too long in status meetings — can we cut them back?
Fewer last-minute scope changes mid-sprint, please.
More

What valuable thing deserves more time or focus?

More time for code reviews so we catch issues earlier.
I'd like more frequent feedback from our customers.
More cross-team collaboration on shared dependencies.

What is the KALM Retrospective?

The KALM Retrospective gives teams a simple, balanced way to reflect on their practices through four lenses: Keep, Add, Less, and More. Rather than framing everything as good or bad, KALM invites people to think about behaviors and processes along a spectrum — what's working well and should continue, what's missing and should be introduced, what's draining energy and should be reduced, and what's valuable and deserves more attention. This nuanced approach surfaces insights that simple "what went well / what didn't" formats often miss. KALM works by gathering team feedback across these four categories, then grouping, discussing, and voting on the ideas that matter most. The strength of this format lies in the "Less" and "More" columns, which acknowledge that many team practices aren't entirely good or bad — they just need to be dialed up or down. This makes it especially powerful for mature teams who have already addressed the obvious wins and blockers and want to fine-tune their ways of working with greater precision. Popularized within the agile and Scrum communities as a refreshing alternative to the classic Start/Stop/Continue retrospective, KALM helps teams generate actionable, calibrated improvements. By framing reflection around continuation and intensity rather than absolute judgments, teams build a culture of continuous improvement that feels constructive rather than critical — making it an excellent choice for recurring sprint retrospectives.

KALM retrospective format

Keep

What is working well that we should continue doing?

The Keep column captures the practices, behaviors, and processes that are serving the team well and should be preserved. Encourage participants to be specific about what makes these things valuable, so the team understands exactly what's worth protecting. This is a great place to start because it sets a positive, affirming tone before moving into areas for change.

Add

What is missing that we should introduce or start doing?

The Add column is for new ideas, practices, or tools the team isn't doing yet but believes would help. Prompt people to think about gaps in their workflow, recurring pain points, or things they've seen work elsewhere. Capture these as concrete proposals so the team can decide what's worth experimenting with.

Less

What should we reduce because it's draining time or value?

The Less column surfaces things the team is doing too much of — activities that drain energy, time, or focus without enough payoff. Unlike a hard 'Stop', this is about dialing things down rather than eliminating them entirely. Encourage honesty here while keeping the conversation constructive and free of blame.

More

What valuable thing deserves more time or focus?

The More column highlights things that are already working but deserve greater investment or attention. This helps the team amplify their strengths and double down on high-value activities. Ask participants why each item deserves more focus so the team can prioritise the highest-impact opportunities.

When to use this retrospective

  • When your team has outgrown basic Start/Stop/Continue formats and wants a more nuanced way to calibrate their practices.
  • For recurring sprint retrospectives where the obvious wins and blockers have already been addressed and you want to fine-tune how the team works.
  • When you want to balance positive reflection with constructive change without framing things as simply good or bad.
  • For mature agile teams looking to drive continuous improvement by adjusting the intensity of existing practices.

Suggested icebreaker questions

  • If your week were a thermostat, would it have been set to too hot, too cold, or just right?
  • What's one habit you'd like to keep doing and one you'd happily do less of in everyday life?

Ideas and tips for your retrospective meeting

  • Start with the Keep column to set a positive, affirming tone before moving into areas that need change.
  • Encourage specificity — vague items like 'more communication' are hard to action, so push for concrete examples.
  • Use the Less and More columns to capture nuance; not everything is binary, and many practices just need dialing up or down.
  • Give everyone quiet time to add their own ideas before discussion to reduce groupthink and ensure quieter voices are heard.
  • Group similar items, then dot-vote to focus discussion on the highest-impact themes rather than trying to cover everything.
  • Close the session by turning the top voted items into clear, owned action items with due dates so insights lead to change.

Frequently asked questions

What does KALM stand for?
KALM stands for Keep, Add, Less, and More — the four reflection categories teams use to evaluate and calibrate their practices.
How is KALM different from Start, Stop, Continue?
KALM adds nuance by including 'Less' and 'More' instead of just 'Start' and 'Stop', recognising that many practices don't need to be eliminated entirely — they just need to be dialed up or down.
How long does a KALM Retrospective take?
A typical KALM Retrospective runs 45 to 60 minutes, including time for brainstorming, grouping, voting, and agreeing on action items.
When should I use the KALM Retrospective?
It's ideal for mature agile teams that have moved past basic formats and want to fine-tune their ways of working with more precision.
How many people can take part in a KALM Retrospective?
KALM works well for teams of around 3 to 10 people; for larger groups, consider splitting into smaller breakout groups and merging the themes afterward.

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