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 Rich Picture | ![]() Operations Scatter Diagram | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Low | High | High |
Timedifferent | 30-90 min | 30-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-6 Wochen |
Participantsdifferent | 2-10 | 1-4 | Evaluation team, architects, and relevant stakeholders | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Rich Picture, Problem Framing Notes | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | Systems thinkingSoft systemsFramingVisualization | Root causeQualityVisualization | ArchitectureQualityRiskTradeoffsStakeholders | QualityProblem solvingRoot cause |



