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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
Paper illustration for DACI
Decision Making
DACI
Purposedifferent
arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible.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.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage20-60 min45-90 min30-60 min
Participantsdifferent
1-41-42-82-10
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewRunbook, Checklist, Escalation PathRACI Matrix, Responsibility Map, Decision NotesDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
ArchitectureDocumentationCommunication
OperationsReliabilityDocumentation
RolesResponsibilityGovernanceOperations
DecisionRolesGovernanceAlignment
Add more methods