View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Domain Modeling Context Map |  Facilitation Stakeholder Salience Model |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-3 h | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-8 | 2-8 | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Context Map, Integration Patterns, Boundary Notes | Salience Diagram, Strategy per Class | RAID Log, Status Report Source |
Tagsno overlap | FailureResilienceRisk | Domain-Driven DesignBoundariesStrategy | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |