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 |  Architecture Architecture Decision Record |  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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | Half day initial, dann laufend | 15-45 min | 30 min Setup, dann laufend |
Participantsdifferent | Ein Team plus Stakeholder | 1-3 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Async | Async |
Outputdifferent | Team API Document | ADR File, Decision Log, Rationale | RAID Log, Status Report Source |
Tagsno overlap | TeamAlignmentCommunicationService | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
