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 | ![]() Architecture Architecture Decision Record | ![]() Operations Runbook |
|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-2 h | 15-45 min | 20-60 min |
Participantsdifferent | 3-12 | 1-3 | 1-4 |
Formatdifferent | Workshop | Async | Async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | ADR File, Decision Log, Rationale | Runbook, Checklist, Escalation Path |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ArchitectureRationaleDocumentationGovernance | OperationsReliabilityDocumentation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






