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 Monte Carlo Forecasting.
Delivery
Monte Carlo Forecasting
Paper illustration for Bottleneck Analysis.
Operations
Bottleneck Analysis
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
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.For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
HighMediumMedium
Timedifferent
30-90 min Setup, danach laufend1-3 h1-3 h
Participantsdifferent
1-83-83-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Forecast Percentiles, Throughput Dataset, Risk CommunicationBottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
ForecastingFlowDelivery
FlowMeasurementConstraints
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

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

Paper illustration for Theory of Constraints.
Operations
Theory of Constraints
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem