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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration for DACI
Decision Making
DACI
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
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.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.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
1-2 h30-60 min1-3 Wochen vom Draft bis zur Entscheidung1-2 h
Participantsdifferent
3-82-103-20 Reviewer3-10
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop
Outputdifferent
Inception Canvas, Risks, Goal List, Open QuestionsDACI Matrix, Decision Owner, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
AlignmentArchitectureCanvas
DecisionRolesGovernanceAlignment
ArchitectureDecisionAsyncGovernance
CanvasArchitectureAlignmentWorkshop
Add more methods