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)
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.
Complexitydifferent
HighHighMedium
Timedifferent
1 Tag bis mehrere WochenPreparation, scenario analysis, and findings review; effort depends on scope3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
4-10Architecture experts and stakeholders for scenarios and weighting1 or a small team; particularly suitable for 3–4 people
Formatdifferent
WorkshopWorkshop + 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 alternativesLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks
Tagsno overlap
InnovationPrototypeResearch
ArchitectureChangeAnalysisComparisonQuality
ArchitectureQualityRiskAssessmentLean
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Change Analysis.
Operations
Change Analysis
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis