system thinking Archives - The Systems Thinker https://thesystemsthinker.com/tag/system-thinking/ Wed, 14 Mar 2018 19:13:11 +0000 en-US hourly 1 https://wordpress.org/?v=6.8.3 Whom Do You Trust? https://thesystemsthinker.com/whom-do-you-trust/ https://thesystemsthinker.com/whom-do-you-trust/#respond Sat, 16 Jan 2016 02:16:14 +0000 http://systemsthinker.wpengine.com/?p=2046 here’s something about trusting people — and having people trust us — that is exciting. It’s a part of human nature to give and receive respect. Yet when it comes to work, all too often trust — real trust — is in short supply. According to the dictionary, trust has essentially two meanings: To have […]

The post Whom Do You Trust? appeared first on The Systems Thinker.

]]>
There’s something about trusting people — and having people trust us — that is exciting. It’s a part of human nature to give and receive respect. Yet when it comes to work, all too often trust — real trust — is in short supply.

According to the dictionary, trust has essentially two meanings:

  • To have confidence in someone, or
  • To expect/hope/suppose that someone will act or something will happen.

In the workplace, we need to consider this distinction. For me, real trust is about the first definition — the belief in a person’s ability to perform a specific task under specific circumstances. It is a positive statement about the relationship between two people:, “I believe you are capable of [taking some action].” This form of trust implies interdependence and is crucial to the development of a healthy relationship.

The second meaning connotes obligation:, “I expect that you will [take some action].” As such, it implies dependence in the relationship. This attitude blocks the development of an equal partnership, where both parties can feel fully valued. Unfortunately, this latter definition of trust is all too prevalent in many organizations.

We Are in This Together

Why is real trust so important? Studies have shown that it improves task effectiveness, because it reduces the need for people to check up on each other. Great teamwork requires real trust because members need to feel confident that their coworkers are fulfilling their commitments as they work interdependently toward the same aim. In relationships based on the first definition of trust, people feel relaxed and can communicate openly; these factors boost individual and group enthusiasm for joint undertakings. Lack of real trust increases anxiety, diverts attention from the task, stifles innovation, and drains energy.

But real trust can be difficult to achieve. All too often, we see people as assets or things that are ultimately replaceable. We forget that others have aspirations and needs, and, given the opportunity, want to do their best at work. We fail to acknowledge that the individuals who design, operate, and manage our organizations are key to our mutual success.

Dynamics of Trust and Control

When an organization fails to achieve the desired performance, managers have a choice (see “Trust and Control”). They can set in place mechanisms designed to reduce the performance gap — procedures, scripts, checks, and measures that assess and constrain performance. Or they can trust their staff and colleagues and support them by having a clear common purpose, coaching and encouraging them, and engendering a collaborative learning culture.

Command Loop. One option for addressing the performance gap is to introduce control, setting in motion the Command loop. At first, the control may take a supportive form. Common, standardized practices can help everyone behave consistently and successfully. Managers usually introduce control with this positive intent, believing that if the implementation is well managed and aligned to a common purpose, then everything should be okay.

The problem occurs when managers see control mechanisms as the means to minimize performance gaps and use them more and more frequently. They rely less on coaching and open discussion for learning and fine-tuning performance, falling back instead on policing mechanisms designed to ensure compliance with rules.

TRUST AND CONTROL

TRUST AND CONTROL

In the Command loops, managers address a performance gap by instilling control mechanisms and standardized practices. This approach works in the short term, but over time, workers’ level of commitment falls and further undermines performance. In the Nurturing loops, real trust builds on itself, leading to improved performance.

Inherent within the Command loop is the second definition of trust — “I trust that you will…,” meaning “I expect you to adhere to these rules/standards.” These requirements do not constitute real trust in someone; they are about compliance with a directive.

Yet people are not machines. As Maslow documented more than a half century ago, we all have a basic need for fulfillment and involvement. To command performance in a work environment may have been successful when commanders held the lives of workers or slaves in their hands. Today, workers have a totally different set of rights and expectations. People typically respond to being told what to do by digging in their heels or complying with reduced self-motivation. Both responses are saying, “If you don’t trust me, then why should I bother?”

If you’ve never experienced this dynamic, believe me, you don’t want to. It can be debilitating for any team or organization. Compliance costs people and companies money, mental energy, and time. When the use of control mechanisms escalates, it undermines individual and team performance and leads to a pervasive lack of trust.

When this happens, the challenge becomes more than just addressing the performance gap; it involves addressing increasing numbers of employee issues. Employees behave in ways that may not conform with their supervisors’ wishes as they seek to rationalize the rules with their own needs and understanding of what will work. They may lack motivation or commitment, as demonstrated by increased absenteeism; they may become obsessive and emotionally volatile, rejecting all outside input; or they may become politicized, seeking allegiances and undermining perceived threats to their survival.

Suppliers, customers, and other third parties readily pick up on the lack of trust. The organization probably uses the command loop with them, too. No doubt it seemed like a good, or at least an expeditious, idea at the time!

