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 PDCA Cycle.
Operations
PDCA Cycle
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.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.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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
LowLowHighLow
Timedifferent
1 h bis mehrere Wochen5-15 min1-6 Wochen15-30 min
Participantsdifferent
1-81-54-102-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
PDCA Log, Experiment Plan, Learning Outcome, Standard ChangeVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanRoot cause notes, Countermeasures
Tagsno overlap
Continuous improvementLeanExperiments
StartupValidationCompetition
QualityProblem solvingRoot cause
Root causeIncidentLeanProblem solving
Add more methods