View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Mad Sad Glad | ![]() Decision Making Argument Mapping | ![]() Architecture arc42 | ![]() Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 1-3 h | 1-2 Tage | 30-60 min |
Participantsdifferent | 3-10 | 1-8 | 1-4 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | Argument Map, Evidence Gaps, Decision Rationale | Architecture Document, Context View, Runtime View, Deployment View | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveTeamReflection | SensemakingDecisionRationale | ArchitectureDocumentationCommunication | RetrospectiveImprovementTeamReflection |



