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 |  Agile Example Mapping |
|---|---|---|---|
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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-2 h | 15-45 min | 30-60 min |
Participantsdifferent | 3-12 | 1-3 | 3-7 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | ADR File, Decision Log, Rationale | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ArchitectureRationaleDocumentationGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
