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
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 Starfish Retrospective
Agile
Starfish 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.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.When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h30-60 min45–75 min45-90 min
Participantsdifferent
2-83-12Team members involved4-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Issue Map, Positions, Argument NotesStart Stop Continue Board, Improvement Actions4Ls Board, Learning Themes, Improvement ActionsStarfish Board, Practice Changes, Experiments
Tagsno overlap
RationaleKnowledgeDecision
RetrospectiveImprovementTeamReflection
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementExperimentsTeam
Add more methods