View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordArgument MappingAcceptance Criteria WorkshopSpecification by Example
| Criterion |  Architecture Architecture Decision Record |  Decision Making Argument Mapping |  Agile Acceptance Criteria Workshop |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 | 15-45 min | 1-3 h | 20-40 min pro Story | 60-90 min pro Feature |
Participantsdifferent | 1-3 | 1-8 | 3-6 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Argument Map, Evidence Gaps, Decision Rationale | Acceptance Criteria, Story Update | Example Table, Acceptance Tests |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | SensemakingDecisionRationale | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development |