View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Consensus Workshop |  Operations Failure Mode and Effects Analysis |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | 2-6 h | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 5-30 | 3-10 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Consensus Clusters, Theme Titles, Priority Areas | FMEA Table, Risk Priority, Mitigation Actions | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | FacilitationConsensusWorkshopAlignment | RiskQualityOperationsRoot cause | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |