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
Paper illustration of HEART Framework with its method-specific working model.
UX Research
HEART Framework
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 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.Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard.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
LowMediumMediumLow
Timedifferent
20-60 min120 min initial, dann laufendAs needed30-60 min
Participantsdifferent
1-43-64-152-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathHEART-GSM Table, DashboardIncident Log, Action Tracker, Stakeholder UpdatesCounter Metric List, Guardrail Definitions
Tagsno overlap
OperationsReliabilityDocumentation
MetricsUX researchMeasurementSatisfaction
IncidentOperationsReliability
MetricsMeasurementStrategyExperiments
Add more methods