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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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)
Purposedifferent
For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
45-90 min30-180 min5-15 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-51-61-5Designers, developers as users, and facilitation
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
A3 Report, Action Plan, Root Cause AnalysisFault 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 revisions
Tagsno overlap
LeanProblem solvingCoachingOperations
TroubleshootingDiagnosisEngineering
StartupValidationCompetition
ArchitectureEngineeringFeedbackValidationTasks
Add more methods