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 Stakeholder Salience Model |  Agile Ideal Days |  Facilitation Dot Estimation |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-90 min | 15-60 min | 5-20 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-6 | 2-9 | 3-20 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Salience Diagram, Strategy per Class | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Effort Heatmap, Risk Signals, Discussion Targets | RAID Log, Status Report Source |
Tagsno overlap | StakeholdersFacilitationAlignmentGovernance | EstimationEffortAgile | EstimationEffortRisk | RiskTrackingStakeholdersGovernance |