3 ms·

I’ve been in your shoes. Hats off to you for trying to do right by your team. I’ve had success with coaching my employees to refuse any meeting invite that woul

I’ve been in your shoes. Hats off to you for trying to do right by your team. I’ve had success with coaching my employees to refuse any meeting invite that would not directly help them do a better job. We’ve come up with verbiage to help redirect meetings to me so that no hard feelings could crystallize on the other side. This works except in a small minority of cases: some individual contributors enjoy their meetings. It’s not my place to stop them.

wastedhours 8y ago
> This works except in a small minority of cases: some individual contributors enjoy their meetings. Also in a small minority of cases breaking up a developer flow to provide on the ground context in a meeting is better for the organisation than keeping the developer in-flow for another hour. Rarely, I'll concede, but it's worth remembering that few developers are paid to "code", but to create value for the organisation. The vast majority of the time that's done by coding, but sometimes (in those rare moments) that value is derived from a meeting.