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 Risk Storming |  Architecture Views and Beyond |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 15-45 min | 60-90 min | 1-3 Tage | 45-60 min |
Participantsdifferent | 1-3 | 4-12 | 1-4 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Annotated Diagram, Prioritized Risk List, Action Backlog | Architecture Views, Cross-view Notes, Rationale | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskArchitectureWorkshopValidation | DocumentationStakeholdersArchitecture | AssumptionsRiskExperimentsValidation |