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
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Paper illustration of Double Diamond with its method-specific working model.
Innovation
Double Diamond
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 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.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.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
HighMediumMediumLow
Timedifferent
4-5 TageWochen bis Monate3–4 h for initial assessment; preparation and deeper analysis additional60-90 min
Participantsdifferent
5-83-121 or a small team; particularly suitable for 3–4 people4-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Prototype, Test Findings, Decision RationaleProblem Statement, Solution Options, Prototypes, Deliverables per PhaseLean 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
Design sprintPrototypeValidationInnovation
ProcessDivergenceInnovation
ArchitectureQualityRiskAssessmentLean
RiskArchitectureWorkshopValidation
Add more methods