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 |  Product Discovery Product Kata |  Product Discovery Context Canvas |  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. | Product Kata helps clarify customer problems, solution ideas, and evidence through a repeatable improvement routine. It captures direction, current metric, target metric, experiment notes, and learning. | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | 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 | 1-2 Wochen je Loop | 45-90 min | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 3-10 | 3-10 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Direction, Current metric, Target metric, Experiment note, Learning report | Context canvas, Open questions, Shared context notes | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OutcomesDiscoveryLearningIterationCoaching | ContextFramingRequirementsCanvas | AgileRequirementsExamplesBehavior-Driven Development |