View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Delivery Shape Up |  Decision Making Constraint Analysis |
|---|---|---|---|
Purposedifferent | 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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Half day initial, dann laufend | 6 Wochen Cycle + 2 Wochen Cool-Down | 30-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 2-4 pro Pitch | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Team API Document | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | TeamAlignmentCommunicationService | PlanningDeliveryAutonomy | ConstraintsDecisionPlanningOptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
