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
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.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.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 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
MediumMediumHighHigh
Timedifferent
1-2 h1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope2-6 h
Participantsdifferent
3-122-8Evaluation team, architects, and relevant stakeholders1-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsCausal Loop Diagram, Feedback Notes, Leverage PointsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsStock and Flow Model, Dynamics Notes, Simulation Hypotheses
Tagsno overlap
Systems thinkingTradeoffsLeadership
FeedbackSystems thinkingCausalityDynamics
ArchitectureQualityRiskTradeoffsStakeholders
DynamicsSimulationFeedbackSystems thinking
Add more methods