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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration of a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
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
An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.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
1-3 Wochen vom Draft bis zur Entscheidung45-90 min45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-20 Reviewer2-82-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsAnsoff Matrix, Growth Options, Risk NotesAssumption 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
ArchitectureDecisionAsyncGovernance
GrowthStrategyMarketPortfolio
AssumptionsRiskDecisionDiscovery
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods