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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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
MediumMediumMediumHigh
Timedifferent
60-120 min2–4 h review as a planning range; preparation and evaluation additional45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-8Designers, developers as users, and facilitation2-5Evaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Communication Canvas, Stakeholder Messages, Architecture Communication PlanPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsA3 Report, Action Plan, Root Cause AnalysisPrioritized 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
ArchitectureEngineeringFeedbackValidationTasks
LeanProblem solvingCoachingOperations
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods