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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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 Mad Sad Glad
Agile
Mad Sad Glad
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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 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
MediumLowLowLow
Timedifferent
1-3 h1-2 Tage30-60 min30-60 min
Participantsdifferent
1-81-43-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleArchitecture Document, Context View, Runtime View, Deployment ViewStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
SensemakingDecisionRationale
ArchitectureDocumentationCommunication
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods