View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Business Strategy Strategy Execution Loop |  Agile 4Ls Retrospective |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 30 min Setup, dann laufend | Initial 3-6 h, then monthly or quarterly reviews | 45–75 min | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 5-12 | Team members involved | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Execution Loop, Review Cadence, Strategic Learning Log | 4Ls Board, Learning Themes, Improvement Actions | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ExecutionCadenceLearningGovernance | RetrospectiveLearningReflectionTeam | AlignmentStakeholdersTeam |