View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | 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. | 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 | Low | Low | Medium |
Timedifferent | 60-90 min | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 4-12 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskArchitectureWorkshopValidation | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
