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 for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration for Change Analysis.
Operations
Change Analysis
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.When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
1-3 WochenPreparation, scenario analysis, and findings review; effort depends on scope30-240 min45-120 min
Participantsdifferent
5-12 InterviewsArchitecture experts and stakeholders for scenarios and weighting1-62-6
Formatsame
Workshop + asyncWorkshop + 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 alternativesHypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
CustomerOutcomesNeeds
ArchitectureChangeAnalysisComparisonQuality
TroubleshootingProblem solvingDiagnosis
ChangeRoot causeTroubleshootingComparison
Add more methods