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 of Double Diamond with its method-specific working model.
Innovation
Double Diamond
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
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
For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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
MediumMediumMediumLow
Timedifferent
Wochen bis Monate45-60 min3–4 h for initial assessment; preparation and deeper analysis additional60-90 min
Participantsdifferent
3-122-81 or a small team; particularly suitable for 3–4 people4-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Problem Statement, Solution Options, Prototypes, Deliverables per PhaseAssumption map, Test backlog, Risk rankingLean 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
ProcessDivergenceInnovation
AssumptionsRiskExperimentsValidation
ArchitectureQualityRiskAssessmentLean
RiskArchitectureWorkshopValidation
Add more methods