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 |  Facilitation Stakeholder Salience Model |  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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 | Medium | Low |
Timedifferent | 30-60 min je Interview | 1-3 Tage | 60-90 min | 15-45 min |
Participantsdifferent | 5-12 Interviews | 1-4 | 3-6 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Architecture Views, Cross-view Notes, Rationale | Salience Diagram, Strategy per Class | ADR File, Decision Log, Rationale |
Tagsno overlap | DiscoveryInterviewsValidation | DocumentationStakeholdersArchitecture | StakeholdersFacilitationAlignmentGovernance | ArchitectureRationaleDocumentationGovernance |