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
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Bottleneck Analysis.
Operations
Bottleneck Analysis
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.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.
Complexitysame
MediumMediumMedium
Timesame
1-3 h1-3 h1-3 h
Participantsdifferent
3-83-83-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Context Canvas, Glossary, Integration NotesBottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
Domain-Driven DesignBoundariesModeling
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