Government Operational Research Service (GORS) Assessment Problem Structuring and Soft OR Methods Syllabus

Problem Structuring and Soft OR Methods syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Problem Structuring and Soft OR Methods in Government Operational Research Service (GORS) Assessment, not a summary of it.

1. 1

   The Problem Structuring Test

   4 topics

   • Format and expectations of the timed test
     • Choosing one question from a set of options
     • Real-world government scenario framing
   • Demonstrating structured thinking under time pressure
   • Assessment criteria: clarity, logic and feasibility
   • Presenting and defending a structured approach
2. 2

   Framing and scoping a problem

   4 topics

   • Clarifying the real question behind a commission
     • Identifying the decision to be supported
     • Distinguishing symptoms from underlying problems
   • Identifying objectives, constraints and stakeholders
   • Defining scope, assumptions and success criteria
   • Setting analytical questions and hypotheses
3. 3

   Soft OR and problem structuring methods (PSMs)

   4 topics

   • Soft Systems Methodology (SSM)
     • Rich pictures and CATWOE
     • Conceptual models and root definitions
   • Strategic Options Development and Analysis (SODA) and cognitive mapping
   • Strategic Choice Approach
   • Drivers, influence and causal-loop diagrams
4. 4

   Structuring tools and logic

   4 topics

   • Issue trees, logic models and theory of change
   • Stakeholder mapping and analysis
   • Driver mapping and prioritisation matrices
   • Identifying data, evidence and method requirements

Problem Structuring and Soft OR Methods flashcards for Government Operational Research Service (GORS) Assessment

19 of 51 cards from the Problem Structuring and Soft OR Methods deck — real questions with worked answers.

1. What is the primary purpose of Problem Structuring Methods (PSMs) / Soft OR?

   To help groups make sense of complex, messy, ill-defined problem situations (where objectives are unclear or conflicting) by structuring the problem itself, rather than optimising a pre-defined model. They focus on understanding and agreeing on the problem before solving it.

2. How do 'Soft OR' methods differ from 'Hard OR' methods?

   Hard OR assumes a well-defined problem with clear objectives and seeks an optimal quantitative solution (e.g. LP, simulation). Soft OR treats objectives as contested and uncertain, works with multiple stakeholder perspectives, and aims for shared understanding, learning and accommodation rather than a single optimum.

3. In the GORS assessment context, what does the timed problem-structuring test typically require a candidate to do?

   Read a written commission/scenario, structure the problem under time pressure, and produce a clear, logical, feasible analytical approach (objectives, scope, methods, data) that can be explained and defended, usually in writing and sometimes verbally.

4. Name the three core assessment criteria used to judge a structured analytical approach in the GORS test.

   Clarity (the approach is easy to follow and well communicated), Logic (the reasoning connects question, analysis and conclusions soundly), and Feasibility (the approach is realistic given time, data and resource constraints).

5. Why is 'demonstrating structured thinking' valued more than reaching a 'right answer' in the GORS timed test?

   Because the scenarios are deliberately open-ended with no single correct answer; assessors look for a logical, transparent thought process that breaks the problem down systematically, shows awareness of assumptions and trade-offs, and could be defended to a client.

6. What is the difference between a problem's 'presenting question' and the 'real question behind a commission'?

   The presenting question is what the client literally asks; the real question is the underlying decision or need driving the request. Clarifying the real question prevents solving the wrong problem and ensures analysis is decision-relevant.

7. List good clarifying questions to ask when receiving an analytical commission.

   Who is the client/decision-maker? What decision will this inform? Why now? What does success look like? What is in and out of scope? What constraints (time, budget, data, legal) apply? What has already been tried? When is it needed and in what form?

8. Define 'objectives' in the context of structuring an analytical problem.

   Objectives are the outcomes the client wants to achieve or the criteria against which options will be judged (e.g. reduce cost, increase access, improve safety). They give direction and provide the basis for evaluating options.

9. Define 'constraints' when scoping an analytical task.

   Constraints are the fixed limits or boundaries the solution must respect — e.g. legal/regulatory requirements, fixed budget, deadlines, available data, political or ethical limits, or resources — that restrict the feasible set of options.

10. What is the difference between an assumption and a constraint in problem structuring?

    A constraint is a genuine, externally imposed limit that cannot be crossed; an assumption is something taken to be true to make progress in the absence of certainty. Assumptions should be made explicit and tested; constraints bound the solution space.

11. What are 'success criteria' and why must they be defined early?

    Success criteria are the measurable or observable conditions that define whether the analysis (or the resulting decision) has achieved its aim. Defining them early ensures the analysis stays focused, makes objectives testable, and provides a basis for evaluating options and impact.

12. What does 'defining scope' involve, and why is a scope statement important?

    Scope defines what the analysis will and will not cover — boundaries of the system, populations, time horizon, geographies and questions addressed. A clear scope manages client expectations, prevents scope creep, and keeps the work feasible within time and resources.

13. Distinguish an 'analytical question' from a 'hypothesis'.

    An analytical question frames what you need to find out (e.g. 'What drives waiting times?'); a hypothesis is a testable, falsifiable proposed answer (e.g. 'Waiting times rise mainly due to staff shortages'). Hypotheses guide what evidence/data to collect.

14. What makes a good hypothesis in structured analysis?

    It is specific, testable/falsifiable with available evidence, directly relevant to the decision, and stated clearly enough that data can confirm or refute it. Good practice generates several competing hypotheses to avoid confirmation bias.

15. Who originated Soft Systems Methodology (SSM) and what problem did it address?

    Peter Checkland (and colleagues at Lancaster University) developed SSM in the 1970s–80s to tackle messy, ill-structured 'soft' problem situations in human activity systems where hard systems engineering failed because objectives were not agreed.

16. What is the classic seven-stage cycle of Soft Systems Methodology (SSM)?

    1) Enter the problem situation; 2) Express the problem situation (rich picture); 3) Formulate root definitions of relevant systems; 4) Build conceptual models; 5) Compare models with the real world; 6) Identify feasible and desirable changes; 7) Take action to improve the situation.

17. In SSM, what is a 'rich picture' and what is its purpose?

    A rich picture is a free-form cartoon-style diagram capturing the people, structures, relationships, conflicts, concerns and processes in a messy situation. It surfaces multiple perspectives and emotional/political content without prematurely imposing structure.

18. In SSM, what does the mnemonic CATWOE stand for?

    Customers (beneficiaries/victims), Actors (who carry out the activities), Transformation process (input → output), Weltanschauung (worldview making the transformation meaningful), Owner (who can stop it), and Environmental constraints. It is used to build root definitions.

19. In SSM, what is a 'root definition'?

    A concise statement defining what a relevant purposeful system is and does — capturing the core transformation and the worldview behind it (built using CATWOE). It anchors the subsequent conceptual model of activities.

See more Problem Structuring and Soft OR Methods flashcards →

Planning Problem Structuring and Soft OR Methods for Government Operational Research Service (GORS) Assessment

Problem Structuring and Soft OR Methods (Government Operational Research Service (GORS) Assessment) FAQ