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 calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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.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
LowLowMediumLow
Timedifferent
30-60 min1-2 h1-3 h60-90 min
Participantsdifferent
3-103-105-304-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Risk Matrix, Top Risk ListArchitecture Canvas, Goals, Constraints, Quality AttributesConsensus Clusters, Theme Titles, Priority AreasAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
RiskDecisionPrioritizationAssessment
CanvasArchitectureAlignmentWorkshop
FacilitationConsensusWorkshopAlignment
RiskArchitectureWorkshopValidation
Add more methods