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 Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Purposedifferent
In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage.When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h30–60 min per interview45-90 min1-2 h
Participantsdifferent
3-81 participant per interview2-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Failure Scenarios, Risk Notes, Control Gaps, Test and Response ActionsInterview Notes, Themes, Insight SummaryAssumption List, Critical Assumptions, Learning PlanDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
FailureResilienceRisk
QualitativeResearchCustomerDiscovery
AssumptionsRiskDecisionDiscovery
StrategyDecisionAssumptionsHypothesis
Add more methods