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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
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 of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Purposedifferent
For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.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.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.
Complexitydifferent
HighLowMediumLow
Timedifferent
1-4 h1-2 h1-3 h60-90 min
Participantsdifferent
3-83-105-304-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Challenge Findings, Risk Register, Mitigation PlanArchitecture Canvas, Goals, Constraints, Quality AttributesConsensus Clusters, Theme Titles, Priority AreasProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
RiskDecisionSensemaking
CanvasArchitectureAlignmentWorkshop
FacilitationConsensusWorkshopAlignment
FacilitationDecisionProblem solvingWorkshop
Add more methods