View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Double Diamond |  Architecture Architecture Decision Record |  Agile Example Mapping |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement. | 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 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 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Wochen bis Monate | 15-45 min | 30-60 min | 20-40 min pro Story |
Participantsdifferent | 3-12 | 1-3 | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | ADR File, Decision Log, Rationale | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | ProcessDivergenceInnovation | ArchitectureRationaleDocumentationGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development |