BoMax76

Document what you find and show it to management. Then layout a plan on how you would fix it. You can get both tech and management experience out of this.

Depends on the company and line of business you are in. I am surprised you have a dedicated security guy at that level, but good for you.

I love when he adds the boss's mailbox so he can delete the message from Sent Items. Classic use of Domain Admin power.

I keep giving it a try but ultimately switch back a day later. I find it difficult to work with calendars and over all just feel slow in it.

We have done lunch and learn style events to get people through these. Order a few pizzas and play the video for everyone in conference room.

Our PO process handles approvals and charge back for equipment. Anyone can request hardware, but both IT and their manager would need to approve the PO as it hits their budget. We don't have any type of charge back on support which I think we need in some capacity. It gets too easy for teams to throw the issue over the wall to IT and never have to take accountability to become more self sufficient.

I sometimes need to just remind myself after-hours that what I do and the company I work for isn’t dealing with life and death situations that need the priority/focus/sacrifice that I tend to make in order to keep things running and users supported. The rest of the company doesn’t operate that way and there is no reason to hold myself to that standard.

If you are in a smaller environment, I would suggest trying to create an ERP team with a handful of key stakeholders. Ask everyone to submit their ERP related questions/requests/issues to some type of ticketing system then have the ERP team prioritize, assign and take action. IT can address the technical issues, but system/business function will need other groups to get involved. This starts to give you a measure of how large the problem is and what resources would be needed to address it.

Worklife balance for me. I have so many things I need to do outside of work with family and helping aging parents that it is almost a job itself.

Me too

I can’t get my company on board with it. If the change is primarily technical in nature it is assumed to be an IT task even if it could impact the business. Can’t get business stakeholders to assume responsibility for their areas and develop the depth of understanding in their tools to even have anything meaningful to say at a CAB.

Larger CPA firm One of my favorite roles was in a larger CPA firm. There were a lot or Partners in the business which occasionally was an issue but largely it was an 8 to 5 job. The firm is closed after 5pm and on the weekends. It was busiest from January to April (Tax filing season) then pretty quiet/calm. On-Call for actual outages vs. user issues/support.

I think it come down to how you feel about your current position and why you choose to look at a new opportunity. If there are underlying issues making you want to leave, they aren’t likely going to go away with a pay raise if you stay. If it is just about money, discussing a counter might make sense. Employers know the job market is strong and salaries are rising sharply.