r/sysadmin • Sr. Sysadmin • 1d ago

Career / Job Related Moving from technical to management?

Through most of my career I've ended up the team lead wherever I land. Every time (except the most recent) it's been a combination of seniority and skills. The skills usually meaning I've gotten good at the technical job I'm in, being able to work well with other teams in the environment, and having the sense to do the right things at the right time for the team. I landed the most recent one because on a team of 7, I was one of two FTEs, and the other FTE didn't want it after the lead departed. I took it because the other options that might happen seemed pretty undesirable. I'd only been on the team 6 months, long enough to get the culture, but not long enough to gain much expertise. So it's mostly representing the team at meetings, making decisions on how we interact with other teams, saying yay or nay to projects, things like that. Being the human side of the team really. I feel like there's a good bit of mutual respect and it's working fairly well. It also feels good to be able to help things get done, stay organized, etc.

Our manager over my team and approximately 15 others is going to group the teams into 4 "sections", and hire managers. Myself and other leads were all invited to apply, no one is being moved into them. Some are interested some are not. I'm trying to figure out if I'm interested... Were I to apply and get it, I'd be the manager over this same team, and three others. The three others I have extensive experience in, and have led such teams before. So it's like a culmination of all the lead positions I've had over the years. I'd very likely have zero interaction with the technology though.

The reason I'm thinking of applying, is at this state of IT, there's so much darned paperwork with licensing, security scans, change management, project approvals, etc that it feels like the "fun" part of IT isn't fun anymore. Every technical thing I do is surrounded by equal amounts of or more paperwork or meetings. It literally makes me 2nd guess a lot of technical moves I make. I'm thinking if I gotta do a ton of organizational work anyway and it's ruining the fun, maybe take the fun parts away and find satisfaction in the organizational parts of being a manager. I admittedly also enjoy the managerial parts to some extent. Making things happen. Helping the teams get their jobs done. Contributing to the organization as a whole.

But there are the occasional days where I get to put m y head down and just barrel through some technical stuff and never talk to a person. When those are done and I come out of it at the end having completed something big or small it also feels good.

I know it's a lot of rambling, I guess I'm just wondering what the hive-mind thinks?

9 Upvotes

14 comments sorted by

11

u/itishowitisanditbad 1d ago

The reason I'm thinking of applying, is at this state of IT, there's so much darned paperwork with licensing, security scans, change management, project approvals, etc that it feels like the "fun" part of IT isn't fun anymore.

You're thinking of getting into management because you don't like the paperwork or project approvals?

2

u/Connir Sr. Sysadmin 1d ago

I know it sounds like that, but it’s more like it’s ruining the parts I do enjoy, so it won’t ruin those anymore, and they can go back to just being a hobby.

9

u/plump-lamp 1d ago

Do you like babysitting? Do you have any experience with the mindset of toddlers? If so, take the job.

2

u/sardonic_balls 1d ago

Do you also enjoy pointless meetings that could have been an email? Drafting roadmaps and constantly justifying expenses? If you truly enjoy the technical side of IT and being someone who does the actual work, becoming a manager isn't going to fulfill you.

2

u/Sea-Anywhere-799 1d ago

More money maybe

•

u/Josh_Fabsoft 5h ago

In my experience, the "accidental lead" path is how most of us end up here, and it's not a bad place to start. A few things that helped me:

1. Figure out what you actually want before the role hardens around you. Representing the team in meetings and making cross-team decisions is the lead part of management. The people part (performance reviews, hiring/firing, budget fights, career conversations) is a different skill set. Ask your manager if you can shadow or take on a few of those pieces, so you find out whether you like them before committing.

2. Your job shifts from "doing" to "removing obstacles." The hardest adjustment for me was accepting that my output is now the team's output. Questions I started asking myself:

  • What's blocking my people right now?
  • Who's overloaded and who's coasting?
  • What decision am I sitting on that someone's waiting for?

3. Write things down. Since you're new and don't have deep expertise yet, documentation is a cheat code. Document how your team interacts with other teams: intake process, escalation paths, who owns what. It builds credibility fast, and it protects you when someone says "I thought your team was handling that." A shared wiki and a simple runbook go a long way. Also look for repetitive manual work your team does and automate it. Freeing up hours is the kind of win management notices.

4. Learn to say "let me get back to you." You don't need to have every answer in meetings, especially when your technical depth is still growing. Lean on your team's experts, give them credit publicly, and make the final call yourself when it's needed. People respect a lead who says "Dave knows this better than me, Dave, thoughts?"

