View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Problem Interview |  Architecture Views and Beyond |  Architecture Risk Storming |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-60 min je Interview | 1-3 Tage | 60-90 min | 15-45 min |
Participantsdifferent | 5-12 Interviews | 1-4 | 4-12 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Architecture Views, Cross-view Notes, Rationale | Annotated Diagram, Prioritized Risk List, Action Backlog | ADR File, Decision Log, Rationale |
Tagsno overlap | DiscoveryInterviewsValidation | DocumentationStakeholdersArchitecture | RiskArchitectureWorkshopValidation | ArchitectureRationaleDocumentationGovernance |