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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration showing three sorted card stacks and an open question about a possible group.
UX Research
Card Sorting
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
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.When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations.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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
MediumLowHighMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional20-45 minSeveral meetings plus preparation and analysis; total effort depends on scope60-120 min
Participantsdifferent
Designers, developers as users, and facilitationBased on research questionEvaluation team, architects, and relevant stakeholders2-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsContent groups, Label set, IA hypothesesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
Information architectureNavigationStructure
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureCommunicationStakeholdersCanvas
Add more methods