
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? 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
Would you like to see your comments posted here? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend me your comments by email, or by Web form.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.
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:
Is It Really Resistance?
- The term resistance, as used in the context of organizational change, describes our reluctance
to abandon the status quo. But it's a loaded term, because it devalues that reluctance. When we approach
change with this model of reluctance in mind, we sabotage our own efforts.
Piling Change Upon Change: Management Credibility
- When leaders want to change organizational directions, processes, or structures, some questions arise:
How much change is too much change? Here's a look at one constraint: the risk to management credibility.
Organizational Roots of Toxic Conflict
- When toxic conflict erupts in a team, cooperation ends and person-to-person attacks begin. Usually we
hold responsible the people involved. But in some cases, the organization is the root cause, and then
replacing or disciplining the people might not help.
On Anticipating Consequences
- Much of what goes wrong when we change systems to improve them falls into a category we call unanticipated
consequences. Even when we lack models that can project these results accurately, morphological analysis
can help us avoid much misery.
The Storming Puzzle: Patterns and Antipatterns
- Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing,"
applies to today's task-oriented work groups, if we understand the six principles that govern transitions
from one stage to another. Here are some examples.
See also Organizational Change for more related articles.
Forthcoming issues of Point Lookout
Coming September 24: Time Is Not a Resource
- In the project management community, it's often said that time is the most precious resource. Although time is indeed precious, to regard it as a resource — like finance, equipment, or people — can be a dangerous mistake. Time is not a resource. Available here and by RSS on September 24.
And on October 1: On the Risks of Obscuring Ignorance
- A common dilemma in knowledge-based organizations: ask for an explanation, or "fake it" until you can somehow figure it out. The choice between admitting your own ignorance or obscuring it can be a difficult one. It has consequences for both the choice-maker and the organization. Available here and by RSS on October 1.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
