methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration of Specification by Example with a method-specific labelled workspace.
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.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 Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.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
LowLowLowMedium
Timedifferent
30-60 min45-90 min1-2 h60-90 min pro Feature
Participantsdifferent
3-73-123-83-6
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsExpectation Map, Alignment Notes, AgreementsInception Canvas, Risks, Goal List, Open QuestionsExample Table, Acceptance Tests
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
AlignmentStakeholdersTeam
AlignmentArchitectureCanvas
AgileRequirementsExamplesBehavior-Driven Development
Add more methods