Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 14, Issue 51;   December 17, 2014: On the Risk of Undetected Issues: II

On the Risk of Undetected Issues: II

by

When things go wrong and remain undetected, trouble looms. We continue our efforts, increasing investment on a path that possibly leads nowhere. Worse, time — that irreplaceable asset — passes. How can we improve our ability to detect undetected issues?
A schematic representation of the blowout preventer that failed in the Deepwater Horizon incident

A schematic representation of the blowout preventer that failed in the Deepwater Horizon incident in 2010 in the Gulf of Mexico. In a report released in June of 2014, the U.S. Chemical Safety Board explained how undetected issues in the blowout preventer, including miswiring and design flaws, led to the disaster. The report also states that these issues could be present today in blowout preventers in widespread use throughout the industry, and that additional blowout preventer failures are possible. The CSB Web site offers a marvelous video, including computer animation of the failure. Image courtesy U.S. Chemical Safety Board.

As we saw last time, the difference between a risk and an issue is that risks are adverse events that might or might not happen. They are uncertain. On the other hand, issues are adverse events that have already arisen, or are certain to do so. Undetected issues are especially problematic when we treat them as risks, instead of mounting serious efforts to uncover them.

Let's now explore tactics for uncovering undetected issues. The general principle underlying all these approaches is an obvious one: Look for undetected issues in the places where you're most likely to find them.

Involve the customer in development — from the beginning
When developers and customers collaborate, they educate each other. Customers don't always know what they want or need. Sometimes they think they know, but they're mistaken. Still, customers can make valuable contributions to development processes, and participation in development helps refine their knowledge of what they want or need. The sooner this happens, the closer the product comes to delighting the customer. And when this mutual education doesn't happen — or when it happens too late — we sometimes discover issues only after the product is delivered.
Use what you're building — early
Actual usage is Actual usage is the method
most likely to expose the
problems that arise
in actual usage
the method most likely to expose the problems that arise in actual usage. Use what you're building (or parts thereof) as early as possible, or recruit actual users to do so. If needed, install placeholders for incomplete components. Placeholders are usually worth the investment, because early usage that exposes serious problems can reduce rework.
Exploit organizational history
In retrospectives, note the occurrence of undetected issues, the time it took before they were detected, and the cost of not having detected them promptly. Review the observations for patterns. Apply this information to future and ongoing efforts, checking for repetitions of these patterns, and incorporating into designs of products, services, projects, controls, and procedures, clever mechanisms that will signal the presence of any of these patterns. Use the cost information to set the levels of these investments.
Account for the effects of cognitive biases
Cognitive biases are patterns of thinking that lead to systematic deviations from rationality and objectivity. They can cause us, for example, to dismiss indications of undetected issues in products or projects. Learn about cognitive biases and incorporate safeguards into your processes to reduce the impact of cognitive biases.
Test with undetected issues in mind
Tests and inspections typically focus on determining whether the items tested meet requirements and quality standards. That isn't enough. If you have evidence of patterns of undetected issues in earlier work, broaden the testing focus to check for undetected issues. If you're unaware of patterns of undetected issues, make some brilliant guesses.

Your organization probably has a number of projects underway. Almost certainly there are some undetected issues. What are they? Where are they?  On the Risk of Undetected Issues: I First issue in this series  Go to top Top  Next issue: The Perils of Novel Argument  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:

The U.S. Capitol at nightNepotism, Patronage, Vendettas, and Workplace Espionage
Normally, you terminate or reassign team members who actually inhibit progress. Here are some helpful insights and tactics to use when termination or reassignment is impossible.
The first page of Thomas Paine's pamphlet Common SensePublish an Internal Newsletter
If you're responsible for an organizational effort with many stakeholders, communicating with them is important to success. Publishing an internal newsletter is a great way to keep them informed.
Assembling an IKEA chairSeven More Planning Pitfalls: III
Planning teams, like all teams, are vulnerable to several patterns of interaction that can lead to counter-productive results. Two of these relevant to planners are a cognitive bias called the IKEA Effect, and a systemic bias against realistic estimates of cost and schedule.
A working meeting with an auditorInternal 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.
An informal meeting in a loungeAllocating Action Items
From time to time in meetings we discover tasks that need doing. We call them "action items." And we use our list of open action items as a guide for tracking the work of the group. How we decide who gets what action item can sometimes affect our success.

See also Project Management for more related articles.

Forthcoming issues of Point Lookout

Mark Twain in 1907Coming July 16: Responding to Unwelcome Events
Unwelcome events have two kinds of effects on decision-makers. One set of effects appears as we respond to events that have actually occurred. Another set manifests itself as we prepare for unwelcome events that haven't yet occurred, but which might occur. Making a wrong decision in either case can be costly. Available here and by RSS on July 16.
A USA road sign indicating a winding road ahead, with an initial curve to the rightAnd on July 23: Microdelegation
Microdelegation is a style of delegation in which the delegator unintentionally communicates the task to the subordinate in such detail and so repetitively that the subordinate is offended. As a result of this delegation style, many subordinates feel distrusted or suspected of fraud or goldbricking. Available here and by RSS on July 23.

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.