View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |  Architecture Risk Storming |  Facilitation Consensus Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 60-90 min | 60-90 min | 1-3 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-6 | 4-12 | 5-30 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Salience Diagram, Strategy per Class | Annotated Diagram, Prioritized Risk List, Action Backlog | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance | RiskArchitectureWorkshopValidation | FacilitationConsensusWorkshopAlignment |