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 Example Mapping |  Decision Making Cynefin Workshop |  Architecture Architecture Decision Record |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | Medium | Low | Medium |
Timedifferent | 30-60 min | 60-180 min | 15-45 min | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 4-20 | 1-3 | 3-6 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Cynefin Map, Domain-specific Actions, Sensemaking Notes | ADR File, Decision Log, Rationale | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ComplexitySensemakingDecision | ArchitectureRationaleDocumentationGovernance | AgileRequirementsExamplesBehavior-Driven Development |