Hey everyone! I'm two months into my first role as a service desk manager and I'm feeling a bit overwhelmed. In my previous experience, I've primarily worked in customer support, and now I'm diving into a solo function using Jira Service Management. In this niche environment, I coordinate ticket management, but the actual troubleshooting is handled by my colleagues from other teams. My responsibilities include overseeing processes for users of a digital platform, focusing on issues like software access, user onboarding, and data requests. Since my role is relatively new, there's a lot that needs to be defined. I've done some process building, but I often feel like I'm just following instructions rather than proactively shaping the role. I'm considering starting ITIL 4 Foundation, but I'd love advice from anyone who's managed a small service desk in unique settings. What should I prioritize to get off on the right foot?
5 Answers
Don’t get too absorbed in ITIL just yet. You’ll need support from your wider team for that. Instead, start categorizing existing tickets and documenting resolutions. Look for ways to automate repetitive tasks to free up your time. Regular reporting will also help you identify hurdles.
To kick things off, focus on organizing your request categories meaningfully. Establish a clear handoff path for each category and monitor your backlog weekly to identify trends. Until you nail down the basics, a lot of what you're doing may seem pointless. ITIL can wait until you have a grasp on the flow.
Streamlining your incoming support channels can help you spot trends faster. Clarity in data capture is essential—make sure all relevant ticket info is recorded to prevent back-and-forths. The clearer your data, the more useful your reports will be!
Tracking ticket resolution times over time can offer valuable insights. Proactively monitor which tickets get stuck and advocate for their needs like a customer rep. This helps you propose changes based on real data that can enhance the service.
It’s tough relying on people in other departments for fixes. I’d recommend building a team and starting a knowledge base to document who knows what and how they resolve issues. Since there's no formal procedure, it’s crucial to create your own framework as you navigate through.
You might want to consider making a list of the common issues and sort them based on frequency. That could guide your efforts early.
Thanks for that suggestion! Given the platform's complexity, it really is about collaborating with the right people. I’m already creating the knowledge base as I learn, but were there specific strategies you used to set priorities early on?