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 4Ls Retrospective |  Architecture C4 Model |  Agile Mad Sad Glad |
|---|---|---|---|---|
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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | 45–75 min | 1-4 h | 30-60 min |
Participantsdifferent | 1-3 | Team members involved | 1-5 | 3-10 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | 4Ls Board, Learning Themes, Improvement Actions | Context Diagram, Container Diagram, Component Diagram | Emotion Board, Themes, Action Items |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RetrospectiveLearningReflectionTeam | ArchitectureCommunicationVisualization | RetrospectiveTeamReflection |