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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
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.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.A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations.A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
1-2 hSeveral meetings plus preparation and analysis; total effort depends on scope1-3 h2-6 h
Participantsdifferent
3-12Evaluation team, architects, and relevant stakeholders2-81-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsCausal Loop Diagram, Feedback Notes, Leverage PointsStock and Flow Model, Dynamics Notes, Simulation Hypotheses
Tagsno overlap
Systems thinkingTradeoffsLeadership
ArchitectureQualityRiskTradeoffsStakeholders
FeedbackSystems thinkingCausalityDynamics
DynamicsSimulationFeedbackSystems thinking
Add more methods