Member-only story
Troubleshooting is a vital part of both developing and implementing our plans. We want to be sure our efforts will be as successful as possible and we want to try and foresee or anticipate as many of the potential obstacles as we can. We have all known, however, those individuals who not only seem to see nothing but obstacles they also view the existence of any obstacles as proof the plan cannot possibly work and is doomed to fail. That isn’t troubleshooting, that is excuse making.
Analyzing and resolving problems within situations, systems, methods, and processes has been around throughout history but was only given the term troubleshooting in the early 1900’s. It began in 1898 when people hired to inspect, examine, and repair telegraph and telephone wires in the field were dubbed ‘trouble-shooters’. The term then evolved to troubleshooting and grew to encompassed any effort to ferret out and resolve problems within any technical system.
Eventually the term and concept expanded even further to include any attempt to diagnose and resolves problems of any kind, either in reaction to some form of failure or proactively in attempt to foresee an prevent potential problems from occurring. We run troubleshooting programs on our computers…