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 | ![]() Operations Runbook | ![]() Operations RACI Matrix | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-2 h | 20-60 min | 45-90 min | 15-45 min |
Participantsdifferent | 3-12 | 1-4 | 2-8 | 1-3 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Runbook, Checklist, Escalation Path | RACI Matrix, Responsibility Map, Decision Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | Systems thinkingTradeoffsLeadership | OperationsReliabilityDocumentation | RolesResponsibilityGovernanceOperations | ArchitectureRationaleDocumentationGovernance |



