3.5 Basic Troubleshooting
Candidates troubleshoot basic software and hardware problems common in digital learning environments. (PSC 3.5/ISTE 3e)
Artifact: VoiceThread
Reflection
When it comes to working with technology, you learn that you have to learn how to quickly assess and troubleshoot basic software and hardware problems. A lot of that comes from after you have created a great lesson and you integrate your technology and it comes down to presenting it and having the students work in it and then all of the sudden there is a problem. You have to be prepared to quickly troubleshoot the software and hardware problems that are common in digital learning environments. This is where if you have worked with a lot of teachers who are reluctant to use technology get their frustration from. They have learned how to do the basics and when they encounter a problem, they want to give up on the whole system. As a coach, you learn through some of the same troubleshooting how to help people you coach.
In this artifact, I was working with students with VoiceThread to present multiplication strategies as a way of providing some blending learning opportunities for students near the end of the school year. I ran into some basic problems with working with the audio and uploading the video to the voicethread. The students were eager and impatient and here I was with trying to troubleshoot the basic software problem in the middle of students attempting to solve the problem. It was a basic problem that I needed to update on a certain computer that required me to use another computer where it ended up being successful. The students were able to complete their assignments before the end of the day. When it comes to troubleshooting, I am not sure what could have been done differently. It was an easy fix so when it comes to those types of troubleshooting, doing it quicker could be a change, but I do not think it could have been fixed any quicker than the 20 minutes it took to assess the problem and solve it.
This issue helped me learn how I have to think on my feet and teach my faculty how to troubleshoot. It gave me insight on when I am showing hardware or software that I need to include how to troubleshoot basic problems. Since I know a lot of people can easily get frustrated, it would be a good suggestion to show how to assess and troubleshoot the software and hardware problems. I think it will help ease faculty members to know that if something happens, it can probably be solved right away. I think it is important that all coaches take time to assess the faculty regarding basic problems that they come into. Assessing the faculty on common problems can help the coach learn about what may need to be discussed whole staff regarding common issues that teachers are running into. This will help to guide me as a coach to check into what troubleshooting needs to be looked at and resolved.
When it comes to working with technology, you learn that you have to learn how to quickly assess and troubleshoot basic software and hardware problems. A lot of that comes from after you have created a great lesson and you integrate your technology and it comes down to presenting it and having the students work in it and then all of the sudden there is a problem. You have to be prepared to quickly troubleshoot the software and hardware problems that are common in digital learning environments. This is where if you have worked with a lot of teachers who are reluctant to use technology get their frustration from. They have learned how to do the basics and when they encounter a problem, they want to give up on the whole system. As a coach, you learn through some of the same troubleshooting how to help people you coach.
In this artifact, I was working with students with VoiceThread to present multiplication strategies as a way of providing some blending learning opportunities for students near the end of the school year. I ran into some basic problems with working with the audio and uploading the video to the voicethread. The students were eager and impatient and here I was with trying to troubleshoot the basic software problem in the middle of students attempting to solve the problem. It was a basic problem that I needed to update on a certain computer that required me to use another computer where it ended up being successful. The students were able to complete their assignments before the end of the day. When it comes to troubleshooting, I am not sure what could have been done differently. It was an easy fix so when it comes to those types of troubleshooting, doing it quicker could be a change, but I do not think it could have been fixed any quicker than the 20 minutes it took to assess the problem and solve it.
This issue helped me learn how I have to think on my feet and teach my faculty how to troubleshoot. It gave me insight on when I am showing hardware or software that I need to include how to troubleshoot basic problems. Since I know a lot of people can easily get frustrated, it would be a good suggestion to show how to assess and troubleshoot the software and hardware problems. I think it will help ease faculty members to know that if something happens, it can probably be solved right away. I think it is important that all coaches take time to assess the faculty regarding basic problems that they come into. Assessing the faculty on common problems can help the coach learn about what may need to be discussed whole staff regarding common issues that teachers are running into. This will help to guide me as a coach to check into what troubleshooting needs to be looked at and resolved.