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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration for DACI
Decision Making
DACI
Purposedifferent
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.When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.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.
Complexitydifferent
MediumHighLowLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung45-90 min1-2 h30-60 min
Participantsdifferent
3-20 Reviewer3-103-82-10
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRanked Backlog, Cost-of-Delay AssumptionsInception Canvas, Risks, Goal List, Open QuestionsDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
ArchitectureDecisionAsyncGovernance
LeanEconomicsSequencePrioritization
AlignmentArchitectureCanvas
DecisionRolesGovernanceAlignment
Add more methods