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 Fishbone Diagram | ![]() Delivery RAID Log | ![]() Business Strategy Strategy Execution Loop |
|---|---|---|---|
Purposedifferent | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. |
Complexitydifferent | Low | Low | High |
Timedifferent | 30-60 min | 30 min Setup, dann laufend | Initial 3-6 h, then monthly or quarterly reviews |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 5-12 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | RAID Log, Status Report Source | Execution Loop, Review Cadence, Strategic Learning Log |
Tagsno overlap | Root causeQualityOperations | RiskTrackingStakeholdersGovernance | ExecutionCadenceLearningGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






