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 for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Purposedifferent
When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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.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.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.
Complexitydifferent
LowMediumHighMedium
Timedifferent
45-90 min1-3 Wochen vom Draft bis zur EntscheidungSeveral meetings plus preparation and analysis; total effort depends on scope90-180 min
Participantsdifferent
3-123-20 ReviewerEvaluation team, architects, and relevant stakeholders4-12
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Expectation Map, Alignment Notes, AgreementsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsDecision Rights Matrix, Agreement
Tagsno overlap
AlignmentStakeholdersTeam
ArchitectureDecisionAsyncGovernance
ArchitectureQualityRiskTradeoffsStakeholders
DecisionGovernanceAlignmentResponsibility
Add more methods