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 Dot Estimation | ![]() Facilitation Expectation Mapping | ![]() Facilitation Stakeholder Salience Model | ![]() Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 5-20 min | 45-90 min | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-20 | 3-12 | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop | Workshop | Async |
Outputdifferent | Effort Heatmap, Risk Signals, Discussion Targets | Expectation Map, Alignment Notes, Agreements | Salience Diagram, Strategy per Class | RAID Log, Status Report Source |
Tagsno overlap | EstimationEffortRisk | AlignmentStakeholdersTeam | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |



