View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Ideal Days |  Facilitation Stakeholder Mapping |  Delivery RAID Log |  Facilitation Dot Estimation |
|---|---|---|---|---|
Purposedifferent | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | 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. | 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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-60 min | 60–90 min | 30 min Setup, dann laufend | 5-20 min |
Participantsdifferent | 2-9 | 2-8 | 1-3 maintaining, briefing for everyone | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Stakeholder Map, Engagement Plan, Risk Notes | RAID Log, Status Report Source | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | EstimationEffortAgile | StakeholdersAlignmentFacilitationChange | RiskTrackingStakeholdersGovernance | EstimationEffortRisk |