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
Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work.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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.
Complexitysame
LowLowLowLow
Timedifferent
Ongoing15-45 min30-60 min1-2 Tage
Participantsdifferent
1-201-32-81-4
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Visual Board, Status Indicators, Exception CuesADR File, Decision Log, RationaleFishbone Diagram, Cause Categories, Investigation BacklogArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
SignalsOperationsVisual management
ArchitectureRationaleDocumentationGovernance
Root causeQualityOperations
ArchitectureDocumentationCommunication
Add more methods