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 |  Architecture C4 Model |  Facilitation Consensus Workshop |  Architecture arc42 |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Mehrere Wochen | 1-4 h | 1-3 h | 1-2 Tage |
Participantsdifferent | 2-6 researchers plus sample | 1-5 | 5-30 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Context Diagram, Container Diagram, Component Diagram | Consensus Clusters, Theme Titles, Priority Areas | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureCommunicationVisualization | FacilitationConsensusWorkshopAlignment | ArchitectureDocumentationCommunication |