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 Software Architecture Canvas |  Innovation Design Thinking |  Product Discovery Outcome-Driven Innovation |  Facilitation Consensus Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 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 | Low | High | High | Medium |
Timedifferent | 1-2 h | 1 Tag bis mehrere Wochen | Mehrere Wochen | 1-3 h |
Participantsdifferent | 3-10 | 4-10 | 2-6 researchers plus sample | 5-30 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Architecture Canvas, Goals, Constraints, Quality Attributes | Problem Statement, Prototype, Test Learnings | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | CanvasArchitectureAlignmentWorkshop | InnovationPrototypeResearch | OutcomesInnovationResearchQuantitative | FacilitationConsensusWorkshopAlignment |