Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 21, Issue 22;   June 2, 2021: The Expectation-Disruption Connection

The Expectation-Disruption Connection

by

In technology-dependent organizations, we usually invest in infrastructure as a means of providing new capability. But mitigating the risk of disruption is a more powerful justification for infrastructure investment, if we understand the Expectation-Disruption Connection.
Out-of-service gas pumps during the Colonial Pipeline shutdown

Out-of-service gas pumps during the Colonial Pipeline shutdown at a Wawa station in Oak Hill, Fairfax County, Virginia. Colonial had paid the attackers their ransom shortly after the attack began. The attackers sent Colonial a software application that would repair the compromised systems, but it operated so slowly that the pipeline operations remained shut down for five days. Image (cc) Famartin, courtesy Wikipedia

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? Go to top Top  Next issue: Self-Imposed Constraints  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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

Comprehensive list of all citations from all editions of Point Lookout
[Mish 2005]
Frederick C. Mish, ed. Merriam-Webster's Collegiate Dictionary, 11th edition. Springfield, Massachusetts: Merriam-Webster, Inc., 2005. Back
[Robertson 2020]
Derek Robertson. "Flint Has Clean Water Now. Why Won't People Drink It?" Politico December 23, 2020. Available here. Back
[Penney 2021]
Veronica Penney. "How Texas' Power Generation Failed During the Storm, in Charts," The New York Times, February 19, 2021. Available here. Back
[Shear 2021]
Michael D. Shear, Nicole Perlroth, and Clifford Krauss. "Colonial Pipeline Paid Roughly $5 Million in Ransom to Hackers," The New York Times, May 13, 2021. Available here. Back

Your comments are welcome

Would you like to see your comments posted here? rbrentSgXnAlNVWlhxNIJner@ChacAtZoEYrrmofzZnjPoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

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:

FeedbackHe's No Longer Here
Sometimes we adopt inappropriate technologies, or we deploy unworkable processes, largely because of the political power of their advocates, and despite widespread doubts about the wisdom of the moves. Strangely, though, the decisions often stick long after the advocates move on. Why? And what can we do about it?
R.M.S. Lusitania coming into port, possibly in New York.Obstacles to Finding the Reasons Why
When we investigate what went wrong, we sometimes encounter obstacles. Interviewing witnesses and participants doesn't always uncover the reasons why. What are these obstacles?
A beekeeper at work, wearing safety equipmentContrary Indicators of Psychological Safety: II
When we begin using new tools or processes, we make mistakes. Practice is the cure, but practice can be scary if the grace period for early mistakes is too short. For teams adopting new methods, psychological safety is a fundamental component of success.
A white water rafting team completes its courseWhite Water Rafting as a Metaphor for Group Development
Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups.
A monarch butterfly emerges from its chrysalisThe Storming Puzzle: I
Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies to today's task-oriented work groups — if we adapt our understanding of it. If we don't adapt, the model appears to conflict with reality.

See also Organizational Change and Organizational Change for more related articles.

Forthcoming issues of Point Lookout

A man in despair, as one might be following a layoffComing April 2: Mitigating the Trauma of Being Laid Off
Trauma is an emotional response to horrible events — accidents, crimes, disasters, physical abuse, emotional abuse, gross injustices — and layoffs. Layoff trauma is real. Employers know how to execute layoffs with compassion, but some act out of cruelty. Know how to defend yourself. Available here and by RSS on April 2.
A common image of bullying in actionAnd on April 9: Defining Workplace Bullying
When we set out to control the incidence of workplace bullying, problem number one is defining bullying behavior. We know much more about bullying in children than we do about adult bullying, and more about adult bullying than we know about workplace bullying. Available here and by RSS on April 9.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrentSgXnAlNVWlhxNIJner@ChacAtZoEYrrmofzZnjPoCanyon.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:

Reprinting this article

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

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.