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 for Risk Storming.
Architecture
Risk Storming
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Purposedifferent
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.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.When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
60-90 min1-3 h1-5 Tage1-2 h
Participantsdifferent
4-125-30Nutzertraffic3-10
Formatdifferent
WorkshopWorkshopAsyncWorkshop
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogConsensus Clusters, Theme Titles, Priority AreasInterest Metrics, Conversion Signal, Learning NoteArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
RiskArchitectureWorkshopValidation
FacilitationConsensusWorkshopAlignment
ValidationExperimentsDemandGrowth
CanvasArchitectureAlignmentWorkshop
Add more methods