Systems Thinking - Sailing through Wicked Problems on Complex Seas

Systems thinking helps us not to be so dependent upon linear thinking when addressing complex challenges. This sometimes means skipping ahead then coming back which is the course I am taking in completing the STW/STiA Systems Thinking Certification course, skipping over the segment next in line. 

The final two segments then, prior to certification, introduce us first to different dynamic systems and then to different soft systems methods. Both were referenced before as part of Michael C. Jackson’s System of Systems Methodology (SOSM) framework in the post Enabling a Better Tomorrow through New Community Paradigms via Systems Thinking. Jackson, as he explains in Critical Systems Thinking: Beyond the Fragments sought to, "relate developments in systems thinking to an increased sophistication in coming to terms with extreme complexity and an increased awareness of difficulties posed by the divergent values and interests of stakeholders."

Under Jackson’s classification, both dynamic systems and soft systems can be used to address simple, which we will skip over, to complex situations in which there are a large number of elements and subsystems with loosely structured interactions which can be non-linear. The difference is that soft systems are used when working with pluralist stakeholders meaning basic interests are compatible though participants do not share the same values and beliefs while dynamic systems are used when the participants are unitary in outlook, meaning the stakeholders all have similar values, perspectives and interests, at least on the relevant issue. 

Soft Systems Methods are generally employed for purposes of exploration and understanding, to obtain a compatible vision. Dynamic Systems Methods are typically employed for improving goal seeking and viability, once a compatible or finally determined upon vision has been obtained. Both could and should not only be used with systems of direct participatory democracy, they should usually be used in tandem.  This would be in keeping with an often cited concept that, “all hard systems are embedded in soft systems”.

As Dr. Mike Yearworth explains though in Hard Systems and Soft Systems this statement does not fully capture the differences between the two systemic approaches. It is an epistemic shift, as described by Peter Checkland and Susan Holwell that defines the differences between hard and soft systems perspectives. 

Soft systems treat the definition as a question of epistemology, as in what can we know or find out about the world? While the hard or dynamic system takes a more ontological approach. Yearworth provides a chart with bullets on the differences between the two approaches. 

There are many concepts and theories that embrace a Soft Systems perspective and are useful for exploratory purposes to attain a greater understanding and potentially draft a compatible approach to the wicked problem.  Appreciative Inquiry, Idealized Design, and Soft Systems Methodology are three offered in the segment because they each have a well defined approach for their use. These will be examined more closely in the future.

System Dynamics and Viable Systems Model are two dynamic systems featured in this segment because they also have a well defined method for using them. Dynamic systems and in particular Systems Dynamics is where the process can get all the more concrete. Systems Dynamics, a field also related to Cybernetics, goes beyond Systems Thinking which can be seen as a relatively qualitative modeling system. System Dynamics, in contrast, is a rigorous methodology employing the development and use of formal computer models based on three components which collectively define it.

1. Apply the accepted system dynamics theory of structure;
2. Are constructed following the scientific method; and
3. Use best practice tools and techniques.

The most adept advocate for Systems Dynamics is its creator, J. W. Forrester, Professor Emeritus of Management System Dynamics at MIT who upended the conventional thinking in management and redefined what growth means through articles such as System Dynamics, Systems Thinking, and Soft OR and Learning through System Dynamics as Preparation for the 21st Century. Professor Forrester has been deemed The Prophet of Unintended Consequences. 

Another dynamic system, Viable Systems Model (VSM), developed by Stafford Beer, could be considered more abstract. 
"It is an organizational representation of the elements and interactions considered essential for any system to be viable or autonomous".  It is  therefore not a method or process but a model of:

“A viable system being one that is organized and operates in a manner such as to survive in its changing environment. Adaptability is one of the prime features of systems that survive. (Adapted from Wikipedia)”

Beer, himself, narrates this video explanation on the Basis for the Viable Systems Model from Javier Livas - YouTube page.

A primary foundation for the Viable Systems Model is Ross Ashby's Law of Requisite Variety, or as is sometimes paraphrased," only complexity absorbs complexity”. 

"The Law has many forms, but it is very simple and common sensical: a model system or controller can only model or control something to the extent that it has sufficient internal variety to represent it."

Arguably #3  of Clemson’s Systems Laws considered valid for all complex systems (Clemson seems to have added more laws. Kauffman also came up with a set of rules of thumb for complex systems as viewed by systems thinking. My suggested rules for community complexity are here.) 

This could then be applied to Beer's environment, process and management as explained in the video, which would suggest that enhanced participation by community members would make the process more viable and sustainable from a community point of view.

The system though only has to survive, it does not have to reach any predetermined goals that we desire or that we may expect from the system. An entrenched city hall, often mentioned on these pages, can then be a viable system highly resistant, internally, to attempts to change it, externally. 

The challenge and the need for some type of virtual systemic inquiry are that complexity is inherent in all phases that should be undertaken by communities addressing a wicked problem. Not only the phases are complex, the transitions are complex. To simply understand a wicked problem is a complex challenge in itself as demonstrated by this Ted Talk by Gavin Schmidt, The Emergent Patterns of Climate Change. The next phase is understanding and developing an agreed upon approach to address the wicked problem. The final stage is implementing that program and ensuring that it creates the desired results.

If it does not then it means moving back to a previous phase. Perhaps the vision created in the second phase was not as unified or compatible as thought. Perhaps it was realized that a significant minority did not support the plan but it was not appreciated how important they would be in implementation. It could also be that the wicked problem system was not as well understood as it needed to be to come up with a viable strategy that was not only devised as compatible through collaborative efforts but could be implemented through collaborative actions. One question then is how viable over an extended period would a winner take all strategy be under such an approach?

The bigger question is how the community manages the complexity that arises in addressing the wicked problem from its own actions when complexity is seen as a massive problem in its own right. Systems thinking provides different means of navigation, with different ones better suited to the task at different times but these means often tend towards the abstract and more concrete means are needed to sail these seas. What is needed are more concrete tools of collaboration, compasses and sextants applied to systemic inquiry and these days it needs to include the virtual sea of the World Wide Web. Looking to the development of such a system is the next (previously skipped over) segment.

More Thinking on Mastering Systems Practice, Dealing with Messes

In the last post, the idea of what Russell Ackoff called “messes” as contrasted with difficulties was introduced. The course promised more on Ackoff in week six but additional background was provided in that NCP post. More will also be offered here, including a paper in which the term “messes” is used, Systems, Messes and Interactive Planning - Modern Times Workplace.

The course quoted Ackoff regards to messes:

Managers are not confronted with problems that are independent of each other, but with dynamic situations that consists of complex systems of changing problems that interact with each other. I call such situations messes. Problems are abstractions extracted from messes by analysis; they are to messes as atoms are to tables and charts … Managers do not solve problems, they manage messes.

Russell Ackoff (1979, s. 93)

It has to be admitted that this is the first time being exposed to Ackoff’s idea of messes being more familiar with the concept of wicked problems. This raises the question though, are "messes" qualitatively different from"wicked problems”?

Judith A. Curry, American climatologist and former chair of the School of Earth and Atmospheric Sciences at the Georgia Institute of Technology, wrote about the differences between messes and wicked problems from which I borrow heavily here.

Russell L. Ackoff wrote about complex problems as messes:

“Every problem interacts with other problems and is, therefore, part of a set of interrelated problems, a system of problems…. I choose to call such a system a mess.”

Robert Horn extended the concept:

“a Social Mess is a set of interrelated problems and other messes. Complexity—systems of systems—is among the factors that makes Social Messes so resistant to analysis and, more importantly, to resolution.”
So a system of problems within a complex system of systems?

“Wicked problem” is a phrase originally used in social planning to describe a problem that is difficult or impossible to solve because of incomplete, contradictory, and changing requirements that are often difficult to recognize. Moreover, because of complex interdependencies, the effort to solve one aspect of a wicked problem may reveal or create other problems.

Curry goes on to cite the executive summary of New Tools for Resolving Complex Problems, subtitled Mess Mapping and Resolution Mapping Processes.

Wicked Problems (equivalently, Social Messes) are seemingly intractable problems. They are composed of inter-related dilemmas, issues, and other problems at multiple levels society, economy, and governance. These interconnections—systems of systems—make Wicked Problems so resilient to analysis and to resolution.

Messes then seem to be Frankenstein problems while wicked problems are Godzilla. We will stick with just the course’s messes and difficulties from here on with the understanding we may need a bigger army.

The course seems to be breaking down its systematic approach by what I’ll call embedded bifurcations, difficulties with messes, emotional reactions with rational reactions, and systemic thinking with systematic thinking as part of understanding the “perceived complexity within situations”. The first dealt with being differences between difficulties and messes.

I am going to jump though and first consider problems, situations and systems. As suggested in the last post there are two types of problems, difficulties and messes. Problems, according to the course, are taken up by, not given to, decision makers and problems are extracted from unstructured states of confusion or complex situations.

These are my interpretations, so its necessary to take the course to see if one comes to the same conclusions. Problems, it seems are undesired situations. Situations are not systems but interactions between us and systems. I don’t see unstructured states of confusion and complex situations as being equivalent but a complex situation is different from a complex system. Can a complex situation, on its own be adaptive?

Back to the more basic and tangible ideas of difficulties and messes. Difficulties refer to simpler, more limited types of situations. A difficulty is fairly clear cut, easy to put a label on it and to explain to someone else what is the problem. With difficulty, the overall context and purpose of the activity can be taken for granted, determining how it can best be done is a relatively simple matter. A difficulty can be disentangled from the broader context of work and addressed in a more or less discrete matter. What a solution will look like is roughly known with a difficulty. Finally, one knows enough or knows what is needed to be known to be able to tackle a difficulty.

Messes aren’t seen as merely being ‘bigger’ than difficulties. They have a number of features that make them qualitatively different. A mess is harder to pin down or even to say what is the actual problem. Having no sure solutions, it usually doesn’t make much sense to talk about ‘an answer’ with a mess. It becomes more a matter of coping as best one can with the circumstances. The aspects of a mess are beyond one’s direct control and what factors are relevant to the situation and what aren’t isn't easily known. A mess is fuzzy. Because its different elements are closely tied to other areas of activity it’s hard to say who and what is involved in the problem and who and what isn’t. With a mess, one never knows enough and is uncertain even what is needed to be known.

Other attributes that distinguish between difficulties and messes concern their scale and the uncertainty associated with them.

The scale of the situation determines the ways in which messes tend to be ‘larger’ and have more serious implications than difficulties. More people are likely to be involved in a mess. Messes usually have a longer time-scale. They are more complicated making them more difficult to tackle. A mess calls into question how much weight to give to different considerations, assumptions and priorities as well as whether particular goals are realistic or not.

The second group of key features comes under the general heading of uncertainty. There is much more about which one is simply unsure with messes. Uncertainty that is inherent in the situation itself, most notably irreducible uncertainty, as suggested by Donella Meadows, or essentially complex stochastic output.

The next level idea best capturing the difference between difficulties and messes is the idea that difficulties are bounded while messes are unbounded in terms of both scale and uncertainty.

A bounded situation implies that it is fairly limited and that one roughly knows where are those limits. Although no single characteristic provides an essential criterion, to describe a situation as messy, rather than just a difficulty, it implies that in some important respects it is unbounded.

An unbounded situation is more extensive, though just how extensive can be hard to determine so it becomes a mess. Knowing that a messy situation may in some important respects be unbounded is useful. It is though ambiguous on an important point.

Elements of rational and emotional complexity must be considered, for practical purposes, as it is essential to remember that both are important in comprehending a messy situation.

What may be hard to pin down is whether this quality of being unbounded is a characteristic of a person’s experience of a particular situation, or is actually of the nature of the situation itself? Is a messy situation one that someone for their own particular reasons can’t see how to disentangle from everything else? Does it only appear to them to be unbounded or is it actually the situation that is unbounded meaning that the circumstances are such that the situation really has very extensive ramifications.

One of the properties of problems with which helpers have found it quite hard to grapple is the extent to which all problems are personal; different persons see different problems in what other people would take to be the same situation. This is an important point in our argument, and is fairly well accepted in everyday ‘common sense’. This point does not seem to raise much difficulty when it is expressed theoretically, but it is often rather more difficult to bear it in mind and act upon in practice.

In summary, difficulties and messes are general terms without clear-cut or categorical distinctions. Instead, they are on a continuum, with most problems lying somewhere in between.

Learning to Apply a Systems Practice to the Wicked Problem of Homelessness

This is the beginning of another online course sponsored by Acumen and another course in collaboration with Jo Foraker with whom I worked with on the Modeling the Last Mile to Feed the Homeless series. In that course, the focus was on financial modeling but systems thinking modeling was always included underneath near the surface. Again, only a flavor of the course is going to be provided here and not the course itself. Instead, the focus, as before, will be more on how the course connects with new community paradigms.

This course is more directly on Systems Practice and is being taught by Rob Ricigliano of Omidyar Group’s Systems & Complexity Team. It appears that it will seek a more pragmatic or on-the-ground application of systems thinking than did the previously taken systems thinking certification course. One new aspect will be how to launch a team. This course will also be using the often featured Kumu relational mapping tool. Here is a perspective on Kumu by Rob Ricigliano.

The course focuses on solving what it calls groundhog day, whack-a-mole and opposite day problems, a little imagination will paint a picture. Another more operationally viable term is "wicked problem". The trouble for those trying to communicate this reality to others is that this reality can be confusing, frustrating and messy. The course sees systems thinking as a necessary mindset in addressing this reality by providing clarity and insights into points of leverage within such systems at which the greatest impact with modest force is possible. It makes it possible to enhance an organization’s adaptability to changing environments. Making it more aware of causal ripple effects, those instances of cause and effect which are separate in time and space from the more ostensibly obvious events within our immediate reality. 

Homelessness is seen as a wicked problem, a complex problem involving large scale system inputs and outcomes having very close, personal and detrimental impact on those afflicted by it. It will arguably require then a wide perspective to find viable solutions. 

In particular with the issue of homelessness in which communities have spent a large amount of money on shelters in many large cities yet did not reduce the overall number of people living on the streets within those cities. 

The course explores why. With the homeless shelter question, the suggested answer is “Shelters were never meant to provide a path to sustainable living.” Beyond that, no one program can address all of the underlying challenges facing our communities. They are all interconnected and interwoven. It is a complex perspective on reality as opposed to an imposed complicated top-down perspective. 

One positive example cited by the course and in the past by this blog, is the Calhoun County, Michigan study which used systems thinking to address homelessness. They looked at the “whole system” under which the incentive for funders and providers had been to provide quick fixes, addressing the immediate problem, rather than sustained change. They used systems thinking to determine where they could effectively intervene with higher level approaches such as housing first. This worked even when unemployment in the area was rising.

1. Setting goals
2. Good Systems Analysis
3. Finding Opportunities for Leverage
4. Preparing to Learn and Adapt Effectively

The course considers how to do a systems analysis through a dynamic systems map of key forces affecting the system under study. How to identify opportunities for impact or leverage points within that system to create the desired change. How do we get started on the process of learning and adapting so that if we manage to do that very well in the context of the complex system (meaning constantly shifting) we are working in we are able to adapt?

1. Mindset for how the world works and how to create change.
2. A set of tools and processes as to how to actually design and implement actions for change.

Rob then goes into what they mean by a system or what makes a system, differentiating it from more tangible physical systems such as an automobile or the healthcare system. Complex social systems produce results or consequences such as homelessness or other social ills to use his examples. This type of system is made up of complex forces that affect each other and more importantly for one’s efforts the issue with which you are concerned. For example, the “things” that produce homelessness are likely diverse but not isolated, they are interrelated in a manner that I would deem organic and intrinsic. These relationships between the things or factors contributing to homelessness can interact in unpredictable ways. 

So a system has discrete and diverse components or elements that are interdependent and interact in complex ways that dynamically change over time. This makes predictability more difficult, not impossible but the ability is far more constrained as one needs to constantly reassess one's systems analysis and the time frame for an accurate prediction can be shortened. 

The Omidyar Group’s take on systems thinking consists of three key components. It is a mindset. A way of thinking about how the world works and how to work with that messy world to promote desired outcomes. It is a set of tools to do analysis and develop a strategy. It is a particular set of processes which demands collective intelligence and sense-making resulting in collective action. This requires certain specific processes, such as participatory deliberations and dialogue.

The course recognizes that there are certain problems that are not solvable by directly addressing the apparent symptoms of the problem. With homelessness, it was the notion that we build shelters but that didn't actually solve the problem. It may have gotten certain people off of the streets but they were replaced and increased by more people. It can be necessary to look at the entire system to determine what it is about the system that is producing that and other negative outcomes. The conundrum is that certain acute challenges cannot be ignored until a complete and permanent solution to the chronic problem is found.

The feeding of the unsheltered, isolated homeless (even in homeless camps there is still isolation) is one such challenge. Those that can’t find occupancy in the shelters can also find themselves isolated from the community's food systems.  The direct approach to the problem, getting food and taking it to the camps is already known to be a tremendous logistical challenge. The question is how to create a system, an enterprise that works most effectively and efficiently in the existing larger systems and that can also, hopefully, begin to change that larger system to not only stop whatever activities it is doing to create the problems but to also directly work on the larger system issues to resolve them.

1. The nature of the environment one is working in.
2. The nature of the goal you have set for yourself.
3. One’s ability to implement this type of approach.

Rob then goes into three criteria for determining whether a systems approach should be applied. First is the nature of the environment one is working dynamic and constantly changing? Have supposedly obvious approaches been tried before and failed? Can change be overwhelming, not just for oneself but especially for those one is trying to assist? Even solutions that may work in one case don’t work in another. 

The second is the nature of the goal that one is striving to accomplish. This one is more problematic. Rob speaks of relief efforts to feed a specific group of people for a specific period of time or to house them so that they don’t die of exposure which can be seen as a relatively mechanical process. However, I don't believe the distinction is so apparent or that the Last Mile program truly fits into that configuration. The relationship between doing A to get B is not as deterministic in dealing with the unsheltered homeless as it can be with other forms of relief aid. 

Now it is true that finding ways to permanently house homeless individuals or better to prevent them from becoming homeless in the first place would be a higher point of leverage within the larger system. However, in focusing on the first approach of finding ways to permanently house the homeless, the status of those individuals in terms of health must also be considered and malnutrition and anemia will make helping them far more difficult. How all this will be addressed though will change from place to place. 

The third is what is happening with one’s self. Are you in an enabling environment, the ability, time and resources that allow you to step back and have the means and capability to think through the building of a strategy, say like taking this course then systems thinking is worth investing in. Rob warns, however, that it is not a magic solution. It does not make complex issues simple or worse yet if wrongly interpreted, simplistic. What it can do, from a new community paradigms perspective is make that complexity coherent. 

Virtual Systemic Inquiry - GPS for New Community Paradigms?

The next segment of the STW/STiA course moves back by two segments and three blog posts. The Kumu map for this section covers the development of a process termed Virtual Systemic Inquiry or VSI.  It is designed to provide a review and means of collaborative communication in developing a systemic approach, as involving an entire system, to community wicked challenges.

An extended and updated multi-video explanation of this Predicament (updated 1/30/2019) is available to begin providing an extensive explanation, for a fairly involved process in which both the steps and the rationale behind them.

The basic Predicament is that difficult and wicked challenges require sets of multiple individuals with diverse backgrounds but geographic or other logistical factors make working together difficult.

Short version, it is a process using web-based resources such as Cacoo, Debategraph, Gmail, Google Docs, Insight Maker, Kumu, LinkedIn, Lucid Chart, MediaWiki, Prezi and Skype or other similar programs to communicate and collaborate through systemic process interventions with others in an effective and efficient manner. despite being geographically, and therefore also time zoned separated, 

A series of Insight Maker, some of which are highlighted and expanded upon below will help make the argument in support based on insights from this course and past new community paradigms articles. 

The logistical challenge of selecting the most appropriate people to participate in the collaboration and developing the means of interaction to improve the likelihood of effecting the intended results remains.

According to a VSI perspective, it's not reasonable or appropriate to expect a single individual or even a small group to determine how to intervene meaningfully and effectively to address a complex wicked situation. That is, however, exactly what we do in most local governments, selecting five individuals for four years who then head a complicated oriented management system based on a solitary figure setting a top-down agenda to address complex issues and when it doesn't work we get another person and repeat. 

Large-scale collaboration then is essential if one wants any hope of addressing wicked problems at a community level in a meaningful and effective manner. Collaboration though presents a number of challenges itself because it, in truth, it brings in more complexity. The goal is to have it become, along with the issues being addressed, closer to what has been termed coherent complexity. 

Complexity though, its true nature, can still remain hidden for a number of reasons despite the significant complexity inherent in the wicked challenges facing our communities being immense. Many of these wicked challenges are the result of emergent properties of larger, even global systems that cannot be understood or fully comprehended by individuals or even by individual components (institutions, political parties, countries) of a larger system. Even if understood, they often cannot be adequately addressed by any of the individual components or subsystems alone. 

Wicked problems have become so complex, incoherently complex, that they're broken down and perceived as complicated by not only the general public but also those tasked with addressing them with top-down complicated and reductionistic based management systems, sometimes tending to reach high levels of bureaucratic complicatedness. 

Not only are the wicked challenges or situations themselves complex but the environment in which they exist, as an integral part of the challenge, and thereby the processes by which they must be addressed, particularly the social aspect, is also complex.

The model Perspectives on Csikszentmihalyi's views on Complexity vs Complicated illustrates important differences between complicated oriented problems and complex oriented problems which makes such an approach even more problematic.

Based on this Realization that situations warranting collaboration are invariably complex, and wicked problems are highly complex, collaboration is logically envisioned then as the most likely means to produce meaningful and effective outcomes. The complex nature of the wicked problems have and are expected to continue to overwhelm previously employed tools and methods.

The problems most successfully addressed by management systems based on reductionism and complicated algorithms are seen as being highly differentiated with little integration. Solutions then tend first towards greater differentiation followed hopefully then by integration. Seldom though are they able to achieve both differentiation and integration at the same time with any long-term success. Complex systems though can be both highly differentiated and highly integrated. This means that when imposing a complicated management system upon a complex system challenge that either differentiation or integration is going to be disregarded and therefore not adequately addressed. 

This then requires an integrated toolset, for which the VSI method provides both Tool Requirements and Tool Evaluation. VSI uses a wiki, as does New Community Paradigms, but as a focus page for the collaborations because of the ease of multi-user updating, allowing anyone involved in the collaboration to know that whatever aspect of the investigation they're searching for that the appropriate links can be found. 

Concept maps could be developed in Insight Maker and Kumu then linking those concept maps to the wiki with issue exchanges on the concept map being conducted through attached discussions. More formal models could also be developed in Insight Maker and Kumu. Again, once initiated, a link to the model could be added to the wiki and issue exchanges on the model again conducted through discussions. Kumu could potentially become the apparent heir simplifying the architecture by combining multiple pieces of the puzzle, focus page, discussions, concept maps and formal models together. It might though be too specialized and internalized though for use with larger groups.

Tools alone though will not be sufficient to ensure meaningful and effective outcomes. The participants must also be able to develop an integrated mindset to offset the natural and, in the right context, still definitely useful differentiations that they bring to the effort.  This will be different for different levels of the process but to be collaborative, a mindset founded on a shared vision is important with participants being on the same wavelength.

It is of critical importance for everyone involved to understand the intent of the collaboration by having them involved in the early establishment and the refinement of the intent from the beginning. Having the collaborators engaged in the development of the intent helps develop a sense of ownership which provides a basis for individuals to stay engaged and contributing. The challenge from a new community paradigms perspective is how to expand upon this to include an entire community.

