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 of a decision table with criteria rows, weighted ratings, and a narrowly leading alternative.
Decision Making
Decision Matrix
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic.When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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
MediumLowLowHigh
Timedifferent
45-90 minHalf day initial, dann laufend45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-8Ein Team plus Stakeholder2-8Evaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Decision Matrix, Scoring Rationale, Selected OptionTeam API DocumentAssumption List, Critical Assumptions, Learning PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
DecisionCriteriaScoringTradeoffs
TeamAlignmentCommunicationService
AssumptionsRiskDecisionDiscovery
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods