Solving Problems
In a recent piece I discussed non-technological strategies that Microsoft could follow to solve some computer security problems. A follow up email and a number of comments prompted me to think about commenting on the problem solving process.
I have been involved in the field of "Creative Problem Solving" (or Applied Creativity) for an number of years chiefly though my association with Dr. Min Basadur and his "Basadur Simplex" process for problem solving. Quite a while ago I created a software instantiation of the process designed for education -- the software is still in use today.
I thought it would be useful to document a number of things I have learned from the years of involvement with Simplex, Dr. Basadur and Larry Crase-- my business partner and a facilitator extraordinaire.
Principles I have learned in solving problems:
- multiple people with differing opinions and backgrounds contributing to the problem solving process create better solutions than single individuals or homogeneous groups assuming the process is managed well
- time spent on reaching consensus on what problem you are trying to solve and explicitly wording the problem is critical
- three skills are needed at all stages in solving problems:
- being able to think divergently without judging the thoughts or ideas produced
- being able to converge on ideas to find the "best" ideas or thoughts
- being able to separate the diverging and converging functions so that they aren't executed at the same time
- it is not necessary that all parties have skills at both diverging and converging
- problem solving in groups often requires an "independent" facilitator to make sure that process is followed and time constraints are adhered to
- problem solving in groups requires discussion and consensus
- individuals with hangups about "ownership" of ideas do not generally make good problem solvers
- the best problem solvers are the people with the most stake in solving the problem
- having people "of power" involved in the process often intimidates other participants and results in solutions of lesser quality ( unless carefully managed by the facilitator)
- solutions to problems always require an action plan with simple straightforward, measurable steps
- many of these same principles can be applied to solve individual problems not involving a group
- solving problems always creates new problems so to be effective problem solving has to be a continuous process
- there are always many solutions to problems(unless they happen to be of a mathematical nature)
- solutions are different depending on ( perhaps subtle) restatement of the problem definition, the people involved in developing and implementing the solution and the point in time when the solution is developed
I wonder if Microsoft explicitly understands and uses these principles in solving problems? I know many people and companies implicitly understand and follow these principles -- Microsoft may be one of those.
|
|
© Copyright
2008
Brian Sullivan.
Last update:
22/06/2008; 12:24:44 PM. |
|
