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
Paper illustration for Landing Page Test.
Product Discovery
Landing Page Test
Paper illustration for Risk Storming.
Architecture
Risk Storming
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When a value proposition first needs to be checked for resonance, it condenses the idea onto a focused entry page. It shows whether language and offering carry interest.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.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
MediumLowMediumHigh
Timedifferent
1-5 Tage60-90 min2–4 h review as a planning range; preparation and evaluation additionalSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
Nutzertraffic4-12Designers, developers as users, and facilitationEvaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Landing Page, Conversion Data, Learning SummaryAnnotated Diagram, Prioritized Risk List, Action BacklogPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ValidationConversionMarketing
RiskArchitectureWorkshopValidation
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods