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 Root Cause Analysis.
Operations
Root Cause Analysis
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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 a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.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 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.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
Stunden bis wenige Tage1-4 h2–4 h review as a planning range; preparation and evaluation additional1-6 Wochen
Participantsdifferent
1-43-8Designers, developers as users, and facilitation4-10
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Pretotyping sketch, Test setup, Conversion data, Go or no-go decisionProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
ValidationDemandMVP
Root causeProblem solvingQualityIncident
ArchitectureEngineeringFeedbackValidationTasks
QualityProblem solvingRoot cause
Add more methods