Work Orders/Tickets layout
I got my first job as an Automotive Technician back in 2012. Since then I have had to use ticketing systems to work on “work orders,” or “tickets.” I have grown accustomed to them and was always made aware that everything I do on the vehicle is to be documented for various reasons.
1) If something broke and it wasn’t me, I had documentation.
2) If I couldn’t not fix it because it was above my level of knowledge or scope then the next technician can see what I tried to do and what I may have forgotten.
3) If the problem is fixed, then there is documentation of how it was fixed.
4) If it is a reoccurring issue with the proper documentation to back that up, then maybe the issue is something else.
This mentality has carried over with me working on fire sprinklers as a service technician and now in IT.
Some new things that I consider now though are…
1) Management can run metrics on the tickets generated for the year and see issues with specific applications or computers. This is essential for a computer that is having more issues than others, an application with bugs that have to keep getting patched so an alternative solution may need to be found.
My first job in IT was for a local mom and pop show Managed Service Provider where I literally had to do everything from creating a new user to deleting them to installing applications, antivirus solutions, manage servers and more.
My second job in IT was for a Managed Service Provider as a level 1 service desk just resetting passwords or assisting with hardware troubleshooting.
My current job is much more technical in some aspects but still not as wide ranging as my first job. Everything is much more segmented in the company and everything has their own department. We are encouraged to learn yet it proves to be hard when the department that we work in is much more limited in permissions.
However, I still like to follow up on all the tickets that I make. I like to know if the issue is something I have not learned, or if the issue truly is something that I do not have the permissions for.
Like I said. I like to monitor my tickets and see if the issue is something I may have missed, something I need to learn, or something that I do not have permissions for.
I do find that if I reach out to some people and ask for help, some are more helpful than others. Some like to keep their secrets and others are more open with their methods.