Process / pipelineProblem StructuringProblem structuring methodsPipeline

SODA – Strategic Options Development and Analysis via Cognitive Mapping

Also known as: Cognitive Mapping, Strategic Options Development and Analysis, SODA Method, Bilişsel Haritalama

OriginatorColin EdenYear1988Sources1Related methods4

Strategic Options Development and Analysis (SODA) is a facilitated, qualitative method for structuring complex organisational problems. Developed by Colin Eden in 1988, it uses cognitive maps — directed graphs of causal constructs — to capture and integrate the subjective views of multiple stakeholders. SODA is most valuable when decision makers face ill-defined, wicked problems where shared understanding must be built before any quantitative analysis can begin.

Key highlights

  • Captures tacit, subjective knowledge that surveys and spreadsheets miss
  • Builds shared understanding among stakeholders with divergent worldviews
  • Reveals hidden leverage points and feedback loops in complex systems
  • Produces a jointly owned problem definition that increases commitment to action

Intuition

This section is available to Pro members. Upgrade to Pro

How it works

This section is available to Pro members. Upgrade to Pro

When to use it

Use SODA when a problem is complex, politically sensitive, and poorly defined — situations where stakeholders hold conflicting mental models and quantitative data alone cannot resolve the dispute. It suits early-stage strategy formulation, post-merger integration, public-policy scoping, and organisational change. Key assumptions: stakeholders are willing to engage in structured dialogue, a skilled facilitator is available, and the goal is shared understanding rather than a provably optimal solution. It is not appropriate when the problem is well-structured, time is extremely short, or participants refuse to articulate their views openly.

Strengths & limitations

Strengths
  • Captures tacit, subjective knowledge that surveys and spreadsheets miss
  • Builds shared understanding among stakeholders with divergent worldviews
  • Reveals hidden leverage points and feedback loops in complex systems
  • Produces a jointly owned problem definition that increases commitment to action
Limitations
  • Highly dependent on facilitator skill; poor facilitation leads to superficial maps
  • Group map can become unwieldy (hundreds of nodes) and hard to interpret
  • Does not produce a provably optimal solution — outcomes are negotiated, not computed
  • Time-intensive: full SODA engagement typically requires multiple workshop sessions

Common pitfalls

This section is available to Pro members. Upgrade to Pro

Applications

This section is available to Pro members. Upgrade to Pro

Frequently asked

How is SODA different from mind mapping?

Mind maps radiate from a central topic and organise information hierarchically without directional causality. SODA cognitive maps are signed directed graphs: every arrow explicitly represents a causal or means–end relationship and can be positive or negative. The structural analysis of loops, heads, and tails — central to SODA — has no equivalent in mind mapping, which is a personal knowledge-organisation tool rather than a participatory problem-structuring method.

Do I need specialised software to run SODA?

Decision Explorer (formerly COPE) is the purpose-built tool and significantly aids large-group map merging and structural analysis. However, small-scale applications can be conducted with sticky notes on a wall or generic graph-drawing tools, provided the facilitator tracks edge signs and performs centrality analysis manually. Software becomes essential when maps exceed roughly 50 nodes or when multiple individual maps must be merged systematically.

Can SODA be combined with quantitative methods?

Yes, and this is common practice. The cognitive map produced by SODA serves as a qualitative front end that identifies key variables and their hypothesised relationships. These can then seed a Fuzzy Cognitive Map for simulation, a System Dynamics model, or a multi-criteria analysis. The SODA stage ensures that the quantitative model reflects stakeholder knowledge rather than only analyst assumptions, improving both validity and stakeholder buy-in.

Sources

  1. 1.
    Eden, C. (1988). Cognitive mapping. European Journal of Operational Research, 36(1), 1–13.

You have read it. What now?

Cite this page

ScholarGate. (2026, June 2). SODA. ScholarGate. https://scholargate.app/problem-structuring/soda-cognitive-mapping