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 A3 Problem Solving |  DevOps Incident Command |  Facilitation Stakeholder Salience Model |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 45-90 min | As needed | 60-90 min | 60–90 min |
Participantsdifferent | 2-5 | 4-15 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Incident Log, Action Tracker, Stakeholder Updates | Salience Diagram, Strategy per Class | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | LeanProblem solvingCoachingOperations | IncidentOperationsReliability | StakeholdersFacilitationAlignmentGovernance | StakeholdersAlignmentFacilitationChange |