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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture 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.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.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 hPreparation, scenario analysis, and findings review; effort depends on scope1-3 h2-6 h
Participantsdifferent
3-12Architecture experts and stakeholders for scenarios and weighting2-81-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesCausal Loop Diagram, Feedback Notes, Leverage PointsStock and Flow Model, Dynamics Notes, Simulation Hypotheses
Tagsno overlap
Systems thinkingTradeoffsLeadership
ArchitectureChangeAnalysisComparisonQuality
FeedbackSystems thinkingCausalityDynamics
DynamicsSimulationFeedbackSystems thinking
Add more methods