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 |  Facilitation Alignment Mapping |  Delivery RAID Log |
|---|---|---|---|
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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Half day initial, dann laufend | 1-2 h | 30 min Setup, dann laufend |
Participantsdifferent | Ein Team plus Stakeholder | 4-12 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Team API Document | Alignment Map, Open Issues, Decision Questions | RAID Log, Status Report Source |
Tagsno overlap | TeamAlignmentCommunicationService | AlignmentStakeholdersStrategyFacilitation | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
