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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
A paper tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
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.For easily distracted solo work, the method sets clear time boundaries for concentrated work. It protects attention when large tasks would otherwise fall apart into small avoidance moves.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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowLowLowMedium
Timedifferent
15-30 min25 min Zyklen5-15 min1-4 h
Participantsdifferent
2-611-53-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresFocus Sessions, Task Progress, Interruption NotesVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
FocusTime managementProductivityExecution
StartupValidationCompetition
Root causeProblem solvingQualityIncident
Add more methods