View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Concept Mapping | ![]() Agile 4Ls Retrospective | ![]() Knowledge Modeling IBIS |
|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-2 h | 45–75 min | 1-3 h |
Participantsdifferent | 1-8 | Team members involved | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | 4Ls Board, Learning Themes, Improvement Actions | Issue Map, Positions, Argument Notes |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | RetrospectiveLearningReflectionTeam | RationaleKnowledgeDecision |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






