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 of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Purposedifferent
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.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.When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.
Complexitydifferent
LowMediumLow
Timedifferent
5-15 minAs needed1-5 Tage
Participantsdifferent
1-54-15Nutzertraffic
Formatdifferent
Workshop + asyncWorkshop + asyncAsync
Outputdifferent
VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepIncident Log, Action Tracker, Stakeholder UpdatesInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
StartupValidationCompetition
IncidentOperationsReliability
ValidationExperimentsDemandGrowth
Add more methods

Often compared together

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

Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem