methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Product Canvas with its core stages and visible working result.
Product Strategy
Product Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Lean UX Canvas with its method-specific working 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.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 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
MediumLowLowMedium
Timedifferent
1-2 h15-45 min1-2 Tage2-3 h
Participantsdifferent
2-81-31-43-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Product Canvas, Product Assumptions, Scope NotesADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment ViewCompleted Lean UX Canvas, Hypothesis list, First experiment
Tagsno overlap
CanvasDiscoveryScope
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
CanvasHypothesisOutcomesDiscovery
Add more methods