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 Concierge MVP |  Architecture Risk Storming |  Facilitation Problem Framing Workshop |
|---|---|---|---|
Purposedifferent | When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | 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 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 | Low |
Timedifferent | 1-4 Wochen | 60-90 min | 60-120 min |
Participantsdifferent | 3-10 Kunden | 4-12 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Concierge Learnings, Service Blueprint, MVP Risks | Annotated Diagram, Prioritized Risk List, Action Backlog | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions |
Tagsno overlap | MVPValidationServiceDiscovery | RiskArchitectureWorkshopValidation | FacilitationAlignmentDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
