View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Fault Tree Analysis | ![]() Facilitation Barcamp | ![]() Facilitation Stakeholder Salience Model | ![]() Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | When many people can contribute knowledge and the flow should stay open, Barcamp provides a framework for self-organized sessions. The format channels energy without defining the content too narrowly in advance. | 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. | 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. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | 2-6 h | Halber Tag bis 2 Tage | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-8 | 15-200 | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | Workshop | Async |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Session Board, Session Notes, Community Learnings | Salience Diagram, Strategy per Class | RAID Log, Status Report Source |
Tagsno overlap | RiskRoot causeSafety | FacilitationLarge groupLearning | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |



