Tag: agile

The Lie of Useful Fictions

While writing about the helpful analysis described in Agile Conversations, I mentioned that I had some concerns with the book. While the analysis method draws upon solid scientific studies and I have personally found the conversation types useful in identifying and engaging in the different interactions that I have with my co-workers, the foundation upon which the authors built bothered me. The fundamental reason that the authors give for why conversations are effective at changing culture is as follows:

"Though our ability to gossip surpasses that of other species, [Yuval] Harari says that what is really unique about human language is our ability to discuss non-existent things. (Sapiens, Ch. 2). With this special power, we are able to create and believe shared fictions. These fictions allow us to collaborate at tremendous scales and across groups of people who have never met. In this way, a community's belief in a crocodile-headed god can create flood control works on the Nile, as described by Harari in another of his books, Homo Deus: A Brief History of Tomorrow (Homo Deus, 158). And a shared belief in continuous improvement can allow us to create a learning environment and a performance-oriented culture rather than a power-oriented or rule-oriented culture, as described in Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations by Nicole Forsgren, Jez Humble, and Gene Kim (Accelerate, 31)."

What triggered the most negative reaction was the concept of "shared fiction". The idea that fictions enabled large groups to collaborate didn't make sense. Rather than dismissing my reaction, I went in pursuit of what it was that bothered me, starting with a rough definition of "shared fiction".

I went to the Merriam-Webster online dictionary and pulled the following definition for "shared":

  • used, done, belonging to, or experienced by two or more individuals

And the following definitions for "fiction":

  • something invented by the imagination or feigned
  • an assumption of a possibility as a fact irrespective of the question of its truth

After seeing these definitions, my initial reaction was to cynically and naively reword the last sentence into the laughable statement: "And if we feigned that continuous improvement could actually happen, then we could create a learning environment and a performance-oriented culture rather than a power-oriented or rule-oriented culture..." Such a statement reminds me of the fairy tale about the Emperor's New Clothes. Just pretend and everyone will play right along until someone points out the obvious. While the rewording was overly simplistic in its application of the definitions, it led me to wonder what Yuval Harari meant when he used the word "fiction".

In an interview that he gave to the Smithsonian Magazine, Yuval Harari states:

"The truly unique trait of Sapiens [that is, human beings] is our ability to create and believe fiction. All other animals use their communication systems to describe reality. We use our communication systems to create new realities. Of course, not all fictions are shared by all humans, but at least one has become universal in our world, and this is money. Dollar bills have absolutely no value except in our collective imagination, but everyone believes in the dollar bill."

This division between the physical paper of the dollar bill and its accepted value provides a clue to what Yuval Harari means when he speaks of shared fictions. If I understand what he means, then Harari is saying that a shared fiction is a fiction that a group of people agree exists when it does not exist. I know of another more unpleasant word for "saying that something exists when it does not exist": a lie. Of course, claiming that Harari is saying the Egyptians were lying to each other about the crocodile-headed god of the Nile falls into the trap of believing that we humans can achieve perfect knowledge of the reality around us. This trap is well summarized by the authors of Agile Conversations in the section on cognitive biases that follows the paragraph I quoted from the book.

Another angle on the separation between the physical dollar and its agreed value is that there is no scientific experiment from which we can determine the value of the dollar bill. To put it another way, there is no empirical evidence from the dollar bill itself that would determine its value. Applying this pattern to what Harari says about the crocodile-headed god of the Nile, it seems to match up. The definition for "shared fiction" appears to be: "something that two or more people claim to exist that has no scientific, empirical or sensible evidence to confirm its existence." Turning to the claim in Agile conversations about a shared belief in continuous improvement, it appears that "shared fiction" as described by Harari and "shared belief" as described by Douglas Squirrel and Jeffrey Fredrick are synonymous.

If we applied this definition broadly, I fear we would find that justice, mercy, and peace would be categorized as "shared fictions". If that is over-broad, I would greatly appreciate being corrected, but based on Harari's application of this definition across science, legal theory, and religion, I find the case rather difficult to make. This definition of "shared fiction" appears to assume that "reality" would be defined as "something that has scientific, empirical, or sensible evidence to confirm its existence." These two definitions, as water-tight as they may seem, are incorrect. I will first deal with the definition of "reality" and then the definition of "shared fiction".

First, how do we know that reality is limited to scientific, empirical, or sensible evidence? If this is certain then we should be able to find such evidence to confirm it, and yet we don't. One example is the Borde-Vilenkin-Guth Proof in physics, which indicates that any universe that has an average expansion rate greater than zero must have a beginning. Since our universe does have an average expansion rate greater than zero and nothing comes from nothing, something had to begin the universe. Now, scientific, empirical, and sensible evidence requires a universe to exist in the first place, yet it would be ridiculous to claim that a fiction brought reality into existence. Another example is from a longitudinal study of near-death experiences reported in The Lancet (van Lommel, et al 2001). In that study, they determined that the near-death experiences of the patients had no physical or medical root. Included in that study are examples of patients blind from birth who were able to accurately describe the people and environment around them during their near-death experience. In both of these examples*, we have indications that reality extends beyond scientific, empirical, or sensible evidence.

Second, if reality does indeed extend beyond scientific, empirical, or sensible evidence, that would contradict the definition of "shared fiction". One potential way to solve this contradiction would be to claim, as Harari does, that when we create "shared fictions" we create new realities. This goes against the basic common sense principle that something greater cannot come from something lesser. As we human beings are part of reality, and the part cannot be greater than the whole, then we cannot create a radically new reality to replace the existing reality. In addition, we human beings build fictions out of reality, which means that reality must be greater than fiction. Another potential way to resolve this contradiction is to point to examples of people who believed in crocodile-headed gods that didn't exist and how this "shared fiction" enabled them to collaborate with each other, as if to say that "if we can do great things by believing that non-realities are real, then so be it." However, believing that non-realities are real can be summed up in another unpleasant word: "insanity". I don't see how collective insanity would be an improvement to human life; it reminds me of Dostoyevsky's Grand Inquisitor who claimed he was greater than Christ since he would ensure people would go to heaven by teaching them that sin was a fiction, even if it meant that he would burn in hell for it.

Now, the authors of Agile Conversations don't say they are spreading a "shared fiction", though they do hint at it. "[A] shared belief in continuous improvement can allow us to create a learning environment and a performance-oriented culture." The authors made a slight adjustment in switching from "shared fiction" to "shared belief". While we may invent fiction, we don't invent belief. Beliefs are often the result of observing the world and drawing conclusions. For example, I believe that I will see the sun tomorrow. However, by using the two terms in the same paragraph in a synonymous way, it appears that Squirrel and Frederick do mean to treat the idea of continuous improvement as a fiction that we should share for the benefit of others. I would posit that this effectively undermines the goal of their entire book, as it would be difficult to build trust and mitigate fear if we believed that all our work, in reality, was for a shared fiction. If that is the case, then something must have gone very, very wrong.

All this being said, there is much that was good to consider and helpful to use when working with others, so there is something "real" and not "fiction" in the book. With this in mind, I will attempt to identify in my next blog post a better foundation that would allow the book to be effective and truly promote the well-being of those who follow the conversational analysis as described in its pages.

Since I've made some very sweeping statements in this blog post, please reach out to me in case I got something wrong or missed a nuance. I want to make sure that my thoughts, perceptions, and beliefs are in alignment with reality, and that I'm not spreading a lie or encouraging insanity.

* These examples were pulled from The Big Book on https://www.crediblecatholic.com.

Lightweight Trust Building

I was speaking with some colleagues the other day about some low trust interactions that I had recently observed. Based on my description of my observations, one colleague commented that the interactions appeared to arise from a negative feedback loop that promoted a low trust environment between senior leadership, managers, and employees. To break that feedback loop, he recommended having the different groups take a Speed of Trust course. Having gone through a course myself, I agreed that it would encourage trust-building behavior, yet I was concerned that convincing even one group to take the course would be a monumental task. Another colleague acknowledged my concern and the difficulty with saying "Hey, I noticed you're in a low trust environment, would you like to take this trust course?"

This comment about the difficulty of opening a conversation on trust in a low trust environment prompted me to pick up the book Agile Conversations, which I had just started reading. Divided into two parts, the book describes a lightweight method of conversational analysis and the theory behind how it works followed by using the analysis in 5 kinds of conversations. The purpose of the book is to encourage high-trust, psychologically safe conversations regarding business value creation that enable participants to jointly set a direction for a project, commit to goals that will achieve it, and be accountable for the steps taken to achieve those goals. Intrigued, I kept reading.

The analysis of a conversation revolves around writing down a conversation and then comparing what was said with what was thought to improve the next conversation. A few good questions to ask during the comparison are:

  • When I ask questions, are they genuine questions or leading questions?
  • If I had difficulties or concerns with what the other person said, did I mention them and show a willingness to work with him/her to overcome them?
  • Am I being consistent in how I talk and act so that others can trust me?

These stuck out to me, as they ensured I stayed honest with myself about my intent (similar to the Speed of Trust) and promoted curiosity and transparency in my conversations. After determining what could be improved, what was said is revised to address the discovered problems. Then the revised conversation can be role-played to practice the improvements before the next conversation.

After explaining the analysis, the 5 conversations that followed were:

  • The Trust conversation
  • The Fear conversation
  • The Why conversation
  • The Commitment conversation
  • The Accountability conversation

Each of the conversations naturally leads to the next.

The Trust conversation ensures that all parties in a conversation are working from the same story of the problem or need that they are dealing with. When a person starts telling a conflicting story, follow the Ladder of Inference to determine what is causing the conflict so that it can be resolved. This ensures that everyone is working from a shared perception of the world and gives a common language that people can use to be understood. Once people trust that they will be understood, then they will more readily and easily bring up concerns that they have, leading to the Fear conversation.

As an aside, the Ladder of Inference is very close to the Catholic philosophical tradition of how we perceive the world and choose our actions based on those perceptions. Here is a rough sketch: The senses perceive the world, the imagination creates an image from that perception, the intellect recognizes the image, recognition prompts a value judgment which can trigger the emotions. Reason, reflecting upon the image, the value judgment, and the emotional reaction, determines the potential responses to the perception. The will makes actual one of the potential responses. For a more complete and accurate summary, see Aquinas' Summa Theologiae Book I. Questions 79-89 and 93

The Fear conversation provides an opportunity for the team to identify problems they fear will prevent project completion. Often the best place to start uncovering these fears is by examining the deviations of the team from their espoused way of working. These deviations are often disparate mitigations that create conflict within the team and prevent them from being effective. Once the problems are brought to light, the team as a whole can design mitigations for them. As it is probable that there are multiple causes for each problem, spend some time talking through multiple scenarios to make sure that the mitigation will be effective. As some mitigations may require an entire project to be effective, the team will start questioning if the current project is the most important thing to be done, leading to the Why Conversation.

The Why conversation builds a shared purpose and direction for the current project between team members and leadership. Within a timebox, each person has an opportunity to discuss the goals of the project and advocate for their position on them. To achieve a shared ownership of the project, it is crucial for the team to share and understand the interests that lead to the different positions, otherwise the conversation can result in an endless loop of debate. When the interests are visible, the team will naturally try to set goals that take them into account. As long as the final decisions regarding the project direction sufficiently address the different interests, the team will have a sense of ownership for the project, leading to the commitment conversation.

The Commitment conversation determines what project goal is going to be delivered and when. This requires that everyone involved in the project agrees on what is being delivered. This is only possible when they trust each other, have identified and determined sufficient mitigations for any concerns, and understand why this particular increment is the most important thing to deliver. Without achieving these first, people may be showing up, but they won't be fully participating in delivering the goal. Once the team commits to the desired goal, then work on the project beings, leading to the Accountability conversation.

The Accountability conversation communicates the progress of a project increment. It provides an opportunity for the team members to "radiate intent" and to receive feedback. This conversation is more about each person giving an account for their actions rather than being kept accountable for them. The structure of such a conversation can closely mirror the textbook standup questions: What is the current state of the project? What is planned next and the expected outcomes? what are the existing or upcoming obstacles? This conversation allows the project plan to adapt to new business constraints or missed user needs. It also creates a positive feedback loop that reinforces trust as conflicts are resolved through understandable compromises or the discovery of a more fundamental value for the business.

These 5 conversations and the analysis process looked very promising for overcoming the problems that I was facing. What made them immediately usable was that the first three conversations are all triggered when a conflict is perceived. However, the reasons describing why this analysis works gave me some cause for concern, which I'll be examining in another blog post.

What do you think? Is there possibly an even easier way to start improving trust within an organization? Are there additional conversations that could be added to this list? Is there a situation where taking a Speed of Trust course would be more beneficial? Let me know either in the comments or you can reach out to me on the various platforms where I'll be posting this.