Method guideSystems Thinking

Soft Systems Methodology

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityHigh

Time0.5-3 Tage

Participants5-15

FormatWorkshop

MaturityCanonical

Plan Soft Systems Methodology

Prerequisite

What needs to be finished first

Complete firstClear boundary

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

Without a boundary, cases, periods, or variables become mixed.

Complete firstEvidence access

Interview and observation notes, rich-picture surface, CATWOE, root definitions, conceptual activity models, and comparison log

Missing sources remain visible as uncertainty.

Preparation

What needs to be ready before start

Materials

Interview and observation notes, rich-picture surface, CATWOE, root definitions, conceptual activity models, and comparison log

People / roles

SSM facilitator · participants with different worldviews · situation owner · scribe

Pre-read

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

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.

Core question

The one question this method answers

Which different purposeful systems help us understand the messy situation and negotiate changes that are both desirable and feasible?

Flow

Phases with goal, actions, output and pitfall

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.

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

1
Situation
Rich picture
Goal
Rich picture: Show facts, perceptions, relationships, conflicts, roles, and the observer position in a rich picture.
Inputs for this step
- 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
Actions
- Show facts, perceptions, relationships, conflicts, roles, and the observer position in a rich picture.
Output
Rich picture
Show facts, perceptions, relationships, conflicts, roles, and the observer position in a rich picture.
Quality check
Does it contain hard and soft information plus conflicting perspectives?
Pitfall
The rich picture becomes a tidy process map. Add relationships, feelings, conflicts, symbols, and the observer position.
Timing: 60–90 minutes
2
Perspectives
Root definitions
Goal
Root definitions: Select several relevant purposeful activity systems and write CATWOE plus PQR root definition for each view.
Inputs for this step
- Rich picture
Actions
- Select several relevant purposeful activity systems and write CATWOE plus PQR root definition for each view.
Output
Root definitions
Select several relevant purposeful activity systems and write CATWOE plus PQR root definition for each view.
Quality check
Are transformation and worldview clear in each definition, with perspectives kept separate?
Pitfall
One allegedly objective root definition replaces all worldviews. Model at least two potentially conflicting perspectives separately.
Timing: 60–90 minutes
3
Models
Activity models
Goal
Activity models: Derive logically necessary activities from each root definition as a conceptual verb model, without copying current process.
Inputs for this step
- Root definitions
Actions
- Derive logically necessary activities from each root definition as a conceptual verb model, without copying current process.
Output
Activity models
Derive logically necessary activities from each root definition as a conceptual verb model, without copying current process.
Quality check
Is every activity logically required by the root definition and phrased as a verb?
Pitfall
The model only reproduces current departments and systems. Start from the root definition and state necessary activities solution-neutrally.
Timing: 45–75 minutes
4
Compare
Comparison log
Goal
Comparison log: Compare conceptual models with perceived real world and use differences as learning questions.
Inputs for this step
- Activity models
Actions
- Compare conceptual models with perceived real world and use differences as learning questions.
Output
Comparison log
Compare conceptual models with perceived real world and use differences as learning questions.
Quality check
Does each difference create a reasoned question rather than a simple gap judgment?
Pitfall
The conceptual model becomes the mandated target design. Discuss differences, cultural feasibility, and alternative realisations.
Timing: 60–90 minutes
5
Change
Change agenda
Goal
Change agenda: Negotiate systemically desirable and culturally feasible changes; set learning and next iteration.
Inputs for this step
- Comparison log
Actions
- Negotiate systemically desirable and culturally feasible changes; set learning and next iteration.
Output
Change agenda
Negotiate systemically desirable and culturally feasible changes; set learning and next iteration.
Quality check
Are changes desirable, feasible, owned, and testable?
Pitfall
The group chooses only technically attractive changes. Test each change against benefit, power, culture, owner, and review.
Timing: 45–75 minutes

Artifact

What comes out at the end

Sketch: what the artifact looks like

Soft Systems Methodology · ChecklandUnstrukturierte Problemsituationen über Perspektiven, Root Definitions, Konzeptmodelle und machbare Veränderungen bearbeiten

Form

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

Versioning / ownership

Record date, owner, source state, and review date; preserve prior versions.

Tool alternatives

Rich picture
CATWOE and PQR root definitions
Conceptual activity models and comparison matrix

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

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

soft-systems-methodology-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Soft Systems Methodology · working structure

Rich picture

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

Root definitions

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

Activity models

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

Comparison log

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

Change agenda

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

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Rich pictureThe rich picture becomes a tidy process map.View in phase
Root definitionsOne allegedly objective root definition replaces all worldviews.View in phase
Activity modelsThe model only reproduces current departments and systems.View in phase
Comparison logThe conceptual model becomes the mandated target design.View in phase
Change agendaThe group chooses only technically attractive changes.View in phase

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Situation: Does it contain hard and soft information plus conflicting perspectives?

Stop Perspectives: Are transformation and worldview clear in each definition, with perspectives kept separate?

Stop Models: Is every activity logically required by the root definition and phrased as a verb?

Stop Compare: Does each difference create a reasoned question rather than a simple gap judgment?

Stop Change: Are changes desirable, feasible, owned, and testable?

Where to go next?

Facilitation

Problem Framing Workshop

Translates the negotiated change agenda into a workable problem question.

Systems Thinking

Intervention Mapping

Links the negotiated changes to an implementable intervention program with evaluation.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods