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 a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.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.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.
Complexitydifferent
MediumMediumHighHigh
Timedifferent
1-2 h60-180 minSeveral meetings plus preparation and analysis; total effort depends on scope1-4 h
Participantsdifferent
3-124-20Evaluation team, architects, and relevant stakeholders3-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsCynefin Map, Domain-specific Actions, Sensemaking NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
Systems thinkingTradeoffsLeadership
ComplexitySensemakingDecision
ArchitectureQualityRiskTradeoffsStakeholders
RiskDecisionSensemaking
Add more methods