View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Team Design Team API |  Delivery Shape Up |
|---|---|---|---|
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. | 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. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 45-90 min | Half day initial, dann laufend | 6 Wochen Cycle + 2 Wochen Cool-Down |
Participantsdifferent | 3-12 | Ein Team plus Stakeholder | 2-4 pro Pitch |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Team API Document | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes |
Tagsno overlap | AlignmentStakeholdersTeam | TeamAlignmentCommunicationService | PlanningDeliveryAutonomy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
