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 for Fault Isolation.
Engineering
Fault Isolation
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)
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Purposedifferent
In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected.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 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
MediumLowMediumMedium
Timedifferent
30-180 minStunden bis wenige Tage2–4 h review as a planning range; preparation and evaluation additionalWochen bis Monate je Lernzyklus
Participantsdifferent
1-61-4Designers, developers as users, and facilitation2-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaPretotyping 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 revisionsHypothesis list, MVPs, Learning reports, Pivot or persevere decision
Tagsno overlap
TroubleshootingDiagnosisEngineering
ValidationDemandMVP
ArchitectureEngineeringFeedbackValidationTasks
LeanStartupValidationMVP
Add more methods