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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
MediumHighHighMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung1-4 hSeveral meetings plus preparation and analysis; total effort depends on scope60-120 min
Participantsdifferent
3-20 Reviewer3-8Evaluation team, architects, and relevant stakeholders2-8
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsChallenge Findings, Risk Register, Mitigation PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
ArchitectureDecisionAsyncGovernance
RiskDecisionSensemaking
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureCommunicationStakeholdersCanvas
Add more methods