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.

Selected:SurveysChange AnalysisDesign ThinkingSAAM (Software Architecture Analysis Method)
Criterion
Surveys method illustration showing its working structure
UX Research
Surveys
Paper illustration for Change Analysis.
Operations
Change Analysis
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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
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.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.For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.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
MediumMediumHighHigh
Timedifferent
3-14 Tage45-120 min1 Tag bis mehrere WochenPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
50+2-64-10Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Survey Results, Charts, Segment InsightsChange Matrix, Cause Hypotheses, Validation Questions, Action ListProblem Statement, Prototype, Test LearningsDomain 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
QuantitativeResearchValidation
ChangeRoot causeTroubleshootingComparison
InnovationPrototypeResearch
ArchitectureChangeAnalysisComparisonQuality
Add more methods