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 |  UX Design Lean UX Canvas |  Architecture C4 Model |  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 Lean UX Canvas helps clarify user behavior, touchpoints, and concept decisions. It makes assumptions and desired outcomes visible and captures the result as a completed canvas, hypothesis list, and first experiment. | 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. | 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 | Medium | Low | Low |
Timedifferent | Mehrere Wochen | 2-3 h | 1-4 h | 1-2 Tage |
Participantsdifferent | 2-6 researchers plus sample | 3-8 | 1-5 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Completed Lean UX Canvas, Hypothesis list, First experiment | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | OutcomesInnovationResearchQuantitative | CanvasHypothesisOutcomesDiscovery | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication |