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
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff 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.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.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.
Complexitydifferent
MediumHighHigh
Timedifferent
1-3 WochenPreparation, scenario analysis, and findings review; effort depends on scopeSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
5-12 InterviewsArchitecture experts and stakeholders for scenarios and weightingEvaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Job Stories, Outcome Statements, Opportunity ListDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
CustomerOutcomesNeeds
ArchitectureChangeAnalysisComparisonQuality
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods

Often compared together

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

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)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis