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 Kepner-Tregoe
Operations
Kepner-Tregoe
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-3 hAs needed2-8 h1-4 h
Participantsdifferent
5-304-152-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Consensus Clusters, Theme Titles, Priority AreasIncident Log, Action Tracker, Stakeholder UpdatesProblem Analysis, Decision Analysis, Risk PlanProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
FacilitationConsensusWorkshopAlignment
IncidentOperationsReliability
Problem solvingRoot causeDecisionOperations
Root causeProblem solvingQualityIncident
Add more methods