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 a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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
When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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
MediumLowHighMedium
Timedifferent
45-60 min60-90 min1-6 Wochen3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-84-124-101 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Assumption map, Test backlog, Risk rankingAnnotated Diagram, Prioritized Risk List, Action Backlog8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanLean 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
AssumptionsRiskExperimentsValidation
RiskArchitectureWorkshopValidation
QualityProblem solvingRoot cause
ArchitectureQualityRiskAssessmentLean
Add more methods