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
Empathy Mapping
UX Research
Empathy Mapping
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture 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.When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
30-60 min30–60 min1-3 Wochen vom Draft bis zur Entscheidung1-2 h
Participantsdifferent
2-104-83-20 Reviewer3-10
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
DACI Matrix, Decision Owner, Decision LogEmpathy Map, Assumptions List, Research GapsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
DecisionRolesGovernanceAlignment
SynthesisQualitativeWorkshop
ArchitectureDecisionAsyncGovernance
CanvasArchitectureAlignmentWorkshop
Add more methods