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 PDCA Cycle.
Operations
PDCA Cycle
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Purposedifferent
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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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 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
LowMediumMediumLow
Timedifferent
1 h bis mehrere Wochen45-90 min1-3 h30-60 min
Participantsdifferent
1-82-52-82-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
PDCA Log, Experiment Plan, Learning Outcome, Standard ChangeA3 Report, Action Plan, Root Cause AnalysisContext Map, Integration Patterns, Boundary NotesCounter Metric List, Guardrail Definitions
Tagsno overlap
Continuous improvementLeanExperiments
LeanProblem solvingCoachingOperations
Domain-Driven DesignBoundariesStrategy
MetricsMeasurementStrategyExperiments
Add more methods