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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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 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
LowMediumMediumLow
Timedifferent
20-60 minAs needed90-180 min initial, dann laufend30-60 min
Participantsdifferent
1-44-153-82-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathIncident Log, Action Tracker, Stakeholder UpdatesKPI Tree, Owner ListCounter Metric List, Guardrail Definitions
Tagsno overlap
OperationsReliabilityDocumentation
IncidentOperationsReliability
MetricsStrategyAlignmentMeasurement
MetricsMeasurementStrategyExperiments
Add more methods