Systems Thinking:Difficulties and messes

By -

5.1 Introduction

Reductionist approaches to problem solving take wholes apart and examine the parts to see how they work to gain an understanding of the whole. This approach can work with certain types of problem where it is possible to isolate them to a part of the whole and to then fix it. For example, I might well be able to identify a hard disk failure on my personal computer as the cause of it not working. Fixing the hard disk may well fix the problem and get me a fully functioning computer once again. Unfortunately, not all problems are amenable to this treatment and in many situations it is better to think of the situation as a 'mess' to be explored than a problem to be solved.

In this chapter we will consider the principal ideas behind systems thinking and contrast them with the reductionist approaches of traditional analysis. The aim of this chapter is to build an understanding of systems theory and systems thinking to provide a foundation for the soft systems methodology (SSM) introduced in chapter 6.

5.2 Difficulties and messes

Mental models affect how we see the world. How we view the world is an important factor in what action we take. If we view the situation non-problematically as a difficulty to be resolved then the situation is perceived as being bounded (figure 5.1).Developing Web Information Systems-0025

problem is and agreement is difficult to reach.

With a mess, the 'problem' cannot be disentangled from its context and the priorities are unclear and need to be questioned. With a difficulty the situation is bounded and the boundaries are taken as given. With a mess the situation is unbounded and the boundaries of the problem need to be explored and defined jointly with the process of defining what the problem is.

Real-world situations are not in themselves either difficulties or messes. The degree of difficultness or messiness is an attribute of the relationship between the observer and the situation. What is a local difficulty for one can be a mess with wide implications for another. It is more appropriate to think of problem situations as being perceived by a would-be problem-solver as lying on a spectrum delimited by a difficulty at one end and a mess at the other. The tendency of the system thinker will be to see messes and interconnectedness as well as difficulties and localizable problems. The art of judgment is in knowing where to position a particular intervention on the spectrum of difficulties and messes.

Comments

Post a Comment

Popular posts from this blog

The Conversion Cycle:The Traditional Manufacturing Environment

By -
Image
The Traditional Manufacturing Environment The conversion cycle consists of both physical and information activities related to manufacturing products for sale. The context-level data flow diagram (DFD) in Figure 7-1 illustrates the central role of the conversion cycle and its interactions with other business cycles. Production is triggered by customer orders from the revenue cycle and/or by sales forecasts from marketing. These inputs are used to set a production target and prepare a production plan, which drives production activities. Purchase requisitions for the raw materials needed to meet production objectives are sent to the purchases procedures (expenditure cycle), which prepares purchase orders for vendors. Labor used in production is transmitted to the payroll system (expenditure cycle) for payroll processing. Manufacturing costs associated with intermediate work-in-process and finished goods (FG) are sent to the general ledger (GL) and financial reporting system. Dependin
Read more

The Revenue Cycle:Manual Systems

By -
Image
Manual Systems The purpose of this section is to support the system concepts presented in the previous section with models depicting people, organizational units, and physical documents and files. This section should help you envision the segregation of duties and independent verifications, which are essential to effective internal control regardless of the technology in place. In addition, we highlight inefficiencies intrinsic to manual systems, which gave rise to modern systems using improved technologies. SALES ORDER PROCESSING The system flowchart in Figure 4-12 shows the procedures and the documents typical to a manual sales order system. In manual systems, maintaining physical files of source documents is critical to the audit trail. As we walk through the flowchart, notice that in each department, after completion of the assigned task, one or more documents are filed as evidence that the task was completed. Sales Department The sales process begins with a customer cont
Read more

HIPO (hierarchy plus input-process-output)

By -
Image
HIPO (hierarchy plus input-process-output) 64.1 Purpose The HIPO (Hierarchy plus Input-Process-Output) technique is a tool for planning and/or documenting a computer program. A HIPO model consists of a hierarchy chart that graphically represents the program’s control structure and a set of IPO (Input-Process-Output) charts that describe the inputs to, the outputs from, and the functions (or processes) performed by each module on the hierarchy chart. 64.2 Strengths, weaknesses, and limitations Using the HIPO technique, designers can evaluate and refine a program’s design, and correct flaws prior to implementation. Given the graphic nature of HIPO, users and managers can easily follow a program’s structure. The hierarchy chart serves as a useful planning and visualization document for managing the program development process. The IPO charts define for the programmer each module’s inputs, outputs, and algorithms. In theory, HIPO provides valuable long-term documentation. However
Read more