42 Things I Learned from Working in IT
42 Things I Learned from Working in IT
Read this former QA engineer's technician's take on the lessons that he picked up after having been transitioned to IT.
Join the DZone community and get the full member experience.Join For Free
Discover how TDM Is Essential To Achieving Quality At Speed For Agile, DevOps, And Continuous Delivery. Brought to you in partnership with CA Technologies.
When I was hired on at Lucid, we had fewer than 100 employees. At that time, computer and hardware responsibilities were split between DevOps, security, and office management. If you had any issue with your computer or other hardware, your best bet was to figure it out yourself or just keep asking other people until someone could figure out how to solve your issue.
During my first year at Lucid, I was a QA specialist. I was then approached and asked if I wanted to do IT for the company. I accepted the offer and have been doing IT ever since. We have hired on additional employees to build up our IT team, and I have learned many things along the way. Here’s a look at things I learned from working in IT:
1. Work for a Company That Hires Great People and Finds the Best Fit for Each Employee
The first year I worked at Lucid, I really loved doing QA and was honestly quite surprised when I was approached to do IT. I expressed some reservations about this new position and wondered if I was qualified enough. I was assured that I was, and multiple examples were cited as to why specifically I was qualified for the position. Fast forward to the present—I love my position in IT and actually feel it is a much better fit for me than QA ever was.
What I find remarkable about this situation is that Lucid was able to see something in me that I did not see in myself. Company culture here at Lucid is very important, and “teamwork over ego” is one of our core values. While you may not be able to control your co-workers to make them as amazing as my co-workers, you certainly can have a positive effect by being a leader and an example.
2. The Stereotypes of IT Are True
We have all heard people joke that if something is wrong, you should simply turn it off and back on again. I have been amazed to see how often this actually does fix the problem. This has taught me a couple of valuable principles.
Never Disregard the Simplest Solution
It might be tempting to disregard a solution to a problem because you think that it has probably already been done or that it is so obvious that it won’t work. When we have this type of mindset, we often pass up on the least expensive and the easiest solutions. Don’t overcomplicate things.
Never Make Assumptions Based on past Experiences
I have seen this scenario a handful of times in IT: an employee contacts me for help with a certain problem. I show them how to solve the problem. A month or so passes, and the same employee contacts me with the same problem. When I go to help them this time, I go in with the assumption that they have already done the same troubleshooting that I showed them the previous time, resulting in a misdiagnosis on my part.
While this is not a common scenario, it does bring up a couple important points that are applicable to more than just IT:
- Just because you tell someone something once does not mean they will always remember. Keep in mind that everyone has different experiences, backgrounds, and strengths. It is much easier to remember information related to your strengths.
- Always communicate clearly with people before making assumptions.
3. Plan in Advance to Plan in Advance
For inventory to show up in time, you always have to plan in advance. However, I have often found that planning in advance is often not good enough due to unforeseeable circumstances. For example, if we have 10 new hires starting in two weeks, ordering 10 computers might seem sufficient, but what happens when two of the computers arrive broken, when an employee drops their computer and needs a replacement as soon as possible, or when one of the teams decides at the last minute that they want to hire three additional employees in the next couple of days?
Normally when we plan in advance, we plan on circumstances that we anticipate or expect. When things go unexpectedly, however, we no longer have a plan. I find it especially useful to plan at least two weeks before I would expect to plan.
It is always good to anticipate the unexpected and to plan as if the unexpected will happen.
4. Be Satisfied with Never Being Satisfied
I like checklists. I like checking things off checklists. I like seeing that my checklist is completely done. You will never see many unread emails in my mailbox because I can’t stand to see that something is not done.
Here’s the thing though—I am never completely done. I imagine most people feel the same. When I started in IT, I quickly realized that I would never be caught up with everything. The more employees we get, the more I am interrupted. There are many days where I am never even able to begin my sprint work because I am continuously interrupted with IT requests of one form or another.
I have learned to prioritize and be okay with not having everything completely finished. There will always be more work to do, and there will always be better ways to do things.
5. Don’t Allow Tasks (Or People) to Be Forgotten
Let me describe a typical day in IT.
I will come in a bit earlier than everyone else to pretend that I will have some time to get caught up on things. I will start going through emails from last night to figure out what new tasks I have, what existing tasks people are anxious to have completed, and what emails are spam or ignorable.
Around 9:00 a.m., a couple people will tell me that their password expired and needs to be reset (I literally had to stop writing this paragraph at 8:42 a.m. to reset someone’s password). Around 9:30 a.m., someone will usually message me to let me know they left their computer at home and want to know if there is a loaner computer that they can borrow.
As I am going to get their computer, someone will stop me to ask a random question. When I get to their desk, I will see something wrong in a neighboring conference room that needs to be fixed. On the way back to my desk, someone else will stop me to work on a request that needs to be done right away. When I get back to my desk, I will have a handful of new emails and Slack messages that require my attention.
My point is that there are a lot of people contacting me all the time, and tasks can easily be lost or forgotten.
I have implemented several systems to ensure that tasks will not be forgotten, such as email drafts, Slack snoozing, and a ticketing system.
Whatever it is you are doing, you need to make sure that every task you need to do is recorded somehow and that you frequently look at your list of tasks. When you are not able to work on something in the immediate future, it is important to inform those involved that you still intend on getting the task done even if it will not be completed immediately.
6 Through 42. Stand Out (Leave a Positive Impression)
Just like Douglas Adams has left an impression on me that somehow the number 42 is a special number, I find it important that with whatever work you do, you find a way to stand out and leave a lasting impression. In IT, people only notice when something isn’t working and don’t notice when everything is; however, I have found that I can leave a positive impression by being responsive to all requests for help and assisting with tasks that are not necessarily covered by IT.
Whatever role you have, you should look for a way to stand out and leave a positive impression. Anything you can do to make the workplace better ultimately makes you a better employee and makes work more enjoyable for you and everyone else.
Published at DZone with permission of McKay Christensen , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.