View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Communication PlanCustomer Journey MappingATAM (Architecture Tradeoff Analysis Method)C4 Model
| Criterion |  Delivery Communication Plan |  UX Research Customer Journey Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | 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. | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 45-90 min | 2-4 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 h |
Participantsdifferent | 2-6 | 4-10 | Evaluation team, architects, and relevant stakeholders | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | Journey Map, Pain-point List, Opportunity Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | JourneyServiceService design | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureCommunicationVisualization |