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 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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitydifferent
LowMediumLowLow
Timedifferent
30-60 min1-3 h15-45 min30-60 min
Participantsdifferent
3-121-81-33-10
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsArgument Map, Evidence Gaps, Decision RationaleADR File, Decision Log, RationaleEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveImprovementTeamReflection
SensemakingDecisionRationale
ArchitectureRationaleDocumentationGovernance
RetrospectiveTeamReflection
Add more methods