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 Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
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 of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
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
Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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.IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.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
MediumLowMediumLow
Timedifferent
1-2 h30-60 min1-3 h45–75 min
Participantsdifferent
1-83-122-8Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Concept Map, Relationship Labels, Knowledge GapsStart Stop Continue Board, Improvement ActionsIssue Map, Positions, Argument Notes4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
KnowledgeConceptsMappingSensemaking
RetrospectiveImprovementTeamReflection
RationaleKnowledgeDecision
RetrospectiveLearningReflectionTeam
Add more methods