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 calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
MediumMediumLowLow
Timedifferent
45-60 min1-3 h1-2 h60-90 min
Participantsdifferent
2-85-303-104-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Assumption map, Test backlog, Risk rankingConsensus Clusters, Theme Titles, Priority AreasArchitecture Canvas, Goals, Constraints, Quality AttributesAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
AssumptionsRiskExperimentsValidation
FacilitationConsensusWorkshopAlignment
CanvasArchitectureAlignmentWorkshop
RiskArchitectureWorkshopValidation
Add more methods