methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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.
Complexitydifferent
MediumLowLowHigh
Timedifferent
60-120 min30-60 min15-30 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-82-82-6Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Communication Canvas, Stakeholder Messages, Architecture Communication PlanFishbone Diagram, Cause Categories, Investigation BacklogRoot cause notes, CountermeasuresPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureCommunicationStakeholdersCanvas
Root causeQualityOperations
Root causeIncidentLeanProblem solving
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods