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 for DACI
Decision Making
DACI
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
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.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 domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
LowLowMediumLow
Timedifferent
30-60 min1-2 h2-8 h1-2 h
Participantsdifferent
2-103-105-123-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
DACI Matrix, Decision Owner, Decision LogArchitecture Canvas, Goals, Constraints, Quality AttributesEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
DecisionRolesGovernanceAlignment
CanvasArchitectureAlignmentWorkshop
Domain-Driven DesignEventsDiscoveryWorkshop
AlignmentArchitectureCanvas
Add more methods