3 ms·
> Of course, that wasn't scalable. As opposed to this approach? I have my doubts. Of course, if you are a developer that's very important to the company, you m
by rob74 6y ago
> Of course, that wasn't scalable.
As opposed to this approach? I have my doubts. Of course, if you are a developer that's very important to the company, you may have the clout to push this through (which may then be perceived as a privilege given to you by colleagues: "ah, so-and-so is so important that he gets his undisturbed time, and we others have to schedule our meetings around him"), but what if everyone would be given the right to block off large portions of their calendar as they please? That would make it almost impossible to schedule meetings with a significant number of participants. For this to work, it would have to be embraced company-wide, e.g. a policy of "no meetings on Wednesdays and Fridays". Having customers involved further complicates things...
- aliceryhl 6y agoIt obviously depends on the company, but it is possible in lots of places.
- jon-wood 6y agoIt's really not that difficult so long as you allow a bit of flexibility. My team has a general rule that we schedule meetings in the morning, leaving afternoons free for focused work, but obviously if there's something that needs discussing with customers or other teams and the only time available is in the afternoon then we'll adapt to that. I also fairly frequently block out chunks of time to get actual work done - every now and then someone will ping me and ask if there's any flexibility, rather than just assuming I'm completely unavailable for the next week. People aren't robots, they'll get used to it.