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 Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
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 Causal Factor Analysis.
Operations
Causal Factor Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.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
HighLowHighLow
Timedifferent
Half day15-45 min2-6 h1-2 Tage
Participantsdifferent
3-121-33-101-4
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Leverage Map, Action StrategyADR File, Decision Log, RationaleEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
Systems thinkingChangeStrategy
ArchitectureRationaleDocumentationGovernance
CausalityIncidentRoot causeTimeline
ArchitectureDocumentationCommunication
Add more methods