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
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)
Paper illustration of a participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
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.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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.
Complexitydifferent
HighHighMediumMedium
Timedifferent
1 Tag bis mehrere WochenPreparation, scenario analysis, and findings review; effort depends on scope1-2 h je Session2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
4-10Architecture experts and stakeholders for scenarios and weightingBased on research questionDesigners, developers as users, and facilitation
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Problem 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 alternativesUsability Issues, Severity List, RecommendationsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
InnovationPrototypeResearch
ArchitectureChangeAnalysisComparisonQuality
ValidationUXPrototype
ArchitectureEngineeringFeedbackValidationTasks
Add more methods