Problem structuring methods

Source: Wikipedia, the free encyclopedia.
detail of a Tree of Knowledge after Diderot & d'Alembert's Encyclopédie, by Chrétien Frédéric Guillaume Roth
Information mapping
Topics and fields
Node–link approaches
See also

Problem structuring methods (PSMs) are a group of techniques used to model or to map the nature or structure of a situation or state of affairs that some people want to change.[1] PSMs are usually used by a group of people in collaboration (rather than by a solitary individual) to create a consensus about, or at least to facilitate negotiations about, what needs to change.[2] Some widely adopted PSMs[1] include

Unlike some problem solving methods that assume that all the relevant issues and constraints and goals that constitute the problem are defined in advance or are uncontroversial, PSMs assume that there is no single uncontested representation of what constitutes the problem.[6]

PSMs are mostly used with groups of people, but PSMs have also influenced the

counseling of individuals.[7]

History

The term "problem structuring methods" as a label for these techniques began to be used in the 1980s in the field of operations research,[8] especially after the publication of the book Rational Analysis for a Problematic World: Problem Structuring Methods for Complexity, Uncertainty and Conflict.[9] Some of the methods that came to be called PSMs had been in use since the 1960s.[2]

Thinkers who later came to be recognized as significant early contributors to the theory and practice of PSMs include:[10]

Types of situations that call for PSMs

See also: Cynefin framework § Domains

In discussions of problem structuring methods, it is common to distinguish between two different types of situations that could be considered to be problems.[17] Rittel and Webber's distinction between tame problems and wicked problems (Rittel & Webber 1973) is a well known example of such types.[17] The following table lists similar (but not exactly equivalent) distinctions made by a number of thinkers between two types of "problem" situations, which can be seen as a continuum between a left and right extreme:[18]

Different types of situations, and thinkers who named them[18]
Thinker Left extreme Right extreme
Rittel & Webber Tame problem Wicked problem
Herbert A. Simon Programmed decision Non-programmed decision
Russell L. Ackoff Puzzle / Problem Mess
Jerome Ravetz Technical problem Practical problem
Ronald Heifetz Technical challenge Adaptive challenge
Peter Checkland Hard systems Soft systems
Donald Schön The high ground The swamp
Barry Johnson Problems to solve Polarities to manage

Tame problems (or puzzles or technical challenges) have relatively precise, straightforward formulations that are often amenable to solution with some predetermined technical fix or algorithm. It is clear when these situations have changed in such a way that the problem can be called solved.

Wicked problems (or messes or adaptive challenges) have multiple interacting issues with multiple

stopping rule
and no ultimate test of a solution.

PSMs were developed for situations that tend toward the wicked or "soft" side, when methods are needed that assist

argumentation about, or that generate mutual understanding of multiple perspectives on, a complex situation.[17]
Other problem solving methods are better suited to situations toward the tame or "hard" side where a reliable and optimal solution is needed to a problem that can be clearly and uncontroversially defined.

Characteristics

Problem structuring methods constitute a family of approaches that have differing purposes and techniques, and many of them had been developed independently before people began to notice their family resemblance.[17] Several scholars have noted the common and divergent characteristics among PSMs.

Eden and Ackermann identified four characteristics that problem structuring methods have in common:[19]

  1. The methods focus on creating "a model that is populated with data that is specific to the problem situation". These cause–effect models can be analyzed (albeit in different ways by different methods), and the models are intended to facilitate conversation and negotiation between the participants.
  2. The methods seek to increase the overall productivity of group processes. Productivity includes creating better agreements that are more likely to be implemented, and realizing (to the extent possible in the given situation) ideals such as communicative rationality and procedural justice.
  3. The methods emphasize that the
    facilitation
    of effective group processes requires some attention to, and open conversation about, power and politics within and between organizations. Power and politics can become especially important when major change is being proposed.
  4. The methods provide techniques and skills for facilitation of group processes, and they appreciate that such techniques and skills are essential for effective
    participative decision-making. People who use PSMs must pay attention to what group facilitators
    call process skills (guiding interactions between people through nonlinear applications of the methods) and content skills (helping people build sufficiently comprehensive models of the given situation).

Rosenhead provided another list of common characteristics of PSMs, formulated in a more prescriptive style:[20]

An early literature review of problem structuring proposed grouping the texts reviewed into "four streams of thought" that describe some major differences between methods:[21]

  • the checklist stream, which is step-by-step technical problem solving (not problem structuring as it came to be defined in PSMs, so this stream does not apply to PSMs),
  • the definition stream, which is primarily modeling of relationships between variables, as described by Ackoff and others,
  • the science research stream which emphasizes doing field research and gathering quantitative data, and
  • the people stream, which "regards the definition of problems as a function of people's perceptions" as described by Checkland, Eden, and others.

Compared to large group methods

Mingers and Rosenhead have noted that there are similarities and differences between PSMs and large group methods such as Future Search,

Open Space Technology, and others.[22] PSMs and large group methods both bring people together to talk about, and to share different perspectives on, a situation or state of affairs that some people want to change. However, PSMs always focus on creating a sufficiently rigorous conceptual model or cognitive map of the situation, whereas large group methods do not necessarily emphasize modeling, and PSMs are not necessarily used with large groups of people.[22]

Compared to participatory rural appraisal

There is significant overlap or shared characteristics between PSMs and some of the techniques used in participatory rural appraisal (PRA). Mingers and Rosenhead pointed out that in situations where people have low literacy, the nonliterate (oral and visual) techniques developed in PRA would be a necessary complement to PSMs, and the approaches to modeling in PSMs could be (and have been) used by practitioners of PRA.[23]

Applications

In 2004, Mingers and Rosenhead published a literature review of papers that had been published in

business strategy and information system strategy, planning livestock management in Nepal, regional planning in South Africa, modeling hospital outpatient services, and eliciting knowledge about pesticides.[24]

Technology and software

PSMs are a general

shared display of the models that participants are developing. The shared display could be flip charts, a large whiteboard, Post-it notes on the meeting room walls, and/or a personal computer connected to a video projector.[26] After PSMs have been used in a group work session, it is normal for a record of the session's display to be shared with participants and with other relevant people.[26]

Software programs for supporting problem structuring include Banxia Decision Explorer and Group Explorer,

dialogue mapping and related methods;[28] a similar program is called Wisdom.[29] Such software can serve a variety of functions, such as simple technical assistance to the group facilitator during a single event, or more long-term online group decision support systems
.

Some practitioners prefer not to use computers during group work sessions because of the effect they have on group dynamics, but such use of computers is standard in some PSMs such as SODA[27] and dialogue mapping,[28] in which computer display of models or maps is intended to guide conversation in the most efficient way.[26]

In some situations additional software that is not used only for PSMs may be incorporated into the problem structuring process; examples include spreadsheet modeling, system dynamics software[30] or geographic information systems.[31] Some practitioners, who have focused on building system dynamics simulation models with groups of people, have called their work group model building (GMB) and have concluded "that GMB is another PSM".[32] GMB has also been used in combination with SODA.[33]

See also

Notes

  1. ^ a b Rosenhead 2013, p. 1162
  2. ^ a b Rosenhead 1996, p. 117
  3. ^ Checkland & Poulter 2006
  4. ^ Friend & Hickling 2005
  5. ^ Reynolds & Holwell 2010, pp. 135–190
  6. ^ Rosenhead 1996, p. 118
  7. ^ For example: Chatjoulis & Humphreys 2007
  8. ^ For examples, see: Norris 1985, p. 871; Dunn 1988, p. 720; Landis 1988, pp. 117–119. William N. Dunn wrote in 1988: "In the absence of appropriate problem-structuring methods, how can we expect to formulate problems that encompass the proper elements, for example, the proper policy objectives, alternatives, and expected outcomes? Given a particular problem formulation, how do we know whether all important elements have been included in the set? In short, how do we know when we have formulated an approximate solution to the right problem, as distinguished from an exact solution to the wrong problem?" (Dunn 1988, p. 720)
  9. ^ Rosenhead 1989
  10. ^ Rosenhead 2013, p. 1164
  11. ^ Rittel & Webber 1973
  12. ^ For example: Ackoff 1974, Ackoff 1979
  13. ^ Checkland 1975, Checkland 1981
  14. ^ For example: Eden & Sims 1979, Eden 1982, Eden & Ackermann 2006
  15. ^ For example: Jackson & Keys 1984, Flood & Jackson 1991
  16. ^ For example: Rosenhead 1989, Mingers & Rosenhead 2001
  17. ^ a b c d Rosenhead 2013, pp. 1163–1164
  18. ^ a b This table is adapted from: Culmsee & Awati 2013, p. 108
  19. ^ Eden & Ackermann 2006
  20. ^ Rosenhead 2013, pp. 1164–1165
  21. ^ Woolley & Pidd 1981, pp. 203–204
  22. ^ a b Mingers & Rosenhead 2004, p. 548; examples of large group methods can be found in Bunker & Alban 2006
  23. ^ Mingers & Rosenhead 2004, pp. 548–549
  24. ^ a b Mingers & Rosenhead 2004, pp. 541–542
  25. ^ Rosenhead 2013, p. 1167
  26. ^ a b c d Rosenhead 2013, p. 1170
  27. ^ a b Ackermann & Eden 2011; Rosenhead 2013, p. 1169
  28. ^ a b Conklin 2006; Culmsee & Awati 2013; Culmsee & Awati 2014
  29. ^ Mackenzie et al. 2006
  30. ^ For example: Rodriguez-Ulloa & Paucar-Caceres 2005; Hovmand 2014, p. 83
  31. ^ For example: Pfeiffer et al. 2008; Ferretti 2016
  32. ^ Andersen et al. 2007, p. 691
  33. ^ Herrera et al. 2016

References

  • Ackermann, Fran; Eden, Colin (2011) [1998]. Making strategy: mapping out strategic success (2nd ed.). London; Thousand Oaks, CA:
    OCLC 754163654
    .
  • Mackenzie, Adrian; Pidd, Michael; Rooksby, John; Sommerville, Ian; Warren, Ian; Westcombe, Mark (April 2006). "'Wisdom', decision support and paradigms of decision making".
    doi:10.1016/j.ejor.2004.07.041
    .

Further reading

Retrieved from "https://en.wikipedia.org/w/index.php?title=Problem_structuring_methods&oldid=1208834528"