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
Paper illustration of VRIO Framework with its method-specific working model.
Business Strategy
VRIO Framework
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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.The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
30-180 minStunden bis wenige Tage90-180 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-61-43-6Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaPretotyping sketch, Test setup, Conversion data, Go or no-go decisionVRIO Table, Strategic ActionsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
TroubleshootingDiagnosisEngineering
ValidationDemandMVP
StrategyDiagnosisBusiness modelCapability
ArchitectureEngineeringFeedbackValidationTasks
Add more methods