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 for Pareto Analysis
Decision Making
Pareto Analysis
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 Eat the Frog
Operations
Eat the Frog
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.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.The method protects energy and attention for the task that creates the largest progress and is often postponed.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
30-60 min15-45 min15-90 min daily1-2 Tage
Participantsdifferent
1-61-311-4
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Pareto Chart, Top Causes, Focus ListADR File, Decision Log, RationalePriority Task, Completion Note, Daily FocusArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
PrioritizationQualityFocusRoot cause
ArchitectureRationaleDocumentationGovernance
PrioritizationProductivityFocusExecution
ArchitectureDocumentationCommunication
Add more methods