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 four-quadrant grid with tasks sorted by importance and urgency and translated into actions.
Decision Making
Eisenhower Matrix
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration for Risk Storming.
Architecture
Risk Storming
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Purposedifferent
It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.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.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
15-30 min1-3 h60-90 min1-2 h
Participantsdifferent
1-65-304-123-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Eisenhower Matrix, Action List, Delegation NotesConsensus Clusters, Theme Titles, Priority AreasAnnotated Diagram, Prioritized Risk List, Action BacklogArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
PrioritizationFocusTasks
FacilitationConsensusWorkshopAlignment
RiskArchitectureWorkshopValidation
CanvasArchitectureAlignmentWorkshop
Add more methods