Guidelines to Problem Solving and Decision Making

Guidelines to Problem Solving and Decision Making

• 1.
  Guidelines to ProblemSolving and Decision Making Gabriel BARINA
• 2.
  Overview Much ofwhat people do is solve problems and make decisions. Often, they are "under the gun", stressed and very short for time. Consequently, when they encounter a new problem or decision they must make, they react with a decision that seemed to work before. It's easy with this approach to get stuck in a circle of solving the same problem over and over again. Therefore, it's often useful to get used to an organized approach to problem solving and decision making. Not all problems can be solved and decisions made by the following, rather rational approach. However, the following basic guidelines will get you started. Don't be intimidated by the length of the list of guidelines. After you've practiced them a few times, they'll become second nature to you -- enough that you can deepen and enrich them to suit your own needs and nature.
• 3.
  1. Define theproblem This is often where people struggle. They react to what they think the problem is. Instead, seek to understand more about why you think there's a problem. Define the problem: (with input from yourself and others). Ask yourself and others, the following questions: What can you see that causes you to think there's a problem? Where is it happening? How is it happening? When is it happening? With whom is it happening? (HINT: Don't jump to "Who is causing the problem?" When we're stressed, blaming is often one of our first reactions. To be an effective manager, you need to address issues more than people.) Why is it happening? Write down a five-sentence description of the problem in terms of "The following should be happening, but isn't ..." or "The following is happening and should be: ..." As much as possible, be specific in your description, including what is happening, where, how, with whom and why. (It may be helpful at this point to use a variety of research methods.
• 4.
  1. Define theproblem Defining complex problems: If the problem still seems overwhelming, break it down by repeating steps 1-7 until you have descriptions of several related problems. Verifying your understanding of the problems: It helps a great deal to verify your problem analysis for conferring with a peer or someone else. Prioritize the problems: If you discover that you are looking at several related problems, then prioritize which ones you should address first. Note the difference between "important" and "urgent" problems. Often, what we consider to be important problems to consider are really just urgent problems. Important problems deserve more attention. For example, if you're continually answering "urgent" phone calls, then you've probably got a more "important" problem and that's to design a system that screens and prioritizes your phone calls.
• 5.
  1. Define theproblem Understand your role in the problem: Your role in the problem can greatly influence how you perceive the role of others. For example, if you're very stressed out, it'll probably look like others are, too, or, you may resort too quickly to blaming and reprimanding others. Or, you are feel very guilty about your role in the problem, you may ignore the accountabilities of others.
• 6.
  2. Look atpotential causes for the problem It's amazing how much you don't know about what you don't know. Therefore, in this phase, it's critical to get input from other people who notice the problem and who are effected by it. It's often useful to collect input from other individuals one at a time (at least at first). Otherwise, people tend to be inhibited about offering their impressions of the real causes of problems. Write down what your opinions and what you've heard from others. Regarding what you think might be performance problems associated with an employee, it's often useful to seek advice from a peer or your supervisor in order to verify your impression of the problem. Write down a description of the cause of the problem and in terms of what is happening, where, when, how, with whom and why.
• 7.
  3. Identify alternativesfor approaches to resolve the problem At this point, it's useful to keep others involved (unless you're facing a personal and/or employee performance problem). Brainstorm for solutions to the problem. Very simply put, brainstorming is collecting as many ideas as possible, then screening them to find the best idea. It's critical when collecting the ideas to not pass any judgment on the ideas -- just write them down as you hear them. (A wonderful set of skills used to identify the underlying cause of issues is Systems Thinking.)
• 8.
  4. Select anapproach to resolve the problem When selecting the best approach, consider: Which approach is the most likely to solve the problem for the long term? Which approach is the most realistic to accomplish for now? Do you have the resources? Are they affordable? Do you have enough time to implement the approach? What is the extent of risk associated with each alternative?
• 9.
  5. Plan theimplementation of the best alternative (this is your action plan) Carefully consider "What will the situation look like when the problem is solved?" What steps should be taken to implement the best alternative to solving the problem? What systems or processes should be changed in your organization, for example, a new policy or procedure? Don't resort to solutions where someone is "just going to try harder". How will you know if the steps are being followed or not? (these are your indicators of the success of your plan) What resources will you need in terms of people, money and facilities? How much time will you need to implement the solution? Write a schedule that includes the start and stop times, and when you expect to see certain indicators of success. Who will primarily be responsible for ensuring implementation of the plan? Write down the answers to the above questions and consider this as your action plan. Communicate the plan to those who will involved in implementing it and, at least, to your immediate supervisor.
• 10.
  6. Monitor implementationof the plan Monitor the indicators of success: Are you seeing what you would expect from the indicators? Will the plan be done according to schedule? If the plan is not being followed as expected, then consider: Was the plan realistic? Are there sufficient resources to accomplish the plan on schedule? Should more priority be placed on various aspects of the plan? Should the plan be changed?
• 11.
  7. Verify ifthe problem has been resolved or not One of the best ways to verify if a problem has been solved or not is to resume normal operations in the organization. Still, you should consider: What changes should be made to avoid this type of problem in the future? Consider changes to policies and procedures, training, etc. Lastly, consider "What did you learn from this problem solving?" Consider new knowledge, understanding and/or skills. Consider writing a brief memo that highlights the success of the problem solving effort, and what you learned as a result. Share it with your supervisor, peers and subordinates.
• 12.
  Rational Versus OrganicApproach to Problem Solving -> Rational A person with this preference often prefers using a comprehensive and logical approach similar to the guidelines in the above section. For example, the rational approach, described below, is often used when addressing large, complex matters in strategic planning. Define the problem. Examine all potential causes for the problem. Identify all alternatives to resolve the problem. Carefully select an alternative. Develop an orderly implementation plan to implement that best alternative. Carefully monitor implementation of the plan. Verify if the problem has been resolved or not. A major advantage of this approach is that it gives a strong sense of order in an otherwise chaotic situation and provides a common frame of reference from which people can communicate in the situation. A major disadvantage of this approach is that it can take a long time to finish. Some people might argue, too, that the world is much too chaotic for the rational approach to be useful.
• 13.
  Rational Versus OrganicApproach to Problem Solving -> Organic Some people assert that the dynamics of organizations and people are not nearly so mechanistic as to be improved by solving one problem after another. Often, the quality of an organization or life comes from how one handles being “on the road” itself, rather than the “arriving at the destination.” The quality comes from the ongoing process of trying, rather than from having fixed a lot of problems. For many people it is an approach to organizational consulting.
• 14.
  Rational Versus OrganicApproach to Problem Solving -> Organic A major advantage of the organic approach is that it is highly adaptable to understanding and explaining the chaotic changes that occur in projects and everyday life. It also suits the nature of people who shun linear and mechanistic approaches to projects. The major disadvantage is that the approach often provides no clear frame of reference around which people can communicate, feel comfortable and measure progress toward solutions to problems.