Once lost, real trust can be hard to rekindle. In a control culture, if people’s performance isn’t what managers want it to be, then managers ironically put additional controls in place. But, as Evert Gummesson states in Total Relationship Marketing (Butterworth-Heinemann, 1999), “Trust cannot be assured through contracts.”

Nurturing Loop. The other option is to address the performance gap through the Nurturing loop. Here, real trust allows for open communication when a problem occurs. Healthy relationships and open communication enable people to work together to proactively learn how to address the gap efficiently and effectively. Basic guidelines and protocols provide consistency and help people avoid illegalities. However, any control mechanisms should be minimal, designed with the involvement of the relevant operational teams.

For the Nurturing loop to succeed, the organization must have a clear, explicit common purpose to which all goals and decisions are aligned. This provides a coherent message and environment with which people can engage and to which they can contribute positively. Everyone is explicitly going in the same direction. Trusting appropriately recruited people to meet the agreed performance goals breeds a positive, supportive team environment and serves as a basis for success.

People may lack a common purpose because none exists in the organization, or because it’s not clearly communicated. Humans are goal-oriented beings. We need something to justify our actions and from which to derive self-worth and a sense of identity. Without a common purpose to work toward, we create our own goals or ask colleagues and friends until we find one that makes sense for us.

As a result, most people in the organization have different goals and act in disparate ways. When different parts of the organization try to achieve different things, tension builds. Managers then put more controls in place. In these circumstances, it can be hard to establish a common purpose, as people may have been working to their own strongly defined goals for some time and will be wary of the new initiative.

Solutions

If you find yourself in a control culture, take heart; there are things that you can do.

  1. Understand why the situation is as it is, identify the difference that will make a difference, and leverage change for the better. Finding out about the situation helps to inform you of the underlying dynamics:
    • What and who is sustaining, or benefiting from, the distrust?
    • Who is predisposed and motivated to address it?
    • What sense of “we’re in this together” exists?
    • Where is the leadership?
    • What do people feel they need to move forward?

    Once you’ve identified the dynamics; the players and their goals, motivators, and beliefs; and people’s openness to change and desire to get involved, then you can start to plan your approach to reinstate real trust. The aim is to decide on the most efficacious route to break the patterns in a sustainable way. This can be difficult; organizations driven by red-tape, procedures, and protocols are usually plagued by inertia, providing an extra challenge to change.

  2. Stop the cycle of distrust and find ways as a group to rebuild positive relationships.
  3. Get a commitment from top leaders to follow through on a program of re-engagement and realignment in the organization.
  4. As an individual, define your own overarching goal. Work to nurture and protect your team as you build support for your approach with colleagues and senior managers. All the time, you must align your actions and decisions to your goal, even if you don’t explicitly refer to it. If people are used to following controls, you may even have to create new, aligned procedures and processes until you are able to dismantle the old ones.

Some organizations are so deeply entrenched in the cycle of distrust that one person alone won’t be able to make much of a difference. In that case, you have two choices. First, you can accept the ways things are, do your 9 to 5, and enjoy life. If you work in a large organization full of inertia, you’ll be okay for a while. At some point, you’re likely to become deadwood in the eyes of colleagues. At that point, you either should move on or take another stab at implementing change.

The second choice is to find somewhere else to work. You’ll feel good and will leave on a positive note, looking forward to the next part of your life.

Conclusion

Tom Peters speaks of trust as being the “single most important contributor to the maintenance of human relationships. And for business, it can, quite simply, mean the difference between success and failure.” Relationships are about achieving more together than we could on our own. If problems occur, the most fruitful approach is to work with people to resolve them, based on trust, open communication, and proactive learning. For once you start putting in systems of control that force or constrain behaviors, you will be on the slippery slope toward lower performance and a dysfunctional organization.

David Newport (david@effectivevision.co.uk) is an NLP Practitioner and ergonomist, with a background in qualitative research and operations direction. He works with people and organizations to help them understand the behavioral traits and dynamics that impact both their customer experience and bottom line.

The post Whom Do You Trust? appeared first on The Systems Thinker.

]]>
https://thesystemsthinker.com/whom-do-you-trust/feed/ 0
Anchoring Model Development in Causal Loop Diagrams https://thesystemsthinker.com/anchoring-model-development-in-causal-loop-diagrams/ https://thesystemsthinker.com/anchoring-model-development-in-causal-loop-diagrams/#respond Wed, 13 Jan 2016 04:15:46 +0000 http://systemsthinker.wpengine.com/?p=2399 s a consultant working in the field of systems thinking, I am continually amazed by the ease with which people are able to read and draw causal loop diagrams (CLDs) with just a little instruction and coaching. On the other hand, I am continually frustrated by the fact that many of these same people can […]

The post Anchoring Model Development in Causal Loop Diagrams appeared first on The Systems Thinker.

]]>
As a consultant working in the field of systems thinking, I am continually amazed by the ease with which people are able to read and draw causal loop diagrams (CLDs) with just a little instruction and coaching. On the other hand, I am continually frustrated by the fact that many of these same people can read stock and flow diagrams with little difficulty, but find creating these maps themselves a much greater challenge.

I strongly believe that stock and flow diagrams offer a deeper understanding of a system than do causal loop diagrams. Nevertheless, in the past, I found it difficult to get more than a small handful of clients to develop the facility to build them. Despite its obvious benefits, the rigor of the stock and flow language comes at a price—it is more difficult to learn. While companies that create simulation software have made enormous advances in their products, vastly simplifying the model-building process, we still have a long way to go in learning how to help people develop the facility to create even simple models.

High Performance Systems, the creators of the ithink® software, have stuck firmly to their belief that a true understanding of the dynamics of any system requires an appreciation of the underlying stock and flow structure. For that reason, their software does not provide the facility to build CLDs. The best they offer are “Loop Pads,” which they describe as “. . . simple pictures that identify the cause and effect processes that work to generate dynamic behavior patterns.” To display these pictures, you have to build the stock and flow model first.

The challenge is to find more effective ways of helping clients develop an understanding of the structural dynamics of the system they are studying, while acknowledging that they usually find CLDs an easier place to start than stock and flow diagrams. To that end, I have developed an approach to model building that uses ithink in a slightly unorthodox way to start clients at a relatively easy place and move them quickly to a more sophisticated understanding of a given system using stocks and flows. Paradoxically, this technique capitalizes on the software’s unwillingness to let users draw CLDs.

From Feedback Loops . . .

we are simply building a CLD in which resources allocated to process improvementTo follow this process, you must use version 6.0 of the ithink software, which allows you to minimize the size of the converter icon. Start by changing the defaults to set the converters to small. Doing so lets you use the converters as you would the variables in a CLD. Then use the text box facility, which is one of the objects on the menu bar, to create the polarity signs (, “+” or “-,” which correspond to “s” and “o”). For example:

So far so good. Up to this point, we are simply building a CLD in which “resources allocated to process improvement” are influenced by current “performance” and “desired performance.” However, when we try to create a causal link between “resources allocated to process improvement” and “process errors,” an error message appears indicating that such an action would create a circular connection.

nature of the mathematics that underlies the stock and flow

The nature of the mathematics that underlies the stock and flow language means that the software is unable to calculate the value of any converter or flow when they loop back on themselves. As the help files state: “In drawing connector linkages, you may encounter an alert which tells you that circular connections are not allowed. Mechanically, this alert means that you have attempted to create a chain of converters or flows, such that one converter or flow ultimately depends upon itself. The software cannot resolve the resultant simultaneous equations.”

. . . to Stocks and Flows

to gaining a deeper understanding of the feedback processes involved in this structure

To get past this barrier, we must create at least one stock somewhere in the loop. This process forces us to look more closely at the structure of the loop we are creating and identify one or more stocks. Every feedback loop has an accumulation—it is this accumulation that generates the feedback dynamics. In this example, the issue for the team was how actual performance levels drove “resource allocation to process improvement.” With this in mind, we can now make a simple modification to the CLD by converting the variable “performance” into a stock.

We are now a step closer to gaining a deeper understanding of the feedback processes involved in this structure. We have done so, however, by beginning with a process that clients are familiar and comfortable with and then moving to a structural understanding through one simple step. How we develop the model from this point forward depends on your goals. We could stay with this loop and simply develop the stock and flow structure for each variable.

Going into Greater Detail

We also might want to explore a certain part of the structure in greater detail. For example, we might be interested in the dynamics involved in a process-improvement program. In this case, the team realized that the resource allocation decisions were not only determined by actual performance but by the gap between actual and desired performance:

we might be interested in the dynamics involved in a process-improvement program

On the other hand, we may want to develop a loop to explore the impact of process quality. One possibility could be:

we may want to develop a loop to explore the impact of process quality

Once again, when we try to close the loop by connecting “investing in process quality” with “process quality,” we will receive an error message that circular connections are not allowed. How we respond to this message depends on what we are trying to understand with the model. If we want to examine the financial implications in more detail, we could begin to unravel the structure underlying the variable called “profits.” For example:

we will receive an error message that circular connections are not allowed

The key point is that we always anchor the model development process in something the client is familiar and comfortable with—the development of CLDs. We then force the software to highlight a logical error to provide a stepping stone to unfolding the stock and flow structure. I have found that, using this technique, more clients are able to develop an ability to create their own stock and flow models than before. Prior to using this approach, I found that clients viewed CLDs and stock and flow diagrams as separate and distinct languages. Since I’ve implemented this process, I have noticed that they have begun to see the similarities, rather than the differences, between the two. As a result people are less mystified when working with stocks and flows, seeing them embedded in the feedback loops of CLDs.

David Rees is the director of High Performance Learning Systems, a consultancy firm specializing in applying systems thinking principles and tools in public and private sector organizations. He is also a research fellow at the Centre for the Design of Innovative Systems at UNITEC in Auckland, New Zealand.

The post Anchoring Model Development in Causal Loop Diagrams appeared first on The Systems Thinker.

]]>
https://thesystemsthinker.com/anchoring-model-development-in-causal-loop-diagrams/feed/ 0