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 paper-based illustration representing Product Canvas with its core stages and visible working result.
Product Strategy
Product Canvas
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
When product goal and feature scope don't yet fit cleanly together, it creates a shared working picture. It connects need, core features, and assumptions into a solid starting point.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.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
1-2 h30-60 min1-4 h2-6 h
Participantsdifferent
2-82-83-83-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Product Canvas, Product Assumptions, Scope NotesFishbone Diagram, Cause Categories, Investigation BacklogProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
CanvasDiscoveryScope
Root causeQualityOperations
Root causeProblem solvingQualityIncident
RiskQualityOperationsRoot cause
Add more methods