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 PDCA Cycle | ![]() Facilitation Stakeholder Mapping | ![]() Delivery RAID Log |
|---|---|---|---|
Purposedifferent | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | 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. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 1 h bis mehrere Wochen | 60–90 min | 30 min Setup, dann laufend |
Participantsdifferent | 1-8 | 2-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Stakeholder Map, Engagement Plan, Risk Notes | RAID Log, Status Report Source |
Tagsno overlap | Continuous improvementLeanExperiments | StakeholdersAlignmentFacilitationChange | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






