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 |  Architecture C4 Model |  Agile Sailboat Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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. | 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 wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | 1-4 h | 45-90 min | 45–75 min |
Participantsdifferent | 1-3 | 1-5 | 4-12 | Team members involved |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Sailboat Board, Risks, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | RetrospectiveTeamImprovement | RetrospectiveLearningReflectionTeam |