That sounds like a strict requirement for remote work to work, and intuitively so. In your experience, how was the training done for less experienced IC ?
That sounds like a strict requirement for remote work to work, and intuitively so. In your experience, how was the training done for less experienced IC ?
Since managers have power, and engineers usually don’t personally know their skip levels, managers can easily replace async documented process with lovely hours-long face-to-face 20-person meetings. And they can silence dissent! They can wreak havoc in a way no IC could ever do.
This has been a particular pain-point for me at times. Example: two meetings with the same team members on two connected subjects of about 45mins to an hour in length, spaced half an hour apart when they could easily be combined. That's just in one day. There are others that have mirrored those throughout a week. The meetings don't need to be as long as they are, but they're scheduled for that long and the rest of the time is often filled with awkward chit-chat. But it fills the manager's calendar slots so that they appear effective, even if a lot of time is being squandered. Add on all the frustration of the back and forth across floors, wandering the halls looking for a meeting room that isn't double-booked or waiting on people to vacate rooms, etc etc.
IC time is more directly controlled this way. Occasionally it makes sense, but the amount of duplication is, at times, staggering and can be frustrating.
My complaints are probably less about co-located offices and more just corporate cruft.
Their core business was management consulting.
Has anyone ever promoted a manager because they have so many meetings?
[0]: https://en.wikipedia.org/wiki/Professional-managerial_class
I expect to find useless and inappropriate comments downvoted, but there is no official policy that I remember, so those are only my ideas of how downvoting would help moderate a discussion.