View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Expectation MappingArchitecture Communication CanvasSpecification by ExampleExample Mapping
| Criterion |  Facilitation Expectation Mapping |  Architecture Architecture Communication Canvas |  Agile Specification by Example |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 60-120 min | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 3-12 | 2-8 | 3-6 | 3-7 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AlignmentStakeholdersTeam | ArchitectureCommunicationStakeholdersCanvas | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |