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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
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.The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage20-60 min45-90 min1-4 h
Participantsdifferent
1-41-42-81-5
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewRunbook, Checklist, Escalation PathRACI Matrix, Responsibility Map, Decision NotesContext Diagram, Container Diagram, Component Diagram
Tagsno overlap
ArchitectureDocumentationCommunication
OperationsReliabilityDocumentation
RolesResponsibilityGovernanceOperations
ArchitectureCommunicationVisualization
Add more methods