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 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
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.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.
Complexitysame
HighHighHighHigh
Timedifferent
1 Tag bis mehrere Wochen2-6 h4-5 TageSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
4-103-105-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Problem Statement, Prototype, Test LearningsFMEA Table, Risk Priority, Mitigation ActionsPrototype, Test Findings, Decision RationalePrioritized 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
RiskQualityOperationsRoot cause
Design sprintPrototypeValidationInnovation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods