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 Architecture Decision Record |  Architecture C4 Model |  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. | 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 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. | 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 | 15-45 min | 1-4 h | 2-3 h |
Participantsdifferent | 2-8 | 1-3 | 1-5 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Product Canvas, Product Assumptions, Scope Notes | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Completed Lean UX Canvas, Hypothesis list, First experiment |
Tagsno overlap | CanvasDiscoveryScope | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | CanvasHypothesisOutcomesDiscovery |