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
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
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
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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.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
15-45 min30-60 min30-60 min1-2 Tage
Participantsdifferent
1-31-62-81-4
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationalePareto Chart, Top Causes, Focus ListFishbone Diagram, Cause Categories, Investigation BacklogArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
PrioritizationQualityFocusRoot cause
Root causeQualityOperations
ArchitectureDocumentationCommunication
Add more methods