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 for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h30-60 min30-60 min45–75 min
Participantsdifferent
3-123-103-12Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanEmotion Board, Themes, Action ItemsStart Stop Continue Board, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
KnowledgeMappingRisk
RetrospectiveTeamReflection
RetrospectiveImprovementTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods