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
Paper illustration for Learning Review.
Operations
Learning Review
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
1-2 Tage1-3 hAs needed20-60 min
Participantsdifferent
1-43-104-151-4
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewLearning Review Notes, System Factors, Improvement ActionsIncident Log, Action Tracker, Stakeholder UpdatesRunbook, Checklist, Escalation Path
Tagsno overlap
ArchitectureDocumentationCommunication
LearningRetrospectiveIncidentOperations
IncidentOperationsReliability
OperationsReliabilityDocumentation
Add more methods