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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Purposedifferent
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.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.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.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
MediumLowMediumLow
Timedifferent
1-3 h1 h bis mehrere Wochen90-180 min initial, dann laufend30-60 min
Participantsdifferent
2-81-83-82-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Map, Integration Patterns, Boundary NotesPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeKPI Tree, Owner ListCounter Metric List, Guardrail Definitions
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
Continuous improvementLeanExperiments
MetricsStrategyAlignmentMeasurement
MetricsMeasurementStrategyExperiments
Add more methods