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
Paper illustration of a JTBD interview notebook with a decision timeline, forces of change and a concise job hypothesis.
Product Discovery
Jobs to Be Done
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of Lean UX Canvas with its method-specific working model.
UX Design
Lean UX Canvas
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Purposedifferent
When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 Wochen1-2 h2-3 h1-3 h
Participantsdifferent
5-12 Interviews3-103-85-30
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Job Stories, Outcome Statements, Opportunity ListArchitecture Canvas, Goals, Constraints, Quality AttributesCompleted Lean UX Canvas, Hypothesis list, First experimentConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
CustomerOutcomesNeeds
CanvasArchitectureAlignmentWorkshop
CanvasHypothesisOutcomesDiscovery
FacilitationConsensusWorkshopAlignment
Add more methods