View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Design Lean UX Canvas |  Architecture Architecture Decision Record |  Product Discovery Outcome-Driven Innovation |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 2-3 h | 15-45 min | Mehrere Wochen | 1-2 Tage |
Participantsdifferent | 3-8 | 1-3 | 2-6 researchers plus sample | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Completed Lean UX Canvas, Hypothesis list, First experiment | ADR File, Decision Log, Rationale | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | CanvasHypothesisOutcomesDiscovery | ArchitectureRationaleDocumentationGovernance | OutcomesInnovationResearchQuantitative | ArchitectureDocumentationCommunication |