methodatlas

Systems Thinking Process model

Soft Systems Methodology

Develops a conceptual picture for difficult organisational issues from a Rich Picture and Root Definitions.

The situation is first described as a rich picture or problem field. The team then develops Root Definitions and Conceptual Models, compares them with reality, and derives feasible changes. The method creates a reflective path from perception to intervention.

Core question
Which different purposeful systems help us understand the messy situation and negotiate changes that are both desirable and feasible?
Participants
5-15
Time
Two to five workshops across several weeks; add field access and comparison conversations.

Evidence building, analysis, and effectiveness review form a multi-stage initiative.

Paper illustration for Soft Systems Methodology.
  1. Situation

    Rich picture

    Show facts, perceptions, relationships, conflicts, roles, and the observer position in a rich picture.

  2. Perspectives

    Root definitions

    Select several relevant purposeful activity systems and write CATWOE plus PQR root definition for each view.

  3. Models

    Activity models

    Derive logically necessary activities from each root definition as a conceptual verb model, without copying current process.

  4. Compare

    Comparison log

    Compare conceptual models with perceived real world and use differences as learning questions.

  5. Change

    Change agenda

    Negotiate systemically desirable and culturally feasible changes; set learning and next iteration.

Add new evidence at review and version decisions with the prior state.

A good fit when

Soft Systems Methodology hilft, unklare oder politisch aufgeladene Probleme systematisch zu erkunden. Statt eine schnelle Antwort zu erzwingen, baut die Methode ein gemeinsames Verständnis für Perspektiven und Handlungsräume auf.

Ideal for

  • Complex organizational topics
  • Systemic transformation
  • Stakeholder-rich problems

Not good for

  • Acute troubleshooting
  • Simple process deviations
  • Pure technical diagnosis

Outputs

  • Change agenda

    SSM learning record with rich picture, perspective-specific root definitions, conceptual activity models, real-world comparison, and agreed changes.

Soft Systems Methodology · working structure

Fictional example

Fictional values show the actual method fields.

Rich picture

Show facts, perceptions, relationships, conflicts, roles, and the observer position in a rich picture.

Workshops wait, Warehouse prioritises express cases, Sales promises speed; data flow, conflict, and observer are drawn.

Root definitions

Select several relevant purposeful activity systems and write CATWOE plus PQR root definition for each view.

Workshop view: predictable pickup to limit downtime; Warehouse view: capacity-aware flow for safe handoff.

Activity models

Derive logically necessary activities from each root definition as a conceptual verb model, without copying current process.

Capture demand → determine capacity → confirm slot → prepare handoff → monitor effect.

Comparison log

Compare conceptual models with perceived real world and use differences as learning questions.

Determine capacity is absent today; question: who could do it with which data before confirmation?

Change agenda

Negotiate systemically desirable and culturally feasible changes; set learning and next iteration.

Four-week capacity-slot pilot; Lea owns; warehouse and workshops review wait and predictability; update rich picture.

All values are fictional.

Reference · original teaching example

First step

Set one unstructured problem situation, affected perspectives, and investigation boundary; leave solutions explicitly open.

Open the method guide

Deep dive

Purpose

Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.

How it works

First, the situation is described as a rich picture or problem field. The team then develops root definitions and conceptual models, compares them with reality, and derives feasible changes from them. This creates a reflected path from perception to intervention.

In detail

Soft Systems Methodology treats problems as different perceptions of a situation rather than as clearly objective defects. Rich pictures, root definitions, and conceptual models help develop several meaningful viewpoints. Those models are compared with the real situation to find desirable and feasible changes. The method creates learning between stakeholders, not just a technical solution.

Facilitation

Plan several working phases and invite different perspectives. Use visualization to make abstract system models tangible, and formulate changes explicitly as desirable and feasible. Keep the process open enough for learning but clear enough to produce concrete next steps.

The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics
Artifact templates
Soft Systems Methodology: WorksheetSet subject, evidence, roles, flow, and review.
markdown

soft-systems-methodology-working-template.md

Set subject, evidence, roles, flow, and review.

Soft Systems Methodology: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Whole initiative Time: Two to five workshops across several weeks; add field access and comparison conversations.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Interview and observation notes, rich-picture surface, CATWOE, root definitions, conceptual activity models, and comparison log
  • Roles: SSM facilitator · participants with different worldviews · situation owner · scribe
  • Advance information: Set one unstructured problem situation, affected perspectives, and investigation boundary; leave solutions explicitly open.
  • Overall time needed: Two to five workshops across several weeks; add field access and comparison conversations.
  • Setup: Prepare a workspace with Situation · Perspectives · Models · Compare · Change; separate example from live data.

Prepare for the work steps

Situation: Rich picture

  • Set one unstructured problem situation, affected perspectives, and investigation boundary; leave solutions explicitly open.
  • Interview and observation notes, rich-picture surface, CATWOE, root definitions, conceptual activity models, and comparison log

Perspectives: Root definitions

  • Rich picture

Models: Activity models

  • Root definitions

Compare: Comparison log

  • Activity models

Change: Change agenda

  • Comparison log

Soft Systems Methodology · working structure

Rich picture

Show facts, perceptions, relationships, conflicts, roles, and the observer position in a rich picture.

...

Root definitions

Select several relevant purposeful activity systems and write CATWOE plus PQR root definition for each view.

...

Activity models

Derive logically necessary activities from each root definition as a conceptual verb model, without copying current process.

...

Comparison log

Compare conceptual models with perceived real world and use differences as learning questions.

...

Change agenda

Negotiate systemically desirable and culturally feasible changes; set learning and next iteration.

...

The blank worksheet contains prompts only.

Reference · original teaching example

Situation: Rich picture

Expected artifact: Rich picture

Show facts, perceptions, relationships, conflicts, roles, and the observer position in a rich picture.

Entry:

...

  • Does it contain hard and soft information plus conflicting perspectives?

Perspectives: Root definitions

Expected artifact: Root definitions

Select several relevant purposeful activity systems and write CATWOE plus PQR root definition for each view.

Entry:

...

  • Are transformation and worldview clear in each definition, with perspectives kept separate?

Models: Activity models

Expected artifact: Activity models

Derive logically necessary activities from each root definition as a conceptual verb model, without copying current process.

Entry:

...

  • Is every activity logically required by the root definition and phrased as a verb?

Compare: Comparison log

Expected artifact: Comparison log

Compare conceptual models with perceived real world and use differences as learning questions.

Entry:

...

  • Does each difference create a reasoned question rather than a simple gap judgment?

Change: Change agenda

Expected artifact: Change agenda

Negotiate systemically desirable and culturally feasible changes; set learning and next iteration.

Entry:

...

  • Are changes desirable, feasible, owned, and testable?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/soft-systems-methodology/run-sheet

Alternatives and neighbors

Fitting alternatives with decision guidance, followed by other related methods.

All methods
Constraints and origin
HighWorkshop0.5-3 Tage

Profile

Method form
Process model
Participants
5-15
Time
0.5-3 Tage
Maturity
Canonical
Origin
Peter Checkland
Paper illustration for Problem Framing Workshop.
Next up: Problem Framing Workshop