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 Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
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
Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.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
HighLowLowMedium
Timedifferent
90-180 min15-45 min1-2 h90-180 min
Participantsdifferent
3-81-33-104-12
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
CoD Table, Prioritization SequenceADR File, Decision Log, RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesDecision Rights Matrix, Agreement
Tagsno overlap
PrioritizationDeliveryEconomicsDecision
ArchitectureRationaleDocumentationGovernance
CanvasArchitectureAlignmentWorkshop
DecisionGovernanceAlignmentResponsibility
Add more methods