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 Business Model Stress Test |  Facilitation Expectation Mapping |  Agile ROAM Board |
|---|---|---|---|---|
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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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. | 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 | Low | High | Low | Low |
Timedifferent | 30 min Setup, dann laufend | Half day | 45-90 min | 20-40 min initial, dann laufend |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-8 | 3-12 | 3-15 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Stress Test Report, Action Plan per Scenario | Expectation Map, Alignment Notes, Agreements | ROAM Board, Owner List |
Tagsno overlap | RiskTrackingStakeholdersGovernance | StrategyBusiness modelRiskDiagnosis | AlignmentStakeholdersTeam | RiskAgileTrackingAlignment |