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 Specification by Example |  Decision Making Force Field Analysis |  Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 45-90 min | 60–90 min |
Participantsdifferent | 3-6 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Force Field Map, Change Levers, Risk Notes | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ChangeDecisionStrategy | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