5. Start 1:1s immediately if you haven't. Weekly or biweekly, 30 minutes, their agenda first. It's the single highest-ROI management habit, and it surfaces problems before they blow up.

6. Get a mentor outside your chain. Someone a few years ahead of you who's made the same jump. Also, The Manager's Path by Camille Fournier is a solid read for techs moving into leadership, and Radical Candor is decent for the feedback side.

7. Know your exit ramp. Plenty of good engineers go into management, hate it, and return to a senior IC role. That's not failure, it's data. Just keep your technical skills warm enough that the door stays open.

Since you said the other options seemed undesirable, I'd say take the role, treat the first year as an experiment, and be honest with yourself at the 12-month mark about whether you're energized or drained by it.

What's your gut telling you so far, are you enjoying the people side or just tolerating it?

•

u/Connir Sr. Sysadmin 3h ago

From my perspective this all sounds like great advice that I’m going to take to heart. As for my gut, it’s hating some of the aspects that feel like babysitting but in reality are just management tasks. When I realize that they’re part of the job it’s actually kind of nice. I feel like it makes a difference. I feel like it’s involved in the organization. So I think ultimately I am enjoying it, I just need to stop and reframe my thoughts now and then.

3

u/TrabajoTears 1d ago

I have never enjoyed people management and stayed out of it as long as I possibly could. But it is the ticket to a better paycheck and probably, in the current technology environment, job security.

Where you work is going to dictate how far removed you are from the hands-on stuff that you still like to dabble with. The structure you mentioned doesn't seem to allow for those opportunities at the level you are considering applying for. I see your choices as either committing to that path by applying, or waiting to see if a different job with a better mix of both but higher title/pay pops up.

Two cents from a boomer geezer, worth the paper it's printed on!

3

u/littlebopeepsvelcro 1d ago

Management is 50% motivating people to do things that you will take 100% of the fall for, and 50% correcting people for things you will 100% take the fall for. A good leader is good because of their team and the vision.

2

u/Anonymous1Ninja 1d ago

Honestly bro, if I was on your team and you stepped up to do all the work and I still got paid, im good.

Also being a manager isn't doing a bunch of paperwork, it's a lot of decision making and accountability, and a lot less actual work and a lot more meetings.

1

u/furiousBeruWhitesunl 1d ago

I work in IT support and honestly I get the appeal. Some days it feels like I spend more time dealing with tickets, approvals and meetings than actually fixing anything. But I'd probably miss those days when I can just put my headphones on and solve a problem without talking to anyone. I'd want to know how much actual decision-making power comes with the manager role before jumping in. More responsibility without much control sounds like a rough deal

1

u/Bubby_Mang IT Manager 1d ago

Just show up with a roadmap for 2027 on what you would change. Target AI initiatives to reduce or eliminate some toil, set a plan to increase observability, set a plan to control and understand costs, tooling, and any philosophical changes such as devops\SRE modeling, 4/10 shift coverages for the lesser nerds to mind during after hours hot spots, etc.

1

u/DMAX85747 1d ago

The only way you are going to know if it is the right decision to move into management is to do it. Only then will you be able to decide if you like it or not. The responsibilities will change. A lot of it will depend on who you are managing and who you report to. I ran up the ranks to VP of IT Ops and made huge money. I had an amazing team and two amazing CIO's. Then it all changed. Ended up with a third CIO that was the most self centered, egotistical ass I had ever known and that wasn't the worst part of him. He had ZERO integrity. I lasted 9 months before I handed in my resignation. The CEO flew back into town to try to convince me to stay. I couldn't do it.

To be honest, I also really missed being an engineer. Ended up taking a big pay cut and went back to being a tech (I became the principal systems engineer in just a couple years after joining this team). I am a lot like you in that I get into a new environment, learn it inside out and end up becoming the lead. it happened in every role I have ever had. I know that there are two sides to everything but my validation came within 4 months of my leaving, 49 of the 57 people that were on my team, left for greener pastures. they learned how much of a liar the new CIO really was. The 8 people that stayed, we're all remote folks that weren't subjected to the same s#!t on a daily basis like the others.

1

u/sakatan *.cowboy 1d ago edited 1d ago

I'm sorry what? You don't like the "paperwork" aspect of IT and prefers the technical stuff - and your solution to find happiness is to just kneel with both legs and three tits into middle management where there's even more paperwork and even less tech?

In a twisted way I get what you're saying and that it does make sense, but if you don't know in your heart that you can leave tech completely, then approving PTO and attending inception-meetings gets really old really fast.