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.

Selected:Design ThinkingSurveysRAID LogATAM (Architecture Tradeoff Analysis Method)
Criterion
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
Surveys method illustration showing its working structure
UX Research
Surveys
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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
HighMediumLowHigh
Timedifferent
1 Tag bis mehrere Wochen3-14 Tage30 min Setup, dann laufendSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
4-1050+1-3 maintaining, briefing for everyoneEvaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopAsyncAsyncWorkshop + async
Outputdifferent
Problem Statement, Prototype, Test LearningsSurvey Results, Charts, Segment InsightsRAID Log, Status Report SourcePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
InnovationPrototypeResearch
QuantitativeResearchValidation
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods