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
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 of a participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
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.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.When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down.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 min1 Tag bis mehrere Wochen1-2 h je SessionPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
2-64-10Based on research questionArchitecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Change Matrix, Cause Hypotheses, Validation Questions, Action ListProblem Statement, Prototype, Test LearningsUsability Issues, Severity List, RecommendationsDomain 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
InnovationPrototypeResearch
ValidationUXPrototype
ArchitectureChangeAnalysisComparisonQuality
Add more methods