A month after arriving at college, I was writing my first ten-page paper on my brand new Dell desktop. Suddenly, and without warning, my paper was gone! And I hadn’t saved in almost an hour! What’s a college freshman to do?
In a panicked state, I frantically called the dorm IT “specialist.” Within minutes, my paper was back, although without the unsaved last hour of work (lesson number one learned). I asked, “What happened?? What did I do wrong??” He replied, “Nothing. Computers are just temperamental.”
Lesson number two learned was that computers are apparently not the simple machines I had at first suspected. They have a “temperament” and sometimes they break without reason. The same is true for all technologies, including your website. So when dealing with your website, what do you do when something breaks??
Reporting errors is a very important skill to learn when you’re working with a website, application or management system. When reporting errors, it’s a good idea to include and test out as much of the following as possible when sending a request for fixes to your web team:
- What browser am I using? Is the error the same in another browser? What version of the browser do I have?
- Can I replicate the issue? If so, what were the exact steps I took to create the issue?
Is my internet connection ok?
- Am I using a MAC or a PC?
- Did I include a link to the page the error is on? Can I take a screenshot to show exactly what’s happening?
Answer as many questions as possible to give your web team a good idea of what’s going on. The more information your web team has, the faster it can be fixed!