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 an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Purposedifferent
IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-3 h15-45 min1-2 h90-180 min
Participantsdifferent
2-81-33-104-12
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Issue Map, Positions, Argument NotesADR File, Decision Log, RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesDecision Rights Matrix, Agreement
Tagsno overlap
RationaleKnowledgeDecision
ArchitectureRationaleDocumentationGovernance
CanvasArchitectureAlignmentWorkshop
DecisionGovernanceAlignmentResponsibility
Add more methods