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 Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Purposedifferent
When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.
Complexitydifferent
HighMediumMediumHigh
Timedifferent
4-5 Tage45-60 min2-4 h2-6 h
Participantsdifferent
5-82-82-63-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prototype, Test Findings, Decision RationaleAssumption map, Test backlog, Risk rankingBarrier Inventory, Failure Analysis per Barrier, Action BacklogFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
Design sprintPrototypeValidationInnovation
AssumptionsRiskExperimentsValidation
Root causeSafetyIncident
RiskRoot causeSafety
Add more methods