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 Solution Interview
Product Discovery
Solution Interview
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
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
Purposedifferent
When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.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.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.
Complexitydifferent
MediumHighHighHigh
Timedifferent
30-60 min je Interview4-5 TagePreparation, scenario analysis, and findings review; effort depends on scope1 Tag bis mehrere Wochen
Participantsdifferent
5-10 Interviews5-8Architecture experts and stakeholders for scenarios and weighting4-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Solution Feedback, Objection List, Validation NotesPrototype, Test Findings, Decision RationaleDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesProblem Statement, Prototype, Test Learnings
Tagsno overlap
ValidationInterviewsPrototype
Design sprintPrototypeValidationInnovation
ArchitectureChangeAnalysisComparisonQuality
InnovationPrototypeResearch
Add more methods