Even with a well defined intent and community or group ownership of the challenge, working with a distributed group of individuals through multiple applications will require efforts expended on an ongoing basis to maintain focus. It is essential that all the component tools that may be employed be glued together in a manner that allows collaborators to keep track of their contributions and the overall development.

The Enabling Generative Interactions requires an integrative mix of differentiation and integration meaning that it can potentially become coherently complex in a manner that complicated top-down management systems cannot. 

Micro-worlds are models of the relevant relationships of a challenging situation or wicked problem set up in a manner with which people can interact to study the implications of their actions and as such are hopefully better able to understand the situation. A problem is that people often create these Micro-worlds unconsciously then tend to treat them as video games, seeking to understand only enough to win the game and miss the deeper underlying set of relations that are responsible for that micro-world working the way it does.

This review of Virtual Systemic Inquiry will continue in the next two blog posts and will be integrated with the Participatory Democracy with Systems Thinking Insight Maker model in the next post and later as a Kumu map.

Systems Practice - Practice Can Mean Making Mistakes and Repeating to Learn from Them

The latest Systems Practice project ”Jerusalem Vision” dealing with Jewish Palestinian relationships has been approached from around the edges in the last post and the two preceding. With this post we will begin zeroing in. As always, this blog is not intended as a substitute for the course. Instead, it takes more of a bird's eye view to see how it might relate to other aspects of new community paradigms.

For me, Systems Practice is basically applied Systems Thinking, thought experiments with pictures (graphic systems maps) using alternative forms of cognitive navigation to steer through challenges, especially wicked challenges. This again needs to be recognized as a sizable cognitive shift for many. Though it can be far more intuitive than might be expected. A favorite metaphor of mine for this new thinking is navigation during the Age of Discovery, a paradigm shift as notable as modern man’s mission to the moon as told in How We Got To Now with Steven Johnson / Time (Emmy Winner). We still need all of our existing “sailor skills” but we are adding a new layer of mapping skills based on a new way of looking at the world.

I still consider myself as having a limited background in Systems Thinking. Many if not most people taking the course though were even less familiar with Systems Thinking and far more familiar with the usual linear reductionist approach to understanding which means breaking things up into smaller pieces for ostensibly better control. The challenge then is developing a means of helping others to cross over to a more holistic, Systems Thinking approach or in the case of a systems practice approach through a group process. I still don’t believe that there is a strong enough foundation in Systems Thinking provided at the beginning of the Systems Practice course and introducing the systems mapping tool Kumu at the very start could help with that. Those with less experience in Systems Thinking may have problems with Systems Practice but those with that do have that experience will still need to be open to taking different perspectives.

Despite any issues raised in the last post with the article A Systemic View of the Israeli-Palestinian Conflict and its related systems map, its author David Peter Stroh is also recognized as the author of ”Leveraging Grantmaking: Understanding the Dynamics of Complex Social Systems”, concerning the Calhoun County, Michigan study, which used Systems Thinking to address homelessness. The report was cited in the blog post Learning to Apply a Systems Practice to the Wicked Problem of Homelessness and has also been cited in the past when discussing Collective Impact and other times since then.

The Calhoun study looked at the “whole system," not one system for funders, one for providers and another for everybody else. The community’s incentives structure existed to provide quick fixes to address the immediate problem, rather than creating sustained change. One study observation was “The most ironic obstacle to implementing the fundamental solution was the community’s very success in providing temporary shelters and supports.” Systems Thinking was used to determine where intervening with higher level approaches such as housing first could effectively occur. This approach worked even with rising unemployment in the area. Stroh also wrote an insightful article on “Exposing the Hidden Benefits of Business as Usual: Why the Status Quo is So Difficult to Change,” which can also be seen as being applicable to a Systems Practice effort.

This is the third completed Systems Practice project. Waiting this time until the end of the Systems Practice course before blogging allows for a bird’s eye view of the entire Systems Practice process. It also allows inclusion of the other past Systems Practice projects found in the New Community Paradigms Systems Practice wiki-page, which include “Addressing Homelessness in Portland, Oregon” and “Addressing Plastic Pollution in Thailand” as well as looking at Systems Practice from a more philosophical perspective categorized as ”Systems Practice UK”.

The SP UK course’s more philosophical indoctrination did help to realize some important insights more fully. One is appreciating the difference between people finding themselves in a complex system and those finding themselves in complex situations, recognizing that these aren’t mutually exclusive. People in the actual applicable problem situation will have different perspectives from those considering the relevant more abstract system in which those situations arise.

The project Plastic Pollution in Thailand and the UK Systems Practice more philosophical perspective gave rise to my own perspective that Systems Practice (SP USA) is not a philosophy. It is a playbook. They actually have a playbook, Systems Practice Workbook Omidyar Group that describes the process undertaken in implementing a Systems Practice approach to deal with wicked problems (the impossible of the course’s title). It has no issues with taking from any of the different Systems Thinking approaches, whether ontological, epistemological, soft or hard explored in the Systems Practice UK series that suits its pragmatic purposes.

