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 for Change Analysis.
Operations
Change Analysis
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Surveys method illustration showing its working structure
UX Research
Surveys
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
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.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.When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal.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
MediumHighMediumHigh
Timedifferent
45-120 minMehrere Wochen3-14 TagePreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
2-62-6 researchers plus sample50+Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Change Matrix, Cause Hypotheses, Validation Questions, Action ListDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesSurvey Results, Charts, Segment InsightsDomain 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
ChangeRoot causeTroubleshootingComparison
OutcomesInnovationResearchQuantitative
QuantitativeResearchValidation
ArchitectureChangeAnalysisComparisonQuality
Add more methods