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 of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
Purposedifferent
When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.
Complexitydifferent
LowMediumHighLow
Timedifferent
30-60 minAs needed2-6 h30-60 min
Participantsdifferent
3-104-153-101-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Risk Matrix, Top Risk ListIncident Log, Action Tracker, Stakeholder UpdatesFMEA Table, Risk Priority, Mitigation ActionsPareto Chart, Top Causes, Focus List
Tagsno overlap
RiskDecisionPrioritizationAssessment
IncidentOperationsReliability
RiskQualityOperationsRoot cause
PrioritizationQualityFocusRoot cause
Add more methods