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 Monte Carlo Forecasting.
Delivery
Monte Carlo Forecasting
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication.When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.
Complexitydifferent
LowHighMedium
Timedifferent
15-45 min30-90 min Setup, danach laufend1-3 h
Participantsdifferent
1-31-84-10
Formatdifferent
AsyncWorkshop + asyncWorkshop
Outputdifferent
ADR File, Decision Log, RationaleForecast Percentiles, Throughput Dataset, Risk CommunicationCurrent-state map, Future-state map, Bottleneck list
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ForecastingFlowDelivery
LeanFlowWasteDelivery
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments