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)
Paper illustration for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
LowMediumMediumLow
Timedifferent
Stunden bis wenige Tage2–4 h review as a planning range; preparation and evaluation additional30-240 min60-90 min
Participantsdifferent
1-4Designers, developers as users, and facilitation1-64-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
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 revisionsHypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
ValidationDemandMVP
ArchitectureEngineeringFeedbackValidationTasks
TroubleshootingProblem solvingDiagnosis
RiskArchitectureWorkshopValidation
Add more methods