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: 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)
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Purposedifferent
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.Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs.
Complexitydifferent
HighMediumHigh
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope3–4 h for initial assessment; preparation and deeper analysis additionalMehrere Wochen
Participantsdifferent
Evaluation team, architects, and relevant stakeholders1 or a small team; particularly suitable for 3–4 people2-6 researchers plus sample
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized 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 checksDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureQualityRiskAssessmentLean
OutcomesInnovationResearchQuantitative
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
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis