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 the Consensus Workshop working structure.
Facilitation
Consensus Workshop
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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Purposedifferent
When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
MediumMediumHighLow
Timedifferent
1-3 hAs needed2-6 h30-60 min
Participantsdifferent
5-304-153-102-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Consensus Clusters, Theme Titles, Priority AreasIncident Log, Action Tracker, Stakeholder UpdatesFMEA Table, Risk Priority, Mitigation ActionsFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
FacilitationConsensusWorkshopAlignment
IncidentOperationsReliability
RiskQualityOperationsRoot cause
Root causeQualityOperations
Add more methods