Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 10, Issue 30;   July 28, 2010: Exploiting Failed Ideas

Exploiting Failed Ideas

by

When the approach you've been using fails, how do you go about devising Plan B? Or Plan C? Here are some ways to find new approaches by examining failures.
Senator Carter Glass (Democrat of Virginia) and Representative Henry B. Steagall (Democrat, Alabama Third), the co-sponsors of the Glass-Steagall Act

Senator Carter Glass (Democrat of Virginia) and Representative Henry B. Steagall (Democrat, Alabama Third), the co-sponsors of the Glass-Steagall Act, also known as the Banking Act of 1933. It was this law that established the Federal Deposit Insurance Corporation, which to this day insures deposits at U.S. banking institutions. This insurance mechanism is generally regarded as having prevented bank runs, which were common in the years prior to the adoption of Glass-Steagall, and in most if not all economic panics in the decades prior to the Great Depression. It was an examination of these panics and the Depression, and their causes, that led to the idea of deposit insurance as a means of breaking the feedback loop that had been intensifying economic slowdowns. Other portions of Glass-Steagall, notably those limiting the activities that insured institutions were permitted to undertake, were repealed in 1999. Within eight years of that repeal, the U.S. economy experienced its most intense contraction since the passage of Glass-Steagall, a contraction from which it and the world have not yet recovered. It's possible — even likely — that the repeal of Glass-Steagall is a failed idea. Perhaps the recently enacted Dodd-Frank Wall Street Reform and Consumer Protection Act is a step toward harvesting some learning from that error. Photo courtesy Wikimedia.

Your team is stuck. The approach you were using has failed, or it can't possibly be finished in time — if ever. A solution is needed yesterday. So you assemble a small group to generate some new options. The most popular method in such situations is brainstorming, and for many of us, it's the only method we know. As good as it is, there are techniques we can use to make brainstorms even more productive. One method works by exploiting failed ideas.

By examining the ideas we've already tried or rejected, we can generate new ideas we might have missed otherwise. And we can do this within the familiar structure of a brainstorming session.

Here's an example. Suppose we have a blown out oil well on the floor of the Gulf of Mexico, and it's gushing oil all over the ocean. Hey, it could happen. We want to collect all the spilled oil. We've tried burning it, dragging booms behind boats, and skimming it off the surface into supertankers, but nothing has worked.

So we ask, what's fundamentally wrong with these approaches? Actually, it's basic geometry. These methods are all point-oriented — the fire we light burns at a single point, the mouth of the boom loop we drag behind the boats is narrow, as is the prow of the supertanker skimmer. Compared to the surface of the Gulf, these are points, while the oil is spread unevenly over a big part of the ocean surface. To capture material spread over a surface, we need a surface-oriented approach, not a point-oriented approach.

A more effective method might involve tens or hundreds of thousands of small, possibly robotic, skimmers working close enough to mother ships to free them of storage and separation functions. In effect, a fleet of oil-seeking mega-Roombas.

Luckily, the problems you face are probably smaller scale than that. Here are some questions that will generate ideas using what is already known about failures.

About failure
Why have the ideas we've tried failed? If we were to try them again, would they fail the same way or would they fail in new ways? What did their failures have in common?
About new ideas
How does this new idea Why have the ideas we've tried
failed? If we were to try
them again, would they
fail the same way?
differ from others we've tried or rejected? If it doesn't differ by much, how can we make it more novel?
About costs
How expensive is exploring this idea? How can we make exploration cheaper? Can we pilot it? How expensive would it be to implement?
About completeness
What parts of the problem would this idea resolve? What parts of the problem would remain? Why?
About effectiveness
If we implement this idea would it move us forward? What can we change about this idea to make it even more effective?

You get the idea. Now, if you were to try to exploit failed ideas, and the suggestions above all failed, what else could you do? Go to top Top  Next issue: On Being the Canary  Next Issue

101 Tips for Effective MeetingsDo you spendyour days scurrying from meeting to meeting? Do you ever wonder if all these meetings are really necessary? (They aren't) Or whether there isn't some better way to get this work done? (There is) Read 101 Tips for Effective Meetings to learn how to make meetings much more productive and less stressful — and a lot more rare. Order Now!

Your comments are welcome

Would you like to see your comments posted here? rbrenPKTcYOJfhpSuGmqGner@ChacrQWiormtaTsJUNkWoCanyon.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.

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 Effective Meetings:

Out of the actionThe Shape of the Table
Not only was the meeting running over, but it now seemed that the entire far end of the table was having its own meeting. Why are some meetings like this?
The Thinker PowerPointingThink Before You PowerPoint
Microsoft PowerPoint is a useful tool. Many of us use it daily to create presentations that guide meetings or focus discussions. Like all tools, it can be abused — it can be a substitute for constructive dialog, and even for thought. What can we do about PowerPoint abuse?
Carrot and stickIrrational Self-Interest
When we try to influence others, especially large groups or entire companies, we sometimes create packages of incentives and disincentives that are intended to affect behavior. These strategies usually assume that people make choices on rational grounds. Is this assumption valid?
A single-strand knotTangled Thread Troubles
Even when we use a facilitator to manage a discussion, managing a queue for contributors can sometimes lead to problems. Here's a little catalog of those difficulties.
Barack Obama, 44th President of the United StatesSpeak for Influence
Among the factors that determine the influence of contributions in meetings are the content of the contribution and how it fits into the conversation. Most of the time, we focus too much on content and not enough on fit.

See also Effective Meetings and Problem Solving and Creativity for more related articles.

Forthcoming issues of Point Lookout

The end of the line for a railroad trackComing May 30: Chronic Peer Interrupters: I
When making contributions to meeting discussions, we're sometimes interrupted. Often, the interruption is beneficial and saves time. But some people constantly interrupt their peers or near peers, disrespectfully, in a pattern that compromises meeting outcomes. How can we deal with chronic peer interrupters? Available here and by RSS on May 30.
Mohandas K. Ghandi, in the 1930sAnd on June 6: Chronic Peer Interrupters: II
People use a variety of tactics when they're interrupted while making contributions in meetings. Some tactics work well, while others carry risks of their own. Here's Part II of a little survey of those tactics. Available here and by RSS on June 6.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenAuJYHMfHrjScErPiner@ChacQKhFkkAlpwgvTGxXoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program. Here's a date for this program:

Technical Debt Management: Making the Business Case
This Technical Debt Management: Making the Business Caseprogram outlines the steps necessary for deploying a program for rational management of technical debt. For many organizations, adopting a program for rationally managing technical debt entails organizational change. And unlike some organizational changes, this one touches almost everyone in the organization, because technical debt isn't merely a technical problem. Technical debt manifests itself in technological assets, to be sure, but its causes are rarely isolated to the behavior and decisions of engineers. We can't resolve the problem of chronically excessive levels of technical debt by changing the behavior of engineers alone. Technical debt is the symptom, not the problem. In this program we outline the essential elements of an effective business case for adopting a rational technical debt management program. But this business case, unlike many business cases, cannot be captured in a document. We must make the case not only at the leadership level of the organization, but also at the level of the individual contributor. Everyone must understand. Everyone must contribute. We explore five issues that make technical debt so difficult to manage, and develop five guidelines for designing technical debt management strategies for the modern enterprise. Read more about this program. Here's a date for this program:

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's a date for this program:

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program. Here's a date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ 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.