methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of a four-column Kanban board with limited ongoing work, a visible blocker and a review loop.
Engineering
Kanban
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitydifferent
MediumLowLow
Timedifferent
Ongoing30-60 min30-60 min
Participantsdifferent
2-123-123-10
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Kanban board, WIP policies, Flow metricsStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
FlowVisual managementDelivery
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration for Monte Carlo Forecasting.
Delivery
Monte Carlo Forecasting