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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
Purposedifferent
With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 h1-3 h90-180 min initial, dann laufend90-180 min
Participantsdifferent
3-102-83-83-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Process Map, Handoff List, Improvement BacklogContext Map, Integration Patterns, Boundary NotesKPI Tree, Owner ListGQM Table, Metric Profiles
Tagsno overlap
ProcessOperationsImprovement
Domain-Driven DesignBoundariesStrategy
MetricsStrategyAlignmentMeasurement
MetricsMeasurementEngineeringAlignment
Add more methods