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 |  Facilitation Responsibility Poker |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-2 h | 45-90 min | 15-45 min | 1-2 Tage |
Participantsdifferent | 3-12 | 3-10 | 1-3 | 1-4 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Responsibility Map, Role Agreements, Open Questions | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RolesResponsibilityTeamFacilitation | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |