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 Delegation Poker.
Facilitation
Delegation Poker
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Purposedifferent
When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.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.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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.
Complexitydifferent
LowHighMediumLow
Timedifferent
45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope1-2 h45-90 min
Participantsdifferent
3-10Evaluation team, architects, and relevant stakeholders1-83-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsConcept Map, Relationship Labels, Knowledge GapsExpectation Map, Alignment Notes, Agreements
Tagsno overlap
AutonomyRolesTeam
ArchitectureQualityRiskTradeoffsStakeholders
KnowledgeConceptsMappingSensemaking
AlignmentStakeholdersTeam
Add more methods