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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Pretotyping with its method-specific working model.
Product Discovery
Pretotyping
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 of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Purposedifferent
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data.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.For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight.
Complexitydifferent
LowLowMediumMedium
Timedifferent
30 min Setup, dann laufendStunden bis wenige Tage3–4 h for initial assessment; preparation and deeper analysis additionalWochen bis Monate je Lernzyklus
Participantsdifferent
1-3 maintaining, briefing for everyone1-41 or a small team; particularly suitable for 3–4 people2-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourcePretotyping sketch, Test setup, Conversion data, Go or no-go decisionLean 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 checksHypothesis list, MVPs, Learning reports, Pivot or persevere decision
Tagsno overlap
RiskTrackingStakeholdersGovernance
ValidationDemandMVP
ArchitectureQualityRiskAssessmentLean
LeanStartupValidationMVP
Add more methods