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
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)
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing North Star Metric with its core stages and visible working result.
Growth
North Star Metric
Purposedifferent
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.The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design.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.When product teams track many metrics, the view of the actual customer outcome easily gets lost. A North Star Metric bundles growth, usage, and value contribution into one signal that makes the system's direction visible.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additionalMultiple workshops over several weeksSeveral meetings plus preparation and analysis; total effort depends on scope1-2 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-8Evaluation team, architects, and relevant stakeholders3-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Lean 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 checksHooked loop, Trigger map, Reward design, Ethics checkPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsNorth Star metric, Input metric tree, Measurement cadence
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
GrowthBehaviorRetention
ArchitectureQualityRiskTradeoffsStakeholders
GrowthMetricsAlignmentRetention
Add more methods