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 Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list.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.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
MediumLowMediumLow
Timedifferent
30-180 min5-15 min2–4 h review as a planning range; preparation and evaluation additional60-90 min
Participantsdifferent
1-61-5Designers, developers as users, and facilitation4-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
TroubleshootingDiagnosisEngineering
StartupValidationCompetition
ArchitectureEngineeringFeedbackValidationTasks
RiskArchitectureWorkshopValidation
Add more methods