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 Systems Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |
|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | System Map, Dependencies, Leverage Points | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RAID Log, Status Report Source |
Tagsno overlap | Systems thinkingMappingBoundariesChange | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
