View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research HEART Framework | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Delivery Communication Plan |
|---|---|---|---|
Purposedifferent | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 120 min initial, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 3-6 | Evaluation team, architects, and relevant stakeholders | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | HEART-GSM Table, Dashboard | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | MetricsUX researchMeasurementSatisfaction | ArchitectureQualityRiskTradeoffsStakeholders | CommunicationStakeholdersDeliveryPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






