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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Purposedifferent
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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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
MediumMediumLow
Timedifferent
45-90 minAs needed30-60 min
Participantsdifferent
2-54-152-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
A3 Report, Action Plan, Root Cause AnalysisIncident Log, Action Tracker, Stakeholder UpdatesCounter Metric List, Guardrail Definitions
Tagsno overlap
LeanProblem solvingCoachingOperations
IncidentOperationsReliability
MetricsMeasurementStrategyExperiments
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper scorecard with four perspectives, connected objective cards and columns for measures, targets and initiatives.
Business Strategy
Balanced Scorecard
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem