IT Technician to IT Director: Advice From Someone Who Did It
Moving from IT technician to IT Director means trading ticket fixing for district-wide decisions, leadership meetings, and a lot more communication. In this episode of The IT Director’s Podcast, hosts Jay and Michael sit down in studio with Ric Moseley, IT Director at Guntersville City Schools and a Clear Winds customer and partner, to talk about his unconventional path from graphic design to technician to IT Director. Ric shares what surprised him most about the role, how he learned to delegate and let his team own tickets and projects, and how he earned a superintendent’s approval for new email protection by explaining it in simple terms. Whether you’re an IT Director in K-12, a technician aiming for leadership, or an IT leader curious about how education differs from the private sector, this conversation covers delegation, communication, and the steps Ric recommends for growing into the role.
IT Technician to IT Director with Ric, Michael and Jay
Jay: What is going on? This is Jay and Michael here on The IT Director’s Podcast. Michael, how are you doing today?
Michael: I am doing awesome. I have had two cups of coffee now, and will probably do three before the day is over, so I am amped and ready to go.
Jay: You’re ready to go. Look, we have a special guest in studio today, our great friend, one of our customers, our partners, Ric Moseley, the IT Director at Guntersville City Schools. Ric, how are you doing?
Ric: I’m doing well. Thanks for having me here today. Yes, sir.
Jay: Ric, thanks for making the drive in to our studio and joining us in person. Ric is a very awesome guy, for our listeners and viewers, a very unique person. He has a lot of talents, even more so than an IT director. You guys are going to learn about him today. So we’re excited to have Ric on today.
Michael: Yeah, no, I’ve enjoyed even getting to hang out with you a little bit at ALET. There’s a couple of little shots of us on the podcast earlier. But I want to ask some questions so people can hear a little bit about yourself. So tell us a little bit about yourself so our people listening know who they’re getting to hear from today.
Ric: Like he said, I’m IT director at Guntersville, but my path to becoming the tech director is actually very unconventional. My career actually started out in graphic design, which is nothing to do with technology. I was living in Atlanta at the time, and then the recession of ’08 hit, so I moved back home to my hometown of Guntersville because I grew up there.
The tech director at the time cold called me and said, “Hey, I know you’re in graphic design. You work with Apple computers a lot. We’re starting to transition to Apple computers. Would you be interested in coming to Guntersville and doing some IT work for us?” I said, “I’ve never done IT work. I don’t even know what that looks like.” But I took the leap because I didn’t have a job at the time, and jumped in and started in ’09. I worked there, and I did have a small break in the middle of that timeframe.
Last year I got hired as the tech director, which was kind of an interesting transition as well. My former boss was the tech director for 24 years, and he retired last spring. We had some trouble figuring out who was going to be the new tech director. They interviewed a lot of good candidates, but all those good candidates, their organization said, “We don’t want you to leave, so we’re giving you a raise, so please don’t leave.” So we went through six different candidates, and none of them took the job.
I had no desire to be the tech director at the time. It was not an interest of mine. I didn’t think I was qualified necessarily. They ended up hiring a gentleman from not the education background, and he did not work out. It was not the right fit for him, not the right fit for us. Coworkers of mine reached out to me and said, “Ric, I think you need to apply. I think you need to be the tech director.” So I did it, met with the superintendent, and they hired me.
Michael: That’s awesome.
Jay: That is so unique. That’s a journey. Let’s back up. Graphic arts to being an IT technician, to being the IT director, and then really not even being in your wheelhouse of, “Hey, this is something I want to do.”
Ric brought up a great point, Michael, and I want to talk about this, Ric, for a second, because I think this will resonate with all of our listeners and viewers, especially in the K-12 space. Education is unique. I was somewhere for 25 years, and leadership always likes to bring in people from the outside. It’s always this misnomer that people from industry or the private sector are just way more intelligent than people in K-12. Would you agree with that?
Ric: I would definitely agree with that.
Jay: Michael, that’s kind of a thing in K-12. It’s pretty interesting. But every time I saw someone come in from the outside, they lasted maybe a month, two months, three months, and then they were not here. It takes a unique person to understand K-12 and the education environment and just how it moves and works and flows. So you said something right there that I think is a good perspective: not everyone can be an IT director in education. It’s totally different than running IT for Dell or Cisco.
Ric: Right. Or just some private company. One thing I think a lot of people just don’t realize is all the avenues of a tech director and what that looks like in education, because it’s not just managing the IT department. It’s making a lot of decisions. It’s being on leadership teams. There’s a lot going on, and coming in from the non-education world is kind of a culture shock for people that have never been in it.
Jay: Ric, what is a task that you assumed would take maybe 5 to 10% of your time, but as an IT director takes a whole lot more of your time right now?
Ric: Wow. I would say communication and emails. As a technician before becoming the tech director, my role was, there’s a ticket in, go fix the ticket. Go fix the issue. Go work with the teachers or the principals or the admin and figure out whatever the problem is and fix it, and then move on. Those emails were quick and simple, and then go fix the problem.
I was not prepared for how many emails I get on a regular basis. I average 200 to 250 emails a day right now. And that’s not spam, that’s actual emails I have to answer.
Michael: Those are legitimate emails. How do you prioritize that?
Ric: I’ve been in this role for a year and a few months, so this is one of the challenges of still figuring it out.
Michael: Which I think is an awesome perspective to have, because a lot of our listeners ask us questions frequently about, how do I learn to think differently? How do I learn to move from a contributor on a team and being task-focused to seeing the big picture? You’re in the middle of that. Hey, you’re there. So give us your perspective on that.
Ric: My perspective is learning to delegate well with your team and trusting your team to handle the things that are important, but not important for my role. So understanding, yes, this is something that I can easily do in five minutes because I’ve been doing it since 2009, and it only takes me a few minutes. Well, one of the other people under me, a technician or a network admin, it may take them 30 minutes. But they need to own it, because my priorities are now district-wide, and I’m trying to prioritize the bigger picture items and make sure our department is going in the right direction for our district and our district has what they need to operate.
So even though this issue may be something I can do quickly, if I keep doing those things, then I’m a technician and a tech director, and I can’t be good at both.
Michael: Yeah, no, that’s good. That’s very good. Have you ever used that method where you’ve got the four quadrants: what’s important and urgent, what’s important but not urgent, and so on? Have you seen that one?
Ric: I have not.
Michael: It’s important and urgent, important but not urgent, not important but urgent, and not important and not urgent. Then you can take all the tasks and fill it out and use that as a workflow.
Jay: Yeah, which is tough in K-12, because everybody that emails Ric, it’s all urgent in their minds, right?
Ric: Right. And I think the biggest challenge for me, and this is kind of an unspoken thing with the tech department in any organization, is that tech people usually get the bad rap of not being very personable, and of being the department of no.
Jay: We’ve talked about that before.
Michael: Yeah, we’ve done a whole session on that.
Ric: For me, coming in from a marketing and graphic design background into education, I’m very personable. The staff that has known me since ’09 reach out to me because I’m not a typical tech guy, and so I’m more personable. So everybody’s got my phone number. Now, transitioning into the IT director position, people still reach out to me that way, and it’s very challenging sometimes to say, “I can’t help you. Please put in a ticket. My guys will get to you. My team will help you out.”
And I need to be able to do that in a diplomatic way, to not hurt feelings, because one thing in education, and you know this, is that emotions can get high quickly when things are not going the way they’re supposed to go.
Jay: Yeah, and people have what I like to call, Michael, selective amnesia. They forget everything you’ve done great for them, and then they remember that one time where you couldn’t help them. Ric brought up a great point: you have to prioritize, and you have to be diplomatic, but you have to help. If you have these SOPs and standardizations, it helps flow. It really helps flow.
And Michael, what about the next question that we came up with from our marketing team? Ric talked about this.
Michael: So how do you stop being the person who fixes everything when you are still the best person to fix it?
Jay: That’s great. That’s great, Ric.
Ric: I would say it’s about delegation and trusting your team to own the ticket system and own the problems. The guy that I hired to replace me as the technician actually does not have an education background. He’s never worked in education, so I’m teaching him what I learned over the course of many years: okay, this is different than where you came from. You have to handle this differently. He’s not familiar with a lot of the tech that we use in education, and he used different tech in the corporate world.
It’s hard sometimes, because I know how our system works, and I know how to fix the problems quickly. But I have to let him own those problems and fix those problems, and be okay with them not getting done at the speed that I would do them or my network admin would do them. He’s going to own those projects, and that helps build our team as a technology department.
In the tech world, for me, we’re always problem-solving. The age-old thing is, someone can show you how to do it easily, or you can learn the hard way, and you’ll remember it a lot longer when you do it the hard way. For my new guy, I really like the fact that I’m letting him own it. Therefore, it’s not falling on my shoulders, because I’m working on everything that’s on my plate, and I’m delegating and trusting him to own the problems and the projects.
Michael: And in the process, you’re helping grow and develop a team member who’s going to ultimately be more effective, the more they’re able to function like that. So you delegate it. You let them sometimes struggle with it, but you’re building their resiliency, you’re building their expertise, their skill set, their knowledge, and they become an even higher performer, a higher contributor, and it helps the whole process overall.
Jay: Well, you’re building up better teammates, right? And Ric, as an IT director and leader, you’re only as good as your staff. Take any sports team. A coach is only as good as his players and his staff. It doesn’t matter how great the coach is. Same thing in leadership in IT. Ric can be a phenomenal leader, but if his team is not built up and empowered to do those things, then it still relies on you, and you’re still that person, right? You can only do so much as one individual.
Ric: I’m one person. I can’t do it on my own. I can’t be a one-stop shop. There’s only so many hours in the day, and the tickets keep coming.
Jay: That’s something, Michael, that we don’t really talk about a lot, because we have the SMB space. We have vendors on our show. We cover a lot of topics on The IT Director’s Podcast. But in K-12, the tickets never quit coming. I just had a conversation with my old predecessor, a young man that took over my old role, and he said, “Jay, I just did not know that it would never stop.” It stopped for them because I would shield them at times, and I would filter stuff and do things. He said, “It just really never stops.” I said, “No, man, it really doesn’t.” Those problems are there all the time, and it is how you handle that, right?
Michael: I think that’s good. One of the things that we talk about some is our users. We’re here to serve them and support them. What I hear you talking about is also your team and your SOPs. A lot of times I hear the tension between IT telling them, “Submit a ticket. I need you to submit a ticket.” They don’t always understand the process, and sometimes it’s viewed as IT being a barrier to doing my job. Like, I just need them to step in. How do you bridge that gap to show your users, hey, we’re not a barrier? We’re here to help and support, but there is a process that lets us do it efficiently. How do you help do that?
Ric: I implemented something new this year, because I think the biggest key to the technology department in K-12 is communication to your staff, to your teachers, to your administrators. I want them to know that we’re here to help them.
One of the things I implemented is an email that goes out every Tuesday. It’s just called Tech Tuesdays, and it’s one tip of the week. It’s nothing big. It’s nothing groundbreaking. It’s just a reminder that we’re here to help you with the tools that you already have in your classroom.
When I first started it, part of that was letting them know, hey, these tips are coming out every Tuesday. If you ever want to go back, create a label that says Tech Tuesday and check out that label in your Gmail account. At the bottom of every email, though: if you have IT issues or problems, submit a ticket, and I have a built-in button that takes them directly to our ticketing system.
Michael: That’s awesome, because you’re also helping the users that you support. You’re building that community. You’re opening that engagement. They can feel more comfortable about working with you, and they know who you are. You’re not the enemy. You’re working together to support them, so that’s awesome.
Jay: And communication is key, Ric. In leadership at any level, but in particular in K-12, because people like to know what’s going on. They like to know why they can access certain things, why they can’t get on Netflix, why they can get on YouTube but can’t get on this. When you communicate, Ric, it really helps you out better, and your team, because you’re not saying no, you’re not putting limitations, but you’re putting guardrails and saying, “Hey, this is why we do these things.” So that’s awesome.
How do you get the cabinet-level board members and the superintendents to fund something, maybe a project or initiative or a great new solution that you know about, that they really don’t understand technically? You don’t want to drown them in all the IT weeds of different things.
Ric: Because they have a different role, they’re not technical people. You don’t need to get into the weeds of explaining all the specs and the details and the technology terms. They’re not going to understand it.
This past year, I can actually use an example. One thing that we didn’t really have in our district was any kind of email protection. We’re a Google Workspace school system, and we use the built-in Google spam and protection, but it’s not great. A lot of the cybersecurity is people implementing through phishing attempts, malware, and trying to get you to click on things. So I wanted some software, another level of protection for my staff, in case they did accidentally click on something, or someone is trying to impersonate maybe one of our admins.
So I went to my superintendent and I said, “Here’s my concern. Here’s the numbers showing that people are more and more getting into systems by phishing attempts. And I would like to add a level of protection for that.” I showed him some software options and I said, “These are the two I’ve come down to. Here’s the pros and cons of this one. Here’s the pros and cons of this one. They cost about the same. Would you approve this for the protection of our district? Because this would give us that level of protection that we currently do not have.” Explaining it that way, in simple terms, my superintendent didn’t hesitate.
Jay: Well, that’s great, because you tied it down to teaching and learning, the direct impact on instruction, because if you have a phishing attack, you have all these different things, and that can do that. So you were able to tie it down and then explain it.
Michael: Yeah. So, back to that same idea, for those who are in a position looking to grow in their field, similar to your own journey, those who might be just a technician at this point and want to move to being the director, what would you tell them? What would be your advice? How would you help them think differently? What steps can they take?
Ric: Pretty simple. Start owning projects that might not necessarily be part of your role. Work on your communication skills. Work on trying to get into the conversation of district-level decision-making. Try to have a voice in those meetings. But I think the biggest thing is taking the initiative to try to own bigger projects that may not actually be your job.
Michael: That’s good. When we ask that question, a lot of times we talk about the hard skills, about the technical side of things, but not necessarily the soft skills, like your communication.
Jay: That’s key.
Michael: That’s awesome. I think that’s all of it.
Jay: Yeah. I agree. I tell people all the time, you can’t be in leadership, you can’t be influencing if you’re not at the table when those decisions are being made. So how do you get at the table? Or how do you get in those conversations? It’s by taking ownership, it’s by doing these things. That’s great. That’s really great.
Michael: Even what you communicate when you say, “Hey, I’m willing to take on something else. I’m willing to learn something else.” Because a lot of times if you’re in those roles, your job is a task-oriented thing, and you’re doing one thing after the other, and you might not feel you’ve got margin to see the big picture, or you’re just trying to do what’s in front of you. If you’re not open to seeing outside of that, you’re closing a door without realizing it. But you signal, “Hey, I am open for more. I am interested in learning. I do want to grow. How can I help with this?” I think that’s an awesome mindset and disposition toward that too.
Jay: It goes to being a servant, right? Serving your staff, serving your students, and serving your district. And that’s why Ric is so great, guys.
This has been great. I’m so glad to have Ric on the show with us, with Michael and I, on The IT Director’s Podcast. We partner with Ric, we help you, but we’re just here to serve you, and it’s exciting to see you serve the students and the population at Guntersville.
Ric: Well, thank you.
Jay: Yeah, and you do a fantastic job. But look, before we close, go check out this guy’s music. He’s on Spotify, Apple Music. Tell us what the name of it is, Ric.
Ric: I have an AI band named Pilgrim Road, and it’s a rewriting of the Psalms of the Bible. It’s pretty awesome.
Jay: That’s cool. You never know what you’ll learn on The IT Director’s Podcast. So, hey, these guys are not just IT leaders. They’re humans, they’re husbands, they’re leaders, and Ric creates music. I like it. I listen to it a lot when I travel. It’s good stuff.
So, hey, look, thank you for joining us on The IT Director’s Podcast. This is Jay and Michael, and we are out.
IT Technician to IT Director Outro
As Ric’s story shows, succeeding as an IT Director depends as much on communication, delegation, and trust as it does on technical knowledge. From letting his team own tickets and projects to sending a weekly Tech Tuesdays email that reminds staff IT is there to help, Ric’s approach shows how an IT Director can support teachers and administrators while keeping a process that works. If you’re an IT Director, or a technician who wants to become one, consider where you can delegate more, communicate more clearly, and take ownership of bigger projects. For more conversations like this, follow The IT Director’s Podcast across all major platforms, and reach out to the Clear Winds team or visit our website to learn more.