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 Pirate Metrics (AARRR) with its core stages and visible working result.
Growth
Pirate Metrics AARRR
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Purposedifferent
For products with complex usage paths, overall growth alone is too coarse to reveal bottlenecks. Pirate Metrics breaks the relationship with the product into consecutive stages and shows where the funnel actually leaks.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.
Complexitydifferent
MediumHighMedium
Timedifferent
1-2 h Setup, laufendSeveral meetings plus preparation and analysis; total effort depends on scope3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-8Evaluation team, architects, and relevant stakeholders1 or a small team; particularly suitable for 3–4 people
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
AARRR funnel, Metric baseline, Experiment backlogPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks
Tagsno overlap
GrowthMetricsExperiments
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureQualityRiskAssessmentLean
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics