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 a JTBD interview notebook with a decision timeline, forces of change and a concise job hypothesis.
Product Discovery
Jobs to Be Done
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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought.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.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.
Complexitydifferent
MediumMediumHigh
Timedifferent
1-3 Wochen3–4 h for initial assessment; preparation and deeper analysis additionalPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
5-12 Interviews1 or a small team; particularly suitable for 3–4 peopleArchitecture experts and stakeholders for scenarios and weighting
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Job Stories, Outcome Statements, Opportunity ListLean 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 checksDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives
Tagsno overlap
CustomerOutcomesNeeds
ArchitectureQualityRiskAssessmentLean
ArchitectureChangeAnalysisComparisonQuality
Add more methods

Often compared together

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

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration of Opportunity Scoring with its method-specific working model.
Product Discovery
Opportunity Scoring