View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Change Analysis |  Agile Specification by Example |  Facilitation Stakeholder Mapping |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 45-120 min | 60-90 min pro Feature | 60–90 min | 30-60 min |
Participantsdifferent | 2-6 | 3-6 | 2-8 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Example Table, Acceptance Tests | Stakeholder Map, Engagement Plan, Risk Notes | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | AgileRequirementsExamplesBehavior-Driven Development | StakeholdersAlignmentFacilitationChange | Behavior-Driven DevelopmentRequirementsExamplesRefinement |