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 Lean Canvas with nine fields, notes, and one highlighted learning risk.
Product Strategy
Lean Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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 an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable.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 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
MediumLowLowMedium
Timedifferent
45-90 min15-45 min1-2 h1-3 h
Participantsdifferent
1-61-33-105-30
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Lean Canvas, Core Assumptions, Experiment BacklogADR File, Decision Log, RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
StartupLeanAssumptionsBusiness model
ArchitectureRationaleDocumentationGovernance
CanvasArchitectureAlignmentWorkshop
FacilitationConsensusWorkshopAlignment
Add more methods