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 of HEART Framework with its method-specific working model.
UX Research
HEART Framework
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
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.Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard.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.When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 h120 min initial, dann laufend1-3 h30-60 min
Participantsdifferent
3-83-63-102-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Bottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresHEART-GSM Table, DashboardDomain Context Map, Boundary Notes, Ownership MapCounter Metric List, Guardrail Definitions
Tagsno overlap
FlowMeasurementConstraints
MetricsUX researchMeasurementSatisfaction
Domain-Driven DesignContextBoundaries
MetricsMeasurementStrategyExperiments
Add more methods