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
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture 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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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.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
MediumMediumLowMedium
Timedifferent
1-3 Wochen1-2 h1-2 h1-3 h
Participantsdifferent
5-12 Interviews4-123-105-30
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Job Stories, Outcome Statements, Opportunity ListAlignment Map, Open Issues, Decision QuestionsArchitecture Canvas, Goals, Constraints, Quality AttributesConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
CustomerOutcomesNeeds
AlignmentStakeholdersStrategyFacilitation
CanvasArchitectureAlignmentWorkshop
FacilitationConsensusWorkshopAlignment
Add more methods