The “Addressing Homelessness in Portland, Oregon” project was an extension of the ”Financial Modeling and Last Mile Homeless Food Truck” project and I was the team leader. With ”Plastic Pollution in Thailand, I joined a group, with an already established focus, which unfortunately broke up before the end of the course though I still brought the project to a conclusion. The most recently completed project was the one most in line with the ideas behind ”Direct Democracy and Systems Thinking.” The topic Palestinian and Jewish relationships in the City of Jerusalem was chosen democratically among the eight members of the group out of nine possible topics.

The greatest value the previous two Systems Practice projects brought to the Jerusalem Vision project is what was done wrong or went wrong in those projects. Before the first Systems Practice course, I had worked solo and still tend to do that. Systems Practice though significantly informed and induced me to substantially change the approach I took when working with a group.

My first mistake with Systems Practice was creating a systems map using Kumu far too early in the process before the course had barely started. I came with my cup perhaps too full, putting me out of alignment with the course and with being able to collaborate with the others on the team I was supposedly leading. It took a while to realize that the differences were due to Systems Practice's attempt to focus on group interactions in coming up with solutions.

A primary issue that Systems Thinking seeks to address, because of a tendency of a reductionist approach of breaking systems into smaller components, is to only look at factors in immediate or near-immediate approximation instead of following causal pathways further out to discover hidden relationships. What may be a positive causal force at one point of the system may then become a negative causal force at another point. Systems Practice does address this though perhaps not explicitly allowing its process to reveal any Systems insight.

This doesn’t mean the analysis by reductionism is completely abandoned. The first assignment of the SP course, USA Plastic Pollution in Thailand had us present our system challenge through a Complexity Spectrum, consisting of selecting within spectrums of polar choices.

• Level of Understanding: Well understood vs Not Understood
• Engagement: Consensus vs Diversity of Opinion
• Environment: Stable vs Dynamic
• Environment: Self-contained vs Interconnected
• Goals: Small Scale vs Broad Change
• Goals: Short-term vs Sustainable

Although any relational mapping with Kumu was delayed, using a different mapping program, Plectica allowed for the creation of a map which reflected the Complexity Spectrum’s hierarchical nature and that provided spaces for each of the members of the team to provide their individual input. It fitted rather well with the course assignment proving in this instance, more helpful than Kumu.

The latest “Jerusalem Vision” project didn’t repeat this Complexity Spectrum but we still had an analytical perspective brought to the team through our team leader Yoel Ben-Avraham who has a background as a Systems Analyst. With the latest Jerusalem Vision project, we used RealTime Board as suggested by our team leader Yoel. It had some features similar to Plectica and despite being spread across the globe, we were able to witness the movement of the different factors we had gathered into common themes while collaborating together in real time.

Factors and themes, as well as forces, enablers, and inhibitors, are among specialized terms Systems Practice introduces to help define their group-oriented approach to Systems Thinking. Before, however, getting into that the course first had us establish some common visions of the challenge we were about to address.

Reaching for a New Jerusalem Vision using Systems Practice

Recently, the first blog post in a long while was posted on the third effort to use Systems Practice to address a complex issue, this time Israeli/Palestinian relationships in the City of Jerusalem. This post continues in that vein. In truth though, little will be said about the issue itself, despite recognizing that its greater awareness generates greater attraction. Instead, the focus will be on the Systems Practice approach and how it could possibly be related to direct democratic governance.

Seeking to find solutions through collaborative dialogue and deliberations, which are aspects of Systems Practice, can also be seen as components of direct democracy as opposed to more competitive forms of interaction, such as debates within more representative forms of democracy through institutions. This is not to establish that one form of democratic governance is preferable to the other. The Systems Practice approach seeks to examine the system at a level foundational to such a determination. It is not the system though that calls for the resolution of differing perspectives. It is for people themselves to make such a determination.

Before proceeding further, certain points will need to be repeated or clarified. As has been said in other efforts of this type this is not intended to be a substitute for the course. If you become interested in the process then sign up to take the course. An added piece of advice for Systems Practice, plan to take it again a second time, one time will likely not be enough. This is suspected to be true whether you sign up as an individual or start off as part of a group. 

Blogging about this third project was held off until completion of the course. This creates new challenges in presenting the approach to addressing this or any complex issue. With previous projects,  the proverbial elephant could be served in small portions focusing on a specific component of the process. Taken as a whole, it becomes all the more complex. It will still be served in limited portions but there is a greater awareness that there are no aspects of the system that can't be considered from multiple perspectives.

A Systems Thinking/Systems Practice approach can assist in addressing what can arguably be designated as a Wicked Problem.  As has been noted before, if messes, as defined by Russell Ackoff are problems that can be thought of like Frankenstein’s monster then wicked problems are Godzilla. Wherein the potential sources of solutions can seem as complex as the wicked problem itself. 

The full systems map for this project will not be presented at this point.  First, this blog post or even series is not intended to provide a final answer or solution. The focus will be on the process of attempting to arrive at an answer. Primarily though because it is too complex, in at least three ways. 

We are requiring people to address the complexity of the issue itself, the complexity of a Systems Thinking approach to the issue as opposed to the more generally overly used and generally taken for granted reductionist approach and the use of general unfamiliar graphically oriented means of communicating these ideas through systems mapping. If these concepts are to be widely disseminated then all three must be considered together.

I had limited knowledge of the factors involved in the issues making up the system being considered. This was made all the more apparent by working with somebody embedded, as a stakeholder, in that system. It’s important to note that additional diverse stakeholder perspectives are still needed. When dealing with systems, especially detrimental systems, recognizing the particular realities and physical manifestations are as important as the underlying conceptual system of relationships. Without this, it’s impossible to understand the story behind people’s motivations.

The tendency to default to reductionist thinking rose even with the writing of this blog post which was rewritten a number of times to continually expand the scope to a more holistic perspective. The systems map for this Systems Practice project was created largely from other text which is more linearly oriented. Reinterpreting the map back to text doesn’t merely involve retracing steps. Hopefully, there is a solid, functional relationship between the two, though not necessarily direct, allowing for a global understanding encompassing both what has been considered longitudinal and latitudinal perspectives.

Systems maps on their own can serve different purposes, to either develop understanding or to communicate understanding but, at least in my experience, not both. There is, in my view, a sizable gap between the two that must be overcome before accomplishing that. Communicating full understanding is difficult and often the solution is to simplify and omit something. My past tendency has been to concentrate more on gaining understanding, admittedly mostly my own, and less on communicating that understanding to others. Systems Practice extends this potential for understanding to a group. 

There is also a danger with people, even if part of the Systems Practice process, getting the mistaken impression that maps, as presented, are complete discouraging additional input.  A systems map can be seen as being more extensive and coherent in describing a system than it is actually. How extensive a map appears can be an issue in making the challenge seem overwhelming without boundaries or with endless divisions. How coherent a map appears can help give the impression that the factors are related but not necessarily how. Together they seemingly suggest containing and controlling a challenge giving a false impression of finality. The maps, as a result, aren't examined closely enough to be properly tested and require having a guide to assist with navigation to do so. This arose during the process of developing a Systems Practice project dealing with Plastic Pollution in Thailand.

The often cited Systems Thinking principle established by George Box that all models (or maps) are wrong but some are useful needs to be retained. The question of where wrong and where useful must be continually asked. Explicitly contrasting those differences helps test the system to maintain authenticity but not to become over-elaborate.

As was said in the previous post, the particular issue being considered is both complex and controversial so one’s approach could potentially leave one susceptible to a charge of white-knight-savior hubris. So let me be clear, as said previously I did not start with any expertise in the issue. Our efforts did not result in a solution to the Israeli-Jewish/Palestinian-Arab conflict. We did not come up with any solutions. That was never an expectation. What we developed was a deeper understanding of what would become to be termed factors, forces and persistent patterns of causality of the system we were addressing. There are still though potential points of controversy remaining that will arise because of positions that are taken. 

This is not to suggest any intention to choose one side of an issue over another. Recognizing contrasts in perspectives can be seen as an essential component of establishing cognitive diversity. Cognitive diversity refers to the concept put forward by thinkers such as Scott Page. It's not meant as a panacea for a lack of other forms of diversity or to address any differences in the distribution of power. Cognitive diversity, particularly beyond my own, was considered to be an essential component in developing the project. The problem is when contrasts rise to the level of conflicts or coercion. Taking a more reductionist oriented approach, the opposing perspectives could be seen as different and separate competing systems. 

Systems Practice approaches these contrasting perspectives, even if to the point of being confrontational, as being a single system in a state of oscillation between those contrasting perspectives. Even so, positions by necessity must be established which will by their nature not be settled and will invariably be objected to by someone. 

It is not enough though to merely recognize arguments of opposing perspectives in an attempt to provide a so-called balanced view. What needs to be realized is how the different factors making up those perspectives interrelate with each other, creating causal influences beyond the point of direct cause-effect confrontation to attaining feedback so as to understand why the entrenched system despite being deleterious is maintained. 

As a means of transition, another systems map, on the same issue in general, will be considered first. The map being used for the purpose of comparison and contrast is A Systemic View of the Israeli-Palestinian Conflict by David Peter Stroh in the Systems Thinker. It is arguably far more accessible and comprehensible than our Systems Practice map and purportedly comes up with a solution. 

A large portion of the Systems Practice project to Create a New Vision for Jerusalem, especially for my contribution, was based on an article by Dr. David Koren, Advisor to the Mayor of Jerusalem for Arab and eastern Jerusalem affairs,  "Eastern Jerusalem: End of an Intermediate Era". The next blog post will go into more detail. 

.