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)
Paper illustration for Flywheel.
Growth
Flywheel
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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.
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 scope60-120 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-8Evaluation team, architects, and relevant stakeholders3-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
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 investigationsFlywheel Map, Friction Points, Growth Levers, Experiment Backlog
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
GrowthBehaviorRetention
ArchitectureQualityRiskTradeoffsStakeholders
GrowthRetentionConversion
Add more methods