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 Views and Beyond | ![]() Architecture Architecture Decision Record | ![]() Agile Start Stop Continue | ![]() Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Tage | 15-45 min | 30-60 min | 45–75 min |
Participantsdifferent | 1-4 | 1-3 | 3-12 | Team members involved |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |



