[Logan Krape]

The value of troubleshooting lies in solving a problem to allow a system to be able to function at its full capability. Being able to troubleshoot allows you to not only make a systematic fix, but also use your knowledge and problem-solving skills to help you make this fix. By using the troubleshooting theory, you give yourself a process to follow to help you stay organized and find a solution to the problem. Step one of identifying the problem allows you to use what you know and identify what could be causing the issue. What then follows is being able to recognize a probable cause and then discovering ways to fix the problem within the system. Now you can test your theory to determine if you were correct about the problem at hand or if you need to keep researching and establish a new probable cause. Once you determine the cause, you can begin the plan of action phase. The plan of action phase allows you to go in and take your research and then put together steps to solve the problem within the software. After you have completed that and checked for full functionality within the system, you have completed the troubleshooting process. All you have left to do is document your actions and steps taken throughout the troubleshooting process. This process is not difficult or time-consuming. I think being able to troubleshoot is becoming more and more important with how much technology is being used throughout all parts of our lives. Being able to take these steps and problem solve and make the fix on your own saves a lot of time and money.