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 arc42 |  Architecture Software Architecture Canvas |  Architecture C4 Model |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Mehrere Wochen | 1-2 Tage | 1-2 h | 1-4 h |
Participantsdifferent | 2-6 researchers plus sample | 1-4 | 3-10 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Architecture Document, Context View, Runtime View, Deployment View | Architecture Canvas, Goals, Constraints, Quality Attributes | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureDocumentationCommunication | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationVisualization |