View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Delegation Poker |  Delivery RAID Log |  Agile ROAM Board |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 45-90 min |
Participantsdifferent | 3-10 | 1-3 maintaining, briefing for everyone | 3-15 | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | RAID Log, Status Report Source | ROAM Board, Owner List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | AutonomyRolesTeam | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | AlignmentStakeholdersTeam |