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 Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Purposedifferent
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.When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.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.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
HighMediumLowHigh
Timedifferent
2-6 h2-8 h45-90 min1-6 Wochen
Participantsdifferent
3-105-122-84-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
FMEA Table, Risk Priority, Mitigation ActionsEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsAssumption List, Critical Assumptions, Learning Plan8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
RiskQualityOperationsRoot cause
Domain-Driven DesignEventsDiscoveryWorkshop
AssumptionsRiskDecisionDiscovery
QualityProblem solvingRoot cause
Add more methods