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 Outcome-Driven Innovation |  Product Discovery Context Canvas |  Architecture Software Architecture Canvas |  Facilitation Consensus Workshop |
|---|---|---|---|---|
Purposedifferent | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Mehrere Wochen | 45-90 min | 1-2 h | 1-3 h |
Participantsdifferent | 2-6 researchers plus sample | 3-10 | 3-10 | 5-30 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Context canvas, Open questions, Shared context notes | Architecture Canvas, Goals, Constraints, Quality Attributes | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ContextFramingRequirementsCanvas | CanvasArchitectureAlignmentWorkshop | FacilitationConsensusWorkshopAlignment |