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 |  Facilitation Consensus Workshop |  Architecture arc42 |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
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 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Mehrere Wochen | 1-3 h | 1-2 Tage | 1-2 h |
Participantsdifferent | 2-6 researchers plus sample | 5-30 | 1-4 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Consensus Clusters, Theme Titles, Priority Areas | Architecture Document, Context View, Runtime View, Deployment View | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | OutcomesInnovationResearchQuantitative | FacilitationConsensusWorkshopAlignment | ArchitectureDocumentationCommunication | CanvasArchitectureAlignmentWorkshop |