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 of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Hypothesis Prioritization Canvas with a method-specific labelled workspace.
Product Discovery
Hypothesis Prioritization 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 experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric.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 hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog.
Complexitydifferent
MediumLowHighMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope60-90 min
Participantsdifferent
Designers, developers as users, and facilitation1-5Evaluation team, architects, and relevant stakeholders3-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsCompleted Experiment Canvas, Success MetricPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPrioritization Canvas, Hypothesis Backlog
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ExperimentsValidationDiscoveryHypothesis
ArchitectureQualityRiskTradeoffsStakeholders
ExperimentsPrioritizationDiscoveryHypothesis
Add more methods