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



