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 an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
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 Feynman Technique.
Knowledge Modeling
Feynman Technique
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
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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work.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 min20-60 min45–75 min
Participantsdifferent
2-83-121Team members involved
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Issue Map, Positions, Argument NotesStart Stop Continue Board, Improvement ActionsPlain-language Explanation, Knowledge Gaps, Study Notes4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
RationaleKnowledgeDecision
RetrospectiveImprovementTeamReflection
LearningKnowledgeUnderstanding
RetrospectiveLearningReflectionTeam
Add more methods