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
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.
Complexitydifferent
LowLowLowHigh
Timedifferent
5-15 min60-90 min30-60 min1-6 Wochen
Participantsdifferent
1-54-122-84-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepAnnotated Diagram, Prioritized Risk List, Action BacklogFishbone Diagram, Cause Categories, Investigation Backlog8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
StartupValidationCompetition
RiskArchitectureWorkshopValidation
Root causeQualityOperations
QualityProblem solvingRoot cause
Add more methods