Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 14, Issue 50;   December 10, 2014: On the Risk of Undetected Issues: I

On the Risk of Undetected Issues: I

by

In complex projects, things might have gone wrong long before we notice them. Noticing them as early as possible — and addressing them — is almost always advantageous. How can we reduce the incidence of undetected issues?
The damaged Apollo 13 Service Module, as seen from the command module

The damaged Apollo 13 Service Module, as seen from the command module. The damage was caused when an oxygen tank exploded as a result of damaged insulation on a wire powering a sensor inside the tank, according to the findings of the Apollo 13 Review Board, which conducted a post-mission investigation. In effect, the investigation discovered the undetected issue, even though the Board did not have access to the Service Module, which was destroyed on re-entry into Earth's atmosphere. The Board's analysis demonstrates that, in principle, the issue could have been detected prior to launch. Photo courtesy U.S. National Aeronautics and Space Administration.

Language and terminology are the tools we use to express our thoughts. But language and terminology can do much more — they can actually influence the way we think. And that influence isn't always helpful.

Consider risk. In project management, and fields closely related, there's an ongoing conversation about differences between the term risk and the term issue. Although disagreement and confusion persist, most people agree about two points. First, a risk is an event or condition that might or might not occur, while an issue is an event or condition that has already occurred, or which will certainly occur. Second, both risks (if they occur) and issues have adverse consequences for objectives.

The principal difference between risks and issues is that risks have probability less than 100%; issues have probability 100%.

This distinction leaves at least one situation uncovered: what do we call adverse events that have occurred (or which certainly will occur), but which as yet have escaped notice? I call them undetected issues. Undetected issues can be problematic, because although we treat them as risks, they aren't risks at all.

How does all this relate to our use of language? When we think of undetected issues as risks, we tend to regard them as not yet having happened, as opposed to having happened and not yet having been detected. Thinking about them this way can be problematic. For example, thinking of a condition as not yet having happened can lead to dismissing as pointless — or not worthwhile — any plan to determine whether or not it has already occurred. Why search for something that hasn't happened?

On the other hand, we might be more willing to expend resources to uncover the presence of undetected issues. When we do search, we're more likely to find them.

For example, consider the mission of Apollo XIII. A liquid oxygen tank exploded during Hour 55 of the mission due to When we think of undetected issues
as risks, we tend to regard them
as not yet having happened, as
opposed to having happened
and not yet having been detected
damaged insulation on wires inside the tank, which resulted from procedures executed years earlier. Before installation in the vehicle, the damage was a risk. After installation, it was not a risk at all — it was an undetected issue. And post-incident, a thorough investigation did uncover the undetected issue. How would the mission have been affected if NASA — before launch — had conducted a more thorough search for undetected issues?

Many project teams now develop risk management plans. Few of these plans address the risk of undetected issues. If we think clearly about the distinctions among issues, risks, undetected issues, and the risk of undetected issues, we're more likely to include mechanisms in the design of our systems — and procedures, schedule, and resources in the design of our projects — that facilitate detecting as-yet-undetected issues.

We'll explore some practices that can help teams uncover undetected issues next time.  On the Risk of Undetected Issues: II Next issue in this series  Go to top Top  Next issue: On the Risk of Undetected Issues: II  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!

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

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 Project Management:

US Space Shuttle LaunchSome Causes of Scope Creep
When we suddenly realize that our project's scope has expanded far beyond its initial boundaries — when we have that how-did-we-ever-get-here feeling — we're experiencing the downside of scope creep. Preventing scope creep starts with understanding how it happens.
A fancy diagram of the kind that often accompanies management fadsWhy Do Business Fads Form?
The rise of a business fad is due to the actions of both its advocates and adopters. Understanding the interplay between them is essential for successful resistance.
Dunlin flock at Nelson Lagoon, AlaskaNonlinear Work: Internal Interactions
In this part of our exploration of nonlinear work, we consider the effects of interactions between the internal elements of an effort, as distinguished from the effects of external changes. Many of the surprises we encounter in projects arise from internals.
Magic Lantern Slide of a dog jumping through a hoopJust-In-Time Hoop-Jumping
Securing approvals for projects, proposals, or other efforts is often called "jumping through hoops." Hoop-jumping can be time-consuming and frustrating. Here are some suggestions for jumping through hoops efficiently.
Tuckman's stages of group developmentTuckman's Model and Joint Leadership Teams
Tuckman's model of the stages of group development, applied to Joint Leadership Teams, reveals characteristics of these teams that signal performance levels less than we hope for. Knowing what to avoid when we designate these teams is therefore useful.

See also Project Management for more related articles.

Forthcoming issues of Point Lookout

Photo of Jack Webb as Sergeant Joe Friday from the television series DragnetComing September 3: Contributions in Team Meetings: Advocating
An agenda in the form of an ordered list of topics might not provide an appropriate framework for a given meeting. For example, if A depends on B, and B depends on A, we must find a way to discuss A and B together in some orderly fashion. Here are some alternatives to linear, ordered agendas. Available here and by RSS on September 3.
A Venn Diagram of three setsAnd on September 10: Contributions in Team Meetings: Scoping
Some meetings focus on solving specific problems. We call them "working sessions." More often, we delegate problem solving to task teams, while meetings wrestle with the difficult task of identifying or "scoping" problems rather than solving them. Scoping discussions can be perilous. Available here and by RSS on September 10.

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:

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 Bluesky, 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.