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
Paper illustration for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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.When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.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 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
LowMediumMediumMedium
Timedifferent
Stunden bis wenige Tage30-240 min2–4 h review as a planning range; preparation and evaluation additionalWochen bis Monate je Lernzyklus
Participantsdifferent
1-41-6Designers, developers as users, and facilitation2-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Pretotyping sketch, Test setup, Conversion data, Go or no-go decisionHypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsHypothesis list, MVPs, Learning reports, Pivot or persevere decision
Tagsno overlap
ValidationDemandMVP
TroubleshootingProblem solvingDiagnosis
ArchitectureEngineeringFeedbackValidationTasks
LeanStartupValidationMVP
Add more methods