Usually, when solving problems, generating candidate solutions isn't difficult. What is difficult is finding hidden ideas, or sorting through ideas to isolate the most promising ones. Here's a little catalog of ideas for sorting ideas.
- Examine boring ideas
- Look for ideas that seem workable but boring. Their dreary nature can lead to a bias against them. Few people want to work on them, and securing resources for them might be difficult because they're so unexciting. But workability is what counts. Set your own bias aside, and seek ways to persuade others to do the same.
- Examine unoriginal ideas
- Lack of originality is another source of bias against ideas. Look for an idea that someone has already tried. If it proved unworkable, ask why. If those reasons are still in place, can you remove them or skirt them somehow?
- Examine inelegant ideas
- Because inelegance can be more repulsive than workability can be attractive, we often reject inelegant but workable ideas. To recruit supporters, or to secure resources, emphasize that success is a form of beauty.
- Examine politically encumbered ideas
- Some Some perfectly workable ideas
are rejected, or regarded as
unworkable, when they
carry political baggageperfectly workable ideas are rejected, or regarded as unworkable, when they carry political baggage. Perhaps they offend someone powerful, or they don't conform to the preferences of another powerful person. In these cases, the problem to be solved is political in nature. Focus not on the original problem, but instead on the politics. - Examine expensive ideas
- Yet another source of bias against ideas is their apparent cost, or their apparent need for skills and knowledge that are in short supply. In these cases, work on resolving the resource issues. What can you do to reduce costs? How can you be clever about finding people who can do the job?
- Examine crazy ideas
- Ideas with reputations for being obviously crazy sometimes inherit their reputations from the people who originated them, rather than by earning their reputations by being truly crazy. Look carefully at the idea itself, setting aside what you know about its originator. Is the idea itself truly crazy?
- Examine past successes
- When you finally solved a problem, what was the critical element that led to a solution? By examining your history, you might find a pattern among those critical elements. Patterns can arise from weakness in problem-solving skills, or unfamiliarity with the problem domain, or the culture in which you work. If you can identify the pattern, you can use it to guide a search for solutions to the current problem.
Finally, deal with your own biases by intentionally searching for ideas you regard as crazy. This stance helps to relax the constraints that conceal solutions. When you find an intriguingly crazy solution, ask, "What makes it crazy?" Can you adjust it so that its craziness is no longer obvious? Is there anything about it that could be useful? 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
Would you like to see your comments posted here? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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.
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 Problem Solving and Creativity:
- Make Space for Serendipity
- Serendipity in project management is rare, in part, because we're under too much pressure to see it.
If we can reduce the pressure, wonderful things happen.
- How to Foresee the Foreseeable: Recognize Haste
- When trouble arises after we commit to a course of action, we sometimes feel that the trouble was foreseeable.
One technique for foreseeing the foreseeable depends on recognizing haste in the decision-making process.
- Start Anywhere
- Group problem-solving sessions sometimes focus on where to begin, even when what we know about the problem
is insufficient for making such decisions. In some cases, preliminary exploration of almost any aspect
of the problem can be more helpful than debating what to explore.
- Disjoint Concept Vocabularies
- In disputes or in problem-solving sessions, when we can't come to agreement, we often attribute the
difficulty to miscommunication, histories of disagreements, hidden agendas, or "personality clashes."
Sometimes the cause is much simpler. Sometimes the concept vocabularies of the parties have too little
in common.
- The McNamara Fallacy
- The McNamara Fallacy is the idea that measuring properly chosen attributes of inputs and outputs provides
all we need for decisions about organizational and human performance. And we can safely ignore anything
that can't be measured. It doesn't work.
See also Problem Solving and Creativity and Problem Solving and Creativity for more related articles.
Forthcoming issues of Point Lookout
- Coming December 11: White Water Rafting as a Metaphor for Group Development
- Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.
- And on December 18: Subgrouping and Conway's Law
- When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed