View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Example MappingArchitecture Communication CanvasExpectation MappingSpecification by Example
| Criterion |  Agile Example Mapping |  Architecture Architecture Communication Canvas |  Facilitation Expectation Mapping |  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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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-120 min | 45-90 min | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 2-8 | 3-12 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Expectation Map, Alignment Notes, Agreements | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureCommunicationStakeholdersCanvas | AlignmentStakeholdersTeam | AgileRequirementsExamplesBehavior-Driven Development |