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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Process Mapping method illustration showing its working structure
Operations
Process Mapping
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
15-45 min1-3 h45-90 min1-2 Tage
Participantsdifferent
1-33-102-51-4
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleProcess Map, Handoff List, Improvement BacklogA3 Report, Action Plan, Root Cause AnalysisArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ProcessOperationsImprovement
LeanProblem solvingCoachingOperations
ArchitectureDocumentationCommunication
Add more methods