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
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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
MediumMediumMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung1-3 Tage1-2 h30-60 min
Participantsdifferent
3-20 Reviewer1-44-122-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArchitecture Views, Cross-view Notes, RationaleAlignment Map, Open Issues, Decision QuestionsDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
ArchitectureDecisionAsyncGovernance
DocumentationStakeholdersArchitecture
AlignmentStakeholdersStrategyFacilitation
DecisionRolesGovernanceAlignment
Add more methods