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 Solution Interview | ![]() Architecture Architecture Decision Record | ![]() Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 30-60 min je Interview | 15-45 min | 60–90 min |
Participantsdifferent | 5-10 Interviews | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | ADR File, Decision Log, Rationale | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ValidationInterviewsPrototype | ArchitectureRationaleDocumentationGovernance | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






