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 Request for Comments |  Operations Causal Factor Analysis |  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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. | 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 | Medium | High | Low |
Timedifferent | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung | 2-6 h | 15-45 min |
Participantsdifferent | 3-12 | 3-20 Reviewer | 3-10 | 1-3 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | ADR File, Decision Log, Rationale |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ArchitectureDecisionAsyncGovernance | CausalityIncidentRoot causeTimeline | ArchitectureRationaleDocumentationGovernance |