Post by jonrojas on Jul 21, 2021 13:45:15 GMT
What are two thoughts that stood out for you in each of the readings?
A: Using Data - What stood to me in this reading was the idea that success and failure needs to be defined before data can be properly gathered. It's important for a team or a company to define their scope and knowing what the goal is is very important. This helps to define what a success looks like in the scenario and this can help to drive a team/company to a successful outcome. This ties into the idea of the important behind analyzing the data that collect. Data collection is very important to my day-to-day work and we speak often in team meetings about analyzing the data that we collect to make informed decisions.
Analytics 3.0 - Everything about this article stood out for me as I have had a personal interest in the history of data collection. I really enjoyed the enthusiasm the writer showed in the article and how well the history of data collection was laid out. Data collection and social engineering go hand in hand and it is very important to understand both when dealing with cyber security. I enjoy that the article ended with creating value in the data you collecting because gathering data without a purpose is pointless. The importance of data has grown so much over the last couple of decades and has become a booming industry in today's technological world.
How might you apply these learnings to your everyday work? Please give a specific example.
A: The ideas behind both of these writings are already applied in my everyday work life as it is crucial for us to operate smoothly. Metrics are very important to us here at the help desk because it helps us to understand the type of issues we are having and how we respond to these issues as well. We go through our metrics weekly as a team and discuss any new or reoccurring issues that we may be facing. We track everything from the amount of tickets, how many open and closed per week, how long the tickets have been open (specially any tickets older than 20 business days which get discussed as a group), how fast we respond to tickets as well as how fast we resolve them, and many other factors that get measured on a week to week basis. It is important for us as a team to understand what exactly we are dealing with and solutions that may help resolve these issues. This requires us to not only collect the data but analyze it so we can get objective understanding from the data that we collected.
When have metrics mattered in your professional experience?
A: Metrics matter for the IT Team everyday. We use it to monitor the health of our network, the performance of the team, understanding the types of issues our user base faces, and also helps to identify any training that may need to be delivered. We also use metrics to show the results of our work to others in the company outside of IT. They are important for our day-to-day internally and externally.
How do you use data in your current role—would you describe your team as data driven?
A: I personally use data to understand the work flow of my team and how they are handling the work including myself. Paying attention to the types of tickets, the volume of tickets, and how long it takes for them to be dealt with helps me to understand my team better and the type of support they need. The data also helps to hold all of us accountable and helps to move improvements as move forward. I couldn't imagine doing this job without utilizing data collection and analytics to get it done.
A: Using Data - What stood to me in this reading was the idea that success and failure needs to be defined before data can be properly gathered. It's important for a team or a company to define their scope and knowing what the goal is is very important. This helps to define what a success looks like in the scenario and this can help to drive a team/company to a successful outcome. This ties into the idea of the important behind analyzing the data that collect. Data collection is very important to my day-to-day work and we speak often in team meetings about analyzing the data that we collect to make informed decisions.
Analytics 3.0 - Everything about this article stood out for me as I have had a personal interest in the history of data collection. I really enjoyed the enthusiasm the writer showed in the article and how well the history of data collection was laid out. Data collection and social engineering go hand in hand and it is very important to understand both when dealing with cyber security. I enjoy that the article ended with creating value in the data you collecting because gathering data without a purpose is pointless. The importance of data has grown so much over the last couple of decades and has become a booming industry in today's technological world.
How might you apply these learnings to your everyday work? Please give a specific example.
A: The ideas behind both of these writings are already applied in my everyday work life as it is crucial for us to operate smoothly. Metrics are very important to us here at the help desk because it helps us to understand the type of issues we are having and how we respond to these issues as well. We go through our metrics weekly as a team and discuss any new or reoccurring issues that we may be facing. We track everything from the amount of tickets, how many open and closed per week, how long the tickets have been open (specially any tickets older than 20 business days which get discussed as a group), how fast we respond to tickets as well as how fast we resolve them, and many other factors that get measured on a week to week basis. It is important for us as a team to understand what exactly we are dealing with and solutions that may help resolve these issues. This requires us to not only collect the data but analyze it so we can get objective understanding from the data that we collected.
When have metrics mattered in your professional experience?
A: Metrics matter for the IT Team everyday. We use it to monitor the health of our network, the performance of the team, understanding the types of issues our user base faces, and also helps to identify any training that may need to be delivered. We also use metrics to show the results of our work to others in the company outside of IT. They are important for our day-to-day internally and externally.
How do you use data in your current role—would you describe your team as data driven?
A: I personally use data to understand the work flow of my team and how they are handling the work including myself. Paying attention to the types of tickets, the volume of tickets, and how long it takes for them to be dealt with helps me to understand my team better and the type of support they need. The data also helps to hold all of us accountable and helps to move improvements as move forward. I couldn't imagine doing this job without utilizing data collection and analytics to get it done.