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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
Purposedifferent
arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.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.Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.
Complexitydifferent
LowHighMediumMedium
Timedifferent
1-2 Tage1-4 Wochen90-180 min initial, dann laufend90-180 min
Participantsdifferent
1-41-63-83-6
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewExperiment results, Decision log, Learning summaryKPI Tree, Owner ListGQM Table, Metric Profiles
Tagsno overlap
ArchitectureDocumentationCommunication
ExperimentsGrowthAnalyticsValidation
MetricsStrategyAlignmentMeasurement
MetricsMeasurementEngineeringAlignment
Add more methods