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 Change Analysis |  Delivery RAID Log |  Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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 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 | Low | Low |
Timedifferent | 45-120 min | 30 min Setup, dann laufend | 60–90 min |
Participantsdifferent | 2-6 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | RAID Log, Status Report Source | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | RiskTrackingStakeholdersGovernance | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
