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
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
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)
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.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.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
MediumHighMediumLow
Timedifferent
30-60 min je Interview1 Tag bis mehrere Wochen3–4 h for initial assessment; preparation and deeper analysis additional60-90 min
Participantsdifferent
5-10 Interviews4-101 or a small team; particularly suitable for 3–4 people4-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Solution Feedback, Objection List, Validation NotesProblem Statement, Prototype, Test LearningsLean 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 checksAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
ValidationInterviewsPrototype
InnovationPrototypeResearch
ArchitectureQualityRiskAssessmentLean
RiskArchitectureWorkshopValidation
Add more methods