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 |  Product Discovery Solution Interview |  Innovation Design Thinking |
|---|---|---|---|
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. | When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 15-45 min | 30-60 min je Interview | 1 Tag bis mehrere Wochen |
Participantsdifferent | 1-3 | 5-10 Interviews | 4-10 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Solution Feedback, Objection List, Validation Notes | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ValidationInterviewsPrototype | InnovationPrototypeResearch |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
