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 Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
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 Argument Mapping
Decision Making
Argument Mapping
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
Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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
HighLowMediumLow
Timedifferent
0.5-3 Tage30-60 min1-3 h45–75 min
Participantsdifferent
5-153-121-8Team members involved
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Rich Picture, Root Definitions, Conceptual Models, Change AgendaStart Stop Continue Board, Improvement ActionsArgument Map, Evidence Gaps, Decision Rationale4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
Soft systemsComplexitySensemakingSystems thinking
RetrospectiveImprovementTeamReflection
SensemakingDecisionRationale
RetrospectiveLearningReflectionTeam
Add more methods