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 Kaizen Event | ![]() Delivery RAID Log | ![]() Facilitation Stakeholder Mapping | ![]() Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments. | 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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 0.5-5 Tage | 30 min Setup, dann laufend | 60–90 min | 20-40 min initial, dann laufend |
Participantsdifferent | 4-10 | 1-3 maintaining, briefing for everyone | 2-8 | 3-15 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update | RAID Log, Status Report Source | Stakeholder Map, Engagement Plan, Risk Notes | ROAM Board, Owner List |
Tagsno overlap | LeanContinuous improvementOperations | RiskTrackingStakeholdersGovernance | StakeholdersAlignmentFacilitationChange | RiskAgileTrackingAlignment |



