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 Bottleneck Analysis.
Operations
Bottleneck Analysis
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
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.When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 h1-3 h20–45 min1-3 h
Participantsdifferent
3-83-10Small cross-functional group2-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Bottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresDomain Context Map, Boundary Notes, Ownership MapRisk list, Mitigation plan, Assumption logContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
FlowMeasurementConstraints
Domain-Driven DesignContextBoundaries
RiskDecisionFailurePlanning
Domain-Driven DesignBoundariesStrategy
Add more methods