Problem Defining and Problem Solving
by Rick Brenner
Sometimes problem-solving sessions are difficult because we get started solving a problem before we know what problem we're solving. Understanding the connection between stakeholders, problem solving, and problem defining can reduce conflict and produce better solutions.
The three of them piled out of the taxi and ran through the rain across the plaza, past the Jersey barriers, to the revolving doors. Hal and Sam let Julie go inside first. Then, highly motivated by the now-pelting rain, Hal and Sam crammed themselves into the next chamber of the doors, and exploded out into the lobby, not quite drenched.
"Used to be a canopy here," said Hal. "They took it out when they put in the Jersey barriers. Must be a security thing."
Sam was wet and fuming: "There has to be a drier way to increase security."
Sam might be right. It's likely that when the security staff addressed the problem of enhancing security, they gave relatively more importance to security considerations than to the inconvenience of building users in inclement weather. They defined the problem they were solving, and (perhaps) failed to account for the problems their solution generated for some stakeholders.
It's a common pattern. Here are some guidelines for defining and solving problems.
- Definition and solution are in a dance
- Definition and solution aren't sequential — they dance together. Progress on solutions can expose unanticipated issues. Even partial solutions can produce discoveries that can actually change what people perceive to be the problem.
- Solution and stakeholders are in a dance
- Any solution can create new problems and/or new stakeholders. Anticipate who these new people might be, and work with them now, despite the added cost. Early involvement is preferable, because involvement after deployment of the solution might be even more expensive.
- Stakeholders and definition are in a dance
- Partial solutions expose new Exploring any one of
Definition, Solution, and
Stakeholders can reveal
new elements of
the other twostakeholders with new insights and perceptions, and they can change the problem definition. This link completes a cycle involving Definition, Solution, and Stakeholders. Their dance can be confusing, but it's more confusing to believe that you have a definition and a solution when you don't. Keep going around the loop until things stabilize.
- Rarely is there a "best" way
- Most of the problems we deal with have no "best" solution. Yet, we spend much of our energy searching for the best solution, even when nobody actually told us to find the best solution. And even if a best solution does exist, the cost of finding it (and proving that we've done so) can be prohibitive. Good enough usually is.
- Optimality requires a metric
- If you're expected to find the "best" solution, be certain that you have a well-defined metric that provides unambiguous comparisons. Without one, "best" has no concrete meaning, and you actually have two problems instead of one. You have to find both a metric and a solution.
Applying these guidelines involves not only the problem you're trying to solve, but also addressing problems in your problem solving process. Beware: tackling both at once can be tricky. 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? rbrenuawslBGdMJzBewODner@ChaciWjGZAqSEaiDwBfDoCanyon.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.
More articles on Personal, Team, and Organizational Effectiveness:
- Appreciate Differences
- In group problem solving, diversity of opinion and healthy, reasoned debate ensure that our conclusions take into account all the difficulties we can anticipate. Lock-step thinking — and limited debate — expose us to the risk of unanticipated risk.
- Taming the Time Card
- Filling out time cards may seem maddeningly trivial, but the data they collect can be critically important to project managers. Why is it so important? And what does an effective, yet minimally intrusive time reporting system look like?
- Status-Report as a Second Language
- Sometimes, the clichés the losing team's players feed to sports reporters can have hidden meaning. So it is with Project Status Reports, especially for projects in trouble.
- Should I Keep Bailing or Start Plugging the Leaks?
- When we're flooded with problems, and the rowboat is taking on water, we tend to bail with buckets, rather than take time out to plug the leaks. Here are some tips for dealing with floods of problems.
- Bottlenecks: Part I
- Some people take on so much work that they become "bottlenecks." The people around them repeatedly find themselves stuck, awaiting responses or decisions. Why does this happen and what are the costs?
See also Personal, Team, and Organizational Effectiveness, Problem Solving and Creativity and Effective Meetings for more related articles.
Forthcoming Issues of Point Lookout
- Coming July 8: Ethical Debate at Work: Part I
- When we decide issues at work on any basis other than the merits, we elevate the chances of making bad decisions. Here are some guidelines for ethical debate. Available here and by RSS on July 8.
- And on July 15: Ethical Debate at Work: Part II
- Outcomes of debates at work sometimes favor one party, not only at the expense of the other or others, but also at the expense of the organization. Here's Part II of a set of guidelines for steering debates toward wise outcomes. Available here and by RSS on July 15.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick for details at rbrenZCCKQKKrGYURscNvner@ChacZFgchgDTFzfEQWRFoCanyon.com
or (617) 491-6289, 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
- Ten Project Management Fallacies: The Power of Avoiding Hazards
- Most of what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's an upcoming date for this program:
- Managing in Fluid Environments
- Most people now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know what's coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help managers who work in fluid environments. Read more about this program. Here are some upcoming dates for this program:
- The Race to the South Pole: The Organizational Politics of Risk Management
- On 14 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. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in risk management, its application to organizational efforts, and how workplace politics enters the mix. A fascinating and refreshing look at risk management from the vantage point of history and workplace politics. Read more about this program. Here's an upcoming date for this program: