On the Risk of Undetected Issues: II

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 usagethe 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?   First issue 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.

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:

Communication Traps for Virtual Teams: II

Communication can be problematic for any team, especially under pressure. But virtual teams face challenges that are less common in face-to-face teams. Here's Part II of a little catalog with some recommendations.

How to Make Good Guesses: Strategy

Making good guesses — guessing right — is often regarded as a talent that cannot be taught. Like most things, it probably does take talent to be among the first rank of those who make conjectures. But being in the second rank is pretty good, too, and we can learn how to do that.

Why Scope Expands: I

Scope creep is depressingly familiar. Its anti-partner, spontaneous and stealthy scope contraction, has no accepted name, and is rarely seen. Why?

Design Errors and Group Biases

Design errors can cause unwanted outcomes, but they can also lead to welcome surprises. The causes of many design errors are fundamental attributes of the way groups function. Here is Part II of our exploration.

The Ultimate Attribution Error at Work

When we attribute the behavior of members of groups to some cause, either personal or situational, we tend to make systematic errors. Those errors can be expensive and avoidable.

See also Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming June 25: Meandering Monologues in Meetings: Engagement

In a meeting, a meandering monologue has taken over when someone speaks at length with no sign of coming to a clear point, and little of evident value. This behavior reduces engagement on the part of other attendees, thereby limiting the meeting's value to the organization. Available here and by RSS on June 25.

And on July 2: The True Costs of Contractors

Among the more commonly cited reasons for hiring contractors instead of direct employees is cost savings. But are these savings real? Direct compensation, including perks and benefits, might favor the contractor arrangement, but indirect costs tell another story. Available here and by RSS on July 2.

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