View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Polarity Mapping |  Team Design Team API |  Architecture Architecture Decision Record |  Operations Accountability Ladder |
|---|---|---|---|---|
Purposedifferent | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | 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. | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-2 h | Half day initial, dann laufend | 15-45 min | 20-45 min |
Participantsdifferent | 3-12 | Ein Team plus Stakeholder | 1-3 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Team API Document | ADR File, Decision Log, Rationale | Ownership Reflection, Action Commitment, Coaching Notes |
Tagsno overlap | Systems thinkingTradeoffsLeadership | TeamAlignmentCommunicationService | ArchitectureRationaleDocumentationGovernance | ResponsibilityLeadershipTeam |