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 Strategy Product Canvas |  Architecture arc42 |  Architecture Architecture Decision Record |  UX Design Lean UX Canvas |
|---|---|---|---|---|
Purposedifferent | When product goal and feature scope don't yet fit cleanly together, it creates a shared working picture. It connects need, core features, and assumptions into a solid starting point. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-2 h | 1-2 Tage | 15-45 min | 2-3 h |
Participantsdifferent | 2-8 | 1-4 | 1-3 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Product Canvas, Product Assumptions, Scope Notes | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Completed Lean UX Canvas, Hypothesis list, First experiment |
Tagsno overlap | CanvasDiscoveryScope | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | CanvasHypothesisOutcomesDiscovery |