Rules To Problem Solving

Written by Richard Lowe

Continued from page 1

Rule #9: Don't assume you don't have a problem either. Again, don't make assumptions. Base your conclusions upon what exists, not what you assume to exist.

Rule #10: Don't assumerepparttar problem isrepparttar 131979 same as an earlier problem. I manage a number of computer systems. One ofrepparttar 131980 functions of these systems is to fax several thousand purchase orders to venders over night. One day someone reported that they could not see any failures, and it's unheard of for no faxes to fail. I assumed. mistakenly, that this was a failure inrepparttar 131981 report, which had happened before. Thus I putrepparttar 131982 incorrect priority onrepparttar 131983 issue and didn't look at it untilrepparttar 131984 afternoon. When I looked, I discovered to my horror that ALL faxes had failed (which causedrepparttar 131985 failure list to fail also, as it made an assumption that at least ONE fax would work). This caused incredible grief which could have been avoided had I actually looked instead of making an assumption.

Rule #11: Don't assume it's a computer error. Not all problems are caused by machines. You could spend countless hours trying to fix something that was actually a data entry error or had some other human cause.

Rule #12: Don't assume it's not a computer error. By now you should thoroughly understand this. Don't make assumptions. Look and form your conclusions based uponrepparttar 131986 evidence that exists.

Rule #13: Don't trustrepparttar 131987 documentation. Use technical documentation as a resource, but do not assume it is correct. Programmers are notorious for allowing their documentation to slip into uselessness. That's justrepparttar 131988 wayrepparttar 131989 world is, so don't beat your head over it. Read any documents you can get your hands on, but also look atrepparttar 131990 code and anything else pertinent.

Rule #14: Don't assume it ever worked. Many years ago, I hadrepparttar 131991 assignment to convert a plotting package from one computer system to another. It appeared to be a simple project (I violated Rule #15) so we just movedrepparttar 131992 code torepparttar 131993 new machine and tried to run it. Several errors occurred (squares not square and triangles not triangular), and these did not occur onrepparttar 131994 original machine. We spent months (literally!) trying to figure out what we did wrong. As it turned out, we violated rule #14. The code was inrepparttar 131995 middle of being modified, andrepparttar 131996 programmer who was doingrepparttar 131997 modifications quit and didn't tell anyone. Thus,repparttar 131998 code we were using never worked, and thus, well, we didn't do anything wrong. Once we hadrepparttar 131999 proper code (from an old backup) it really was very simple.

Rule #15: Don't assume it's simple or complex. Just remember it is what it is. Some problems are simple and some are complex. Don't assume either until you have done your analysis.

Rule #16: Don't assume maliciousness. If you find a human error, don't assume it was malicious. Generally, human errors arerepparttar 132000 result of incompetence -repparttar 132001 person did not understand what he or she was doing. Start with training to correct human errors - you can move to harsher methods later if training doesn't work.

I hope these rules are of value to you in your problem solving endeavors.

Richard Lowe Jr. is the webmaster of Internet Tips And Secrets at - Visit our website any time to read over 1,000 complete FREE articles about how to improve your internet profits, enjoyment and knowledge.

Awards Programs: Handling The Winners

Written by Richard Lowe

Continued from page 1

It's a good idea to attachrepparttar graphic directly to email message, as well as to include a link where it can be picked up if, for some reason,repparttar 131976 image is not received properly.

I've found an email similar to below hits upon all ofrepparttar 131977 necessary points.

Hi Sally,

Thanks for applying forrepparttar 131978 Excellent Site award. Your site has metrepparttar 131979 criteria forrepparttar 131980 award and has won! I found your site is indeed excellent and I thoroughly enjoyed my visit. I especially liked your page about Sammy (your dog) - it made me laugh. The photos of your children are a nice touch (cute kids) and your choice of background images is good.

Your award image is attached. Please link it back to - this is not a requirement but it would be appreciated.

Some URLs which you may find useful:

Description of our awards program in detail

Excellent site award home page.

The criteria common to all of our awards.

You may also pick uprepparttar 131981 award image here if you wish.

One thing that I do NOT recommend is to inform your winners about any negatives or give them ay criticism. I know from personal experience that these kinds of comments detract fromrepparttar 131982 thrill of winning an award. I prefer to just tell my winnersrepparttar 131983 good news and leave it at that.

Some sites use a scoring system to figure out who has wonrepparttar 131984 award. In those instance, I would also recommend that this score NOT be shared with anyone - again, no need to take anything away from your winners victory.

That, in a nutshell, is a method which is useful for handling your winners.

Richard Lowe Jr. is the webmaster of Internet Tips And Secrets. This website includes over 1,000 free articles to improve your internet profits, enjoyment and knowledge. Web Site Address: Weekly newsletter: Daily Tips:

    <Back to Page 1 © 2005
Terms of Use