View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Eisenhower Matrix |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture arc42 |  Decision Making Pareto Analysis |
|---|---|---|---|---|
Purposedifferent | It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 15-30 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 Tage | 30-60 min |
Participantsdifferent | 1-6 | Evaluation team, architects, and relevant stakeholders | 1-4 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Eisenhower Matrix, Action List, Delegation Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Architecture Document, Context View, Runtime View, Deployment View | Pareto Chart, Top Causes, Focus List |
Tagsno overlap | PrioritizationFocusTasks | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureDocumentationCommunication | PrioritizationQualityFocusRoot cause |