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 Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation 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 for Starfish Retrospective
Agile
Starfish Retrospective
Purposedifferent
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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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 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 h45-90 min30-60 min45-90 min
Participantsdifferent
1-83-123-124-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleExpectation Map, Alignment Notes, AgreementsStart Stop Continue Board, Improvement ActionsStarfish Board, Practice Changes, Experiments
Tagsno overlap
SensemakingDecisionRationale
AlignmentStakeholdersTeam
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementExperimentsTeam
Add more methods