View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Growth Golden Circle |  Team Design Team API |  Agile Specification by Example |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | In positioning and communication, what an offering actually stands for often becomes blurred. The Golden Circle sharpens a product's inner rationale and connects purpose, approach, and offering into a clear statement. | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-60 min | Half day initial, dann laufend | 60-90 min pro Feature | 45-90 min |
Participantsdifferent | 1-8 | Ein Team plus Stakeholder | 3-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Why Statement, Messaging Notes, Positioning Draft | Team API Document | Example Table, Acceptance Tests | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | MarketingPositioningCommunication | TeamAlignmentCommunicationService | AgileRequirementsExamplesBehavior-Driven Development | AlignmentStakeholdersTeam |