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 Pretotyping with its method-specific working model.
Product Discovery
Pretotyping
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Purposedifferent
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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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
LowMediumLowMedium
Timedifferent
Stunden bis wenige Tage2–4 h review as a planning range; preparation and evaluation additional15-30 minWochen bis Monate je Lernzyklus
Participantsdifferent
1-4Designers, developers as users, and facilitation2-62-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Pretotyping sketch, Test setup, Conversion data, Go or no-go decisionPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsRoot cause notes, CountermeasuresHypothesis list, MVPs, Learning reports, Pivot or persevere decision
Tagsno overlap
ValidationDemandMVP
ArchitectureEngineeringFeedbackValidationTasks
Root causeIncidentLeanProblem solving
LeanStartupValidationMVP
Add more methods