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 Fault Tree Analysis.
Operations
Fault Tree Analysis
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Surveys method illustration showing its working structure
UX Research
Surveys
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
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.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 a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal.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.
Complexitydifferent
HighHighMediumMedium
Timedifferent
2-6 h4-5 Tage3-14 Tage2-4 h
Participantsdifferent
3-85-850+2-6
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsPrototype, Test Findings, Decision RationaleSurvey Results, Charts, Segment InsightsBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
RiskRoot causeSafety
Design sprintPrototypeValidationInnovation
QuantitativeResearchValidation
Root causeSafetyIncident
Add more methods