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)
Paper illustration for Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop 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 Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots.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.
Complexitydifferent
MediumHighLowMedium
Timedifferent
1-2 hPreparation, scenario analysis, and findings review; effort depends on scope20-45 min1-3 h
Participantsdifferent
3-12Architecture experts and stakeholders for scenarios and weighting1-102-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
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 alternativesBehavior Over Time Graph, Trend Hypotheses, Key EventsCausal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap
Systems thinkingTradeoffsLeadership
ArchitectureChangeAnalysisComparisonQuality
Systems thinkingPatternsDynamics
FeedbackSystems thinkingCausalityDynamics
Add more methods