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 sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.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.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.
Complexitydifferent
MediumLowHighLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope60–90 min
Participantsdifferent
Designers, developers as users, and facilitation2-8Evaluation team, architects, and relevant stakeholders2-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsPower Interest Grid, Strategy per StakeholderPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsStakeholder Map, Engagement Plan, Risk Notes
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
StakeholdersFacilitationAlignmentPlanning
ArchitectureQualityRiskTradeoffsStakeholders
StakeholdersAlignmentFacilitationChange
Add more methods