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 |  Delivery RAID Log |  Architecture Software Architecture Canvas |
|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-2 h | 30 min Setup, dann laufend | 1-2 h |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-10 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | RAID Log, Status Report Source | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RiskTrackingStakeholdersGovernance | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
