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 of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.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.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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
90-180 min90-180 min initial, dann laufend1-2 Tage1-2 h
Participantsdifferent
3-63-81-44-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
GQM Table, Metric ProfilesKPI Tree, Owner ListArchitecture Document, Context View, Runtime View, Deployment ViewAlignment Map, Open Issues, Decision Questions
Tagsno overlap
MetricsMeasurementEngineeringAlignment
MetricsStrategyAlignmentMeasurement
ArchitectureDocumentationCommunication
AlignmentStakeholdersStrategyFacilitation
Add more methods