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 Expectation Mapping |  Agile Example Mapping |  Facilitation Stakeholder Salience Model |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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 a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | 30-60 min | 60-90 min | 60-90 min pro Feature |
Participantsdifferent | 3-12 | 3-7 | 3-6 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Example Map, Acceptance Criteria, Open Questions | Salience Diagram, Strategy per Class | Example Table, Acceptance Tests |
Tagsno overlap | AlignmentStakeholdersTeam | Behavior-Driven DevelopmentRequirementsExamplesRefinement | StakeholdersFacilitationAlignmentGovernance | AgileRequirementsExamplesBehavior-Driven Development |