On the Risk of Undetected Issues: I

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 detecteddamaged 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.  Next in this series  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!

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

Declaring Condition Red

High-performance teams have customary ways of working together that suit them, their organizations, and their work. But when emergencies happen, operating in business-as-usual mode damages teams — and the relationships between their people — permanently. To avoid this, train for emergencies.

The Weaver's Pathway

When projects near completion, we sometimes have difficulty letting go. We want what we've made to be perfect, sometimes beyond the real needs of customers. Comfort with imperfection can help us meet budget and schedule targets.

Internal Audits Without Pain

If adhering to established procedures is part of your job, you probably experience occasional audits. You can manage the pain of the experience by regarding audit preparation as part of the job. Because it is. Here are some tips for navigating audits.

Defect Streams and Their Sources

Regarding defects as elements of a stream provides a perspective that aids in identifying causes other than negligence. Examples of root causes are unfunded mandates, misallocation of the cost of procedure competence, and frequent changes in procedures.

Depth First or Breadth First?

When investigating candidate solutions to a problem, we tend to focus first on what we believe is the "best bet." But a more systematic approach can sometimes yield dramatic advantages by reducing the cost of the investigation and the time it requires.

See also Project Management and Critical Thinking at Work for more related articles.

Forthcoming issues of Point Lookout

Coming June 7: Toxic Disrupters: Tactics

Some people tend to disrupt meetings. Their motives vary, but they use techniques drawn from a limited collection. Examples: they violate norms, demand attention, mess with the agenda, and sow distrust. Response begins with recognizing their tactics. Available here and by RSS on June 7.

And on June 14: Pseudo-Collaborations

Most workplace collaborations produce results of value. But some collaborations — pseudo-collaborations — are inherently incapable of producing value, due to performance management systems, or lack of authority, or lack of access to information. Available here and by RSS on June 14.

Coaching services

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