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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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
Paper illustration for DACI
Decision Making
DACI
Purposedifferent
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.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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 h1-3 h15-45 min30-60 min
Participantsdifferent
3-102-81-32-10
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesIssue Map, Positions, Argument NotesADR File, Decision Log, RationaleDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
RationaleKnowledgeDecision
ArchitectureRationaleDocumentationGovernance
DecisionRolesGovernanceAlignment
Add more methods