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? rbreniVmZBWVuETQxCaAQner@ChacVAkodMrzqskaDKthoCanyon.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:
- FedEx, Flocks, and Frames of Reference
- Your point of view — or reference frame — affects what you see, and how you experience the world around you. By choosing a reference frame consciously, you can see things differently, and open a universe of new choices.
- Let's Revise Our Rituals
- Throughout the workday, we interact with each other on many levels. Some exchanges are so common and ritualized that we're no longer aware of them. If we revise these rituals slightly, we can add some zing to our lives.
- Some Limits of Root Cause Analysis
- Root Cause Analysis uses powerful tools for finding the sources of process problems. The approach has been so successful that it has become a way of thinking about organizational patterns. Yet, resolving organizational problems this way sometimes works — and sometimes fails. Why?
- Mitigating Outsourcing Risks: Part I
- Outsourcing internal processes modifies the usual risk configuration of those processes, but it also creates a special class of risks that are peculiar to the outsourcing relationship. What are some of those risks and what can we do about them?
- Action Item Avoidance
- In some teams, members feel so overloaded that they try to avoid any additional tasks. Here are some of the most popular patterns of action item avoidance.
See also Personal, Team, and Organizational Effectiveness, Problem Solving and Creativity and Effective Meetings for more related articles.
Forthcoming issues of Point Lookout
- Coming May 4: Just-In-Time Hoop-Jumping
- Securing approvals for projects, proposals, or other efforts is often called "jumping through hoops." Hoop-jumping can be time-consuming and frustrating. Here are some suggestions for jumping through hoops efficiently. Available here and by RSS on May 4.
- And on May 11: Characterization Risk
- To characterize is to offer a description of a person, event, or concept. Characterizations are usually judgmental, and usually serve one side of a debate. And they often make trouble. Available here and by RSS on May 11.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick for details at rbrenKOvQwXtAzFbecJSUner@ChacwmcpGJgcFQXedwnjoCanyon.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
- 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 whats 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's an upcoming date for this program:
- Sudoku Solutions, INK: A Simulation of a Project-Oriented Organization
- In this workshop, we simulate a company that solves Sudoku puzzles for its customers. Each puzzle is a project, solved by a project team led by a project manager. Team members hail from different parts of the organization, such as QA or the Department of Threes. Puzzles have different values, and the company must strive to meet revenue goals. The metaphor is uncanny. Lessons abound. Read more about this program. Here's an upcoming date for this program: