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 Kaizen Event.
Operations
Kaizen Event
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Purposedifferent
For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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.
Complexitydifferent
MediumMediumLow
Timedifferent
0.5-5 TageAs needed5-15 min
Participantsdifferent
4-104-151-5
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Kaizen Charter, Waste List, Improvement Experiments, Standard Work UpdateIncident Log, Action Tracker, Stakeholder UpdatesVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step
Tagsno overlap
LeanContinuous improvementOperations
IncidentOperationsReliability
StartupValidationCompetition
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem