The Expectation-Disruption Connection

In an episode of The West Wing, a television drama series about the U.S. Presidency, the "President" comments about the consequences of a possible outbreak of Mad Cow Disease. He says, "The most costly disruptions always happen when something we take completely for granted stops working for a minute." To take for granted is "to assume as true, real, or expected," or "to value too lightly." [Mish 2005] In this case, the President is remarking on the societal disruption that could occur if the U.S. beef industry "stops working." And he's saying that the disruption would be costly because "we take [the beef industry] completely for granted."

Recent events have provided examples of the power of the "President's" observation: the Flint water crisis, which began in 2014 and is ongoing [Robertson 2020]; the Texas power generation failure of winter 2020-2021 [Penney 2021]; and the COVID-19 pandemic, which began in 2019. These three examples illustrate how we took for granted, respectively, the water we drink, the electric power we use, and the air we breathe.

Although these examples are regional or global in scale, an inquiry into possible organizational analogs can be fruitful. In this post I offer two insights for organizations based on the connection between Disruptions and our Expectations.

Disruptions point the way to needed innovations

In May of 2021, extortionists forced the shutdown of pipelines owned and operated by Colonial Pipeline Company. [Shear 2021] The company paid a ransom of approximately USD 5 million to resume operations after a five-day disruption, which resulted in gasoline shortages along the East coast of the United States.

The incident illustrates — not for the first time — that many operators of network infrastructure within companies incorrectly expect that their equipment is safe from cyberattack. One way to address this problem is to expect individual companies to educate themselves about cyberdefense. That is the current approach, and it usually emphasizes technological improvements. This approach places cyberdefense directly in conflict with short-term financial results.

As the Colonial "The most costly disruptions always happen
when something we take completely for
granted stops working for a minute."
— "President Bartlet" of the West Wing
Pipeline incident demonstrates, the current approach is not working well. A more innovative approach would recognize that industry as a whole has a cybersecurity problem. The innovation that's needed here is one that guides individual companies to work more collaboratively to enhance cybersecurity. This problem is perhaps best addressed at a national or global scale.

Expectations indicate unrecognized risks

For any given organizational initiative, if we can identify an expectation, we can then ask, "What if events defy our expectation?" The answer to that question can be expressed as a risk for that initiative. For example, consider a project whose objective is extending a software asset by adding new capabilities. We might expect that if we supply enough resources and time, the project will be successful. Moreover, we might expect that subsequent projects of a similar nature will also be successful.

But such expectations haven't always aligned with events. Over time, repeatedly extending software assets has resulted in increased maintenance costs and general difficulty in making enhancements. The phenomenon is known as software brittleness. Software project managers would do will to regard increased software brittleness as a risk of projects whose objectives are extension of existing assets — a risk that must be mitigated.

Disruptions are evident when they occur, but expectations can remain unrecognized for indefinite periods. That's why investing effort in identifying unrecognized expectations can be so fruitful. As an example, asking questions of the form, "What if X is removed from this situation" can help. What else can you do to find the expectations of yours that can connect to disruptions?  Top    Next Issue

Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Footnotes

Your comments are welcome

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Organizational Change:

Look Before You Leap

When we execute complex organizational change, we sometimes create disasters. It's ironic that even in companies that test their products thoroughly, we rarely test organizational changes before we "roll them out." We need systematic methods for discovering problems before we execute change efforts. One approach that works well is the simulation.

The Ties that Bind

Changing anything in an organization reveals how it's connected to its people, to its processes, to its facilities, and to the overall context. Usually, these connections reach out much further into the organization than we imagine.

Good Change, Bad Change: II

When we distinguish good change from bad, we often get it wrong: we favor things that would harm us, and shun things that would help. When we do get it wrong, we're sometimes misled by social factors.

When Change Is Hard: II

When organizational change is difficult, we sometimes blame poor leadership or "resistance." But even when we believe we have good leadership and the most cooperative populations, we can still encounter trouble. Why is change so hard so often?

Deciding to Change: Trusting

When organizations change by choice, people who are included in the decision process understand the issues. Whether they agree with the decision or not, they participate in the decision in some way. But not everyone is included in the process. What about those who are excluded?

See also Organizational Change and Problem Solving and Creativity for more related articles.

Forthcoming issues of Point Lookout

Coming November 30: Avoiding Speed Bumps: II

Many of the difficulties we encounter when working together don't create long-term harm, but they do cause delays, confusion, and frustration. Here's Part II of a little catalog of tactics for avoiding speed bumps. Available here and by RSS on November 30.

And on December 7: Reaching Agreements in Technological Contexts

Reaching consensus in technological contexts presents special challenges. Problems can arise from interactions between the technological elements of the issue at hand, and the social dynamics of the group addressing that issue. Here are three examples. Available here and by RSS on December 7.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenZLkFdSHmlHvCaSsuner@ChacbnsTPttsdDaRAswloCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info