Four Tips for “Beefing Up” Your Problem-Solving Tool Box – Part Four

Published May 4 2009 2:25 AM | Rich

This is part four of a four-part guest post contributed by Fred Nickols, Managing Partner of Distance Consulting LLC. All four parts focus on improving your problem solving efforts.

Tip #4: Draw pictures of the structure of the problem

A picture or model of the elements and relationships in a problem situation will help you to more quickly and more completely grasp the situation and figure out what to do about it.

Consider, for example, the diagram shown in Figure 4.  It depicts the structure of a general-purpose work sys­tem.  The elements of this system include inputs, a processor, outputs, a con­troller, and two control loops.  On the front end of this system is a task initia­tion loop and on the back end is an evaluation and termination loop (the dotted lines).  The relationships among these elements are such that inputs to the work system interact with the processor.  The interactions between inputs and proces­sor, which typically consist of prefigured routines, are referred to as “processes.”  These proc­esses produce the work system’s outputs.  All this occurs under the watchful eye of the controller.

If the outputs of the work system are faulty, several possibilities are suggested by the structure of the diagram in Figure 4.  The inputs might be faulty.  The processor or the controller might be malfunctioning.  Perhaps one or the other or both of the control loops is open and no information is getting through.  Whatever the contributing factors, the diagram provides guidance regarding places to look for what might be causing the problem and for what might have to be changed in order to solve it.

The use of diagrams or schematics as an aid to problem solving is not new.  Technicians have been using schematics as troubleshooting aids for years.  Computer programmers and systems analysts are familiar with, if not dependent on, flowcharts and data structure models.  Industrial engineers have relied on process flow diagrams ever since the days of Frederick Winslow Taylor.  Diagrams and schematics should be found in your problem solving toolbox too.

Most important, get in the habit of visualizing the problems you tackle.

More Information

This is an edited excerpt from a longer piece titled “Ten Tips for Beefing Up Your Problem Solving Tool Box” that appears on Fred Nickols’ articles web site (www.skullworks.com). Many other articles dealing with problem solving and additional workplace-related subjects can be found there as well. Fred can be contacted by e-mail at nickols@att.net.

Be sure to read the previous three parts of this article from Fred Nickols.




Comments

# Karen Umemoto said on May 12, 2009 11:51 AM:

These four articles are really right to the point and address problem solving in a very clear and insightful way.   Any person would benefit from the articles in any type of job.   Thank you.

# mark berg said on May 12, 2009 10:07 PM:

I am a certified quality improvement trainer and facilitator.  I use 7 step story boards from problem identification, through feasible countermeasures.  This article encapsulsates many of the problem solving components of a rigorous solution process.  It will become part of my toolkit for training and checking process steps for problem solving.  Thanks for the article.

# Alexander Grosskopf said on May 14, 2009 2:23 AM:

Your article series is awsome. Especially this one. Pictures are a common language that can build a bridge. However, you you drawing carefully, because the way you draw it determines the way people perceive and think about it (called cognitive fit).

As a software engineer, I use UML for structural models and data modeling and <A HREF="bpmn-book.com/">BPMN for procedure focused communication</A>.

Leave a Comment

Name:  
Website:

Powered by SmartDraw

Increase your productivity. Be a better manager.

Subscribe by Email

Click here to get the SmartDraw blog delivered by email.

Recent Posts

Categories