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 Risk Storming.
Architecture
Risk Storming
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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.
Complexitydifferent
LowMediumLowHigh
Timedifferent
60-90 min90-180 min initial, dann laufend30-60 min1-4 Wochen
Participantsdifferent
4-123-82-61-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogKPI Tree, Owner ListCounter Metric List, Guardrail DefinitionsExperiment results, Decision log, Learning summary
Tagsno overlap
RiskArchitectureWorkshopValidation
MetricsStrategyAlignmentMeasurement
MetricsMeasurementStrategyExperiments
ExperimentsGrowthAnalyticsValidation
Add more methods