ArticleslgStudy

engineering

Soft systems methodology

Soft systems methodology is a engineering topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Soft systems methodology rather than just read about it. In short: Soft systems methodology (SSM) is an organised way of thinking applicable to problematic social situations and in the management of change by using action. It was developed in England by academics at the Lancaster Systems Department on the basis of a ten-year action research programme.

Key takeaways

  • Soft systems methodology belongs to engineering; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Soft systems methodology to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Soft systems methodology from memory before moving on to harder problems.

Reference excerpt

Soft systems methodology (SSM) is an organised way of thinking applicable to problematic social situations and in the management of change by using action. It was developed in England by academics at the Lancaster Systems Department on the basis of a ten-year action research programme.

Overview The Soft Systems Methodology was developed primarily by Peter Checkland, through 10 years of research with his colleagues, such as Brian Wilson. The method was derived from numerous earlier systems engineering processes, primarily because traditional 'hard' systems thinking was not able to account for larger organisational issues with many complex relationships. SSM has a primary use in the analysis of these complex situations, where there are divergent views about the definition of the problem. These complex situations are known as "soft problems". They are usually real world problems where the goals and purposes of the problem are problematic themselves. Examples of soft problems include: How to improve the delivery of health services? and How to manage homelessness with young people? Soft approaches take as tacit that people's view of the world will change all the time and their preferences of it will also change. Depending on the current circumstances of a situation, trying to agree on the problem may be difficult as there might be multiple factors to take into consideration, such as all the different kinds of methods used to tackle these problems. Additionally, Peter Checkland had moved away from the idea of 'obvious' problems and started working with situations to make concepts of models to use them as a source of questions to help with the problem. Soft systems methodologies then started to emerge as an organised learning system. Purposeful activity models could be declared using worldviews, meaning they were never models of real-world action. Still, those relevant to disclosure and argument about real-world action led to them being called epistemological devices that could be used for discourse and debate. The distinction between the everyday world and systems thinking was to draw attention to the conscious use of systems language in developing intellectual devices which were used to structure debates or an exploration of the problem situation being addressed. In its 'classic' form the methodology consists of seven steps, with initial appreciation of the problem situation leading to the modelling of several human activity systems that might be thought relevant to the problem situation. By getting all the relevant people who are the decision-makers in this situation to come together, sit down in discussion and exploration about the definition of the problem. Only then will the decision makers in said situation will more likely arrive at a mutual agreement which will settle any arguments or problems and help get to the solution over exactly what kind of changes could be either systemically desirable and feasible in the situation at hand. Later explanations of the ideas give a more sophisticated view of this systemic method and give more attention to locating the methodology with respect to its philosophical underpinnings. It is the earlier classical view which is most widely used in practice (created by Peter Checkland). A common criticism of this earlier methodology is that it follows an approach that is too linear. Checkland himself agreed that the earlier methodology is 'rather bald'. Most advanced SSM analysts will agree, though, that the classical view is an easy way for inexperienced analysts to learn the SSM methodology. SSM has been successfully used as a business analysis methodology in various fields. Real-world examples of SSM's wide range of applicability include research applying SSM in the sugar industry leading to improvements in business partner relationships, successful use as an approach in project management by directly involving stakeholders or aiding in business management by improving communication between stakeholders. It has proven to be a useful analysis approach to teaching and learning processes, as it does not require a specific problem to be identified as its starting point – which has led to "outside of the box" suggestions for improvement. SSM was even used by the UK government as part of the revaluation of their Structured Systems Analysis and Design Method (SSADM) system development methodology. Even professional researchers who are to take the change for face value structure of thinking, show the same tendency to distort perceptions of the world rather than change the mental structure which we give our bearings with. Failure of classic systems in rich 'management' problem situations during the research programme led to examining the adequacy of the systems thinking. The methodology has been described in several books and many academic articles. SSM remains the most widely used and practical application of systems thinking, and other systems approaches such as critical systems thinking have incorporated many of its ideas.

Representation evolution SSM had a gradual development process of the methodology as a whole from 1972 to 1990. During this period of time, four different representations of SSM were designed, becoming more sophisticated and at the same time less structured and broader in scope.

Blocks and arrows (1972) The first studies in the research programme were carried out in 1969, and the first account of what became SSM was published in a paper three-years later titled "Towards a systems-based methodology for real-world problem solving" (Checkland 1972). In this paper, soft systems methodology is presented as a sequence of stages with iteration back to previous stages.The sequence was as follows: analysis, root definition of relevant systems, conceptualisation, comparison and definition of changes, selection of change to implement, design of change and implementation and appraisal. The overall aim to implement change instead of introducing or enhancing a system implies that the thinking was ongoing as a result of these early experiences, even if the straight arrows in the diagrams and the rectangular blocks in some of the models can now be misleading!

… excerpt ends here. Continue reading the full article.

Worked examples

Example 1 — a first encounter with Soft systems methodology

Start with the simplest possible case. Write down what Soft systems methodology claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In engineering, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Soft systems methodology before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Soft systems methodology ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Soft systems methodology

In research
Soft systems methodology appears in engineering research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Soft systems methodology in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Soft systems methodology is common in secondary-school and first-year university syllabi. It links to neighbouring topics Enterprise modelling, Methodology, Problem structuring methods, so understanding it makes those chapters shorter.
In everyday life
Look for Soft systems methodology outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Soft systems methodology in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Soft systems methodology means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Soft systems methodology out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Soft systems methodology in simple terms?

Soft systems methodology (SSM) is an organised way of thinking applicable to problematic social situations and in the management of change by using action. It was developed in England by academics at the Lancaster Systems Department on the basis of a ten-year action research programme.

Why does Soft systems methodology matter?

Because it connects several engineering ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Soft systems methodology?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Soft systems methodology.

Tags

  • Enterprise modelling
  • Methodology
  • Problem structuring methods
  • Systems theory

Keep exploring