Inspired by the many comments on previous posts and their deferring visions (myself included) about systems, systems thinking and systems theory, I thought it was time for a post about these subjects. For now I will focus on systems thinking. We talked about whether organizations are systems or not, what systems are and are not, and if it helps to compare organizations with systems. Very precarious matter, it seemed. To me, it is precarious as well. To compare two things with each other is always tricky. Do we share the same vocabulary? Are we referring to the same? Are we oversimplifying the subject matter? Talking about organizations makes it even more trickier, because no organization is the same. The forms of organizations can differ, let alone the people who make up the conversation of organization. Think Wittgenstein here…
Like many people, I like to understand certain phenomena. If we do not understand, we tend to compare these phenomena with ones we do understand, or think we understand. That comparison should help us with understanding the more complex phenomena. While this can be a strategy that helps us, it can distract us from the important aspects of these phenomena as well. This is always a pitfall when comparing apples and oranges. However, systems thinking is not just an apple or an orange, it can make sense to make use of systems thinking to try to understand tiny parts of a larger unit, in relation to other parts.
Can’t we think of organizations as systems at all? It depends on the vocabulary we use and have in common. I think it can help to deduct to some smaller pieces present in organizations. Carter McNamara shares his view, and it contributes to my understanding. His statement on what a system is, shows the complexity of a system:
A pile of sand is not a system. If one removes a sand particle, you’ve still got a pile of sand. However, a functioning car is a system. Remove the carburetor and you’ve no longer got a working car.
The statement above is a somewhat simple example, that illustrates the complexity of a system. When you remove a lot of particles, the pile will collapse or even disappear. Translated to an organization, it becomes apparent what the problem with the comparison between systems and organizations is. Like with systems, every particle in an organization plays a role. It influences other parts. Maybe some particles can easily be removed, because they have little or no influence on other parts. The organization still works as expected, but we call it more efficient. Some particles are more difficult to replace, it has more influence on other parts and the organization will change as a result. Unlike with systems, there are no two particles alike when humans are involved. Therefore, the statement above doesn’t help me that much. The comparison is still a problem. What helps, is the statement of the same Carter McNamera when he explains why it is important to look at organizations as systems.
The effect of this systems theory in management is that writers, educators, consultants, etc. are helping managers to look at organizations from a broader perspective. Systems theory has brought a new perspective for managers to interpret patterns and events in their organizations. In the past, managers typically took one part and focused on that. Then they moved all attention to another part. The problem was that an organization could, e.g., have wonderful departments that operate well by themselves but don’t integrate well together. Consequently, the organization suffers as a whole.
This is helpful. Organizations are not systems, but it helps to look at an organization as if it were a system. Changing something in the organization always has influence on other areas in the organization. The comparison refers to complexity, both organizations as well as systems are complex. It can help to deal with the complexity of an organization. But then again, by looking at it as a system you should not make it a system, the processes that occur in organizations are not comparable to systems at all.