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 | ![]() Operations A3 Problem Solving | ![]() Architecture Views and Beyond | ![]() Operations Gemba Walk |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 45-90 min | 1-3 Tage | 30-120 min |
Participantsdifferent | 1-3 | 2-5 | 1-4 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | A3 Report, Action Plan, Root Cause Analysis | Architecture Views, Cross-view Notes, Rationale | Observation Notes, Improvement Ideas |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | LeanProblem solvingCoachingOperations | DocumentationStakeholdersArchitecture | LeanObservationProcessOperations |



