In my case, I work for a municipality and I legitimately do need to be in the office to meet with citizens, attend public hearings, etc. abut I think they could come up with a schedule where I work remote on Mondays and Fridays or something. It would also make those days “no meeting days” so I could catch up on my actual job.
We get raked over the coals for how long development review takes, but then every developer wants to meet with us for an hour every week, so instead of reviewing plans we’re attending meetings 25 hours a week where they’re bitching at us for how long it takes us to review their plans.
Okay, here’s some unsolicited advice from an IT manager. Please take with a heap of salt.
25 hours is too many for 1:1 weekly meetings unless that’s your whole job description. That leaves 15 hours for overhead, project management, team meetings, leadership meetings, scrum-of-scrums, town halls, mentorship, breaking ties on MRs, etc. At that scale, and assuming you have other responsibilities, 1:1’s really should be monthly, optional 3/4 of the time, or cut back to 15 minutes unless there’s an ask for more time. Also: ya gotta delegate those plan reviews if you can. With a labor pool that size, you probably have at least a few seniors or principals that can take it on.
Also, with 25 direct reports you’re practically a Director without any supporting management under you. It’s entirely possible that you’re being underpaid, especially if this arrangement pushes you into overtime (more than 40hrs a week) a lot.
I work in the planning/building department. We review and permit developments.
The developers aren’t my staff, they’re applicants who want to build something and we have to review it for drainage, engineering, building code, lighting, environmental impact, septic/sewer, etc.
chiliedogg@lemmy.world 5 days ago
In my case, I work for a municipality and I legitimately do need to be in the office to meet with citizens, attend public hearings, etc. abut I think they could come up with a schedule where I work remote on Mondays and Fridays or something. It would also make those days “no meeting days” so I could catch up on my actual job.
We get raked over the coals for how long development review takes, but then every developer wants to meet with us for an hour every week, so instead of reviewing plans we’re attending meetings 25 hours a week where they’re bitching at us for how long it takes us to review their plans.
Valmond@lemmy.world 5 days ago
You’re managing 25 developers?! That’s way too many IMO!
chiliedogg@lemmy.world 5 days ago
Not software development. Municipal development.
I work in the planning/ building department. We review and permit developments.
Valmond@lemmy.world 5 days ago
Aah okay that clears it up, cheers!
dejected_warp_core@lemmy.world 5 days ago
Okay, here’s some unsolicited advice from an IT manager. Please take with a heap of salt.
25 hours is too many for 1:1 weekly meetings unless that’s your whole job description. That leaves 15 hours for overhead, project management, team meetings, leadership meetings, scrum-of-scrums, town halls, mentorship, breaking ties on MRs, etc. At that scale, and assuming you have other responsibilities, 1:1’s really should be monthly, optional 3/4 of the time, or cut back to 15 minutes unless there’s an ask for more time. Also: ya gotta delegate those plan reviews if you can. With a labor pool that size, you probably have at least a few seniors or principals that can take it on.
Also, with 25 direct reports you’re practically a Director without any supporting management under you. It’s entirely possible that you’re being underpaid, especially if this arrangement pushes you into overtime (more than 40hrs a week) a lot.
chiliedogg@lemmy.world 5 days ago
Not software development. Municipal development.
I work in the planning/building department. We review and permit developments.
The developers aren’t my staff, they’re applicants who want to build something and we have to review it for drainage, engineering, building code, lighting, environmental impact, septic/sewer, etc.