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 Risk Storming |  Facilitation Consensus Workshop |  Facilitation Problem Framing Workshop |
|---|---|---|---|---|
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. | 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. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-60 min je Interview | 60-90 min | 1-3 h | 60-120 min |
Participantsdifferent | 5-12 Interviews | 4-12 | 5-30 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Annotated Diagram, Prioritized Risk List, Action Backlog | Consensus Clusters, Theme Titles, Priority Areas | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions |
Tagsno overlap | DiscoveryInterviewsValidation | RiskArchitectureWorkshopValidation | FacilitationConsensusWorkshopAlignment | FacilitationAlignmentDiscovery |