5 ms·
Another key thing is: do _less_ stuff _better_. And by “less” here I mean concurrent projects, not necessarily less work. I had 17 (yes, _seventeen_) calls las
by rcarmo 6y ago
Another key thing is: do _less_ stuff _better_. And by “less” here I mean concurrent projects, not necessarily less work.
I had 17 (yes, _seventeen_) calls last Friday (between 15m to an hour), mostly because I am involved in six (now seven) concurrent activities (some just starting, many ongoing) and they bunched up on the last possible day of the week.
This is a intolerable pace, obviously, so I’m taking some drastic measures, but I already had Cortana booking me 3-hour blocks of “focus time” every day to “sandwich” that cheese, so the next step is to start booking off entire days.
- anticristi 6y agoNot saying that I like it, but I see this as a consequence of moving higher up the ladder. In 15 min, a senior architect can take a decision that potentially saves a junior developer 1 day of work. So, while the architect can't really "do" anything, overall team performance increases. Although I like minimizing interruption, I also accepted delegation as a way to make "myself" productive in the face of many interruptions.
- sverhagen 6y agoI had to learn, and try to tell others every chance I get, that moving up that ladder will come with relearning how to manage your time, and learn to get gratification out of different things than earlier in your career. If you don't, you'll always walk around with the feeling that you didn't get any work done.
- anticristi 6y agoThat's exactly where I am at. Super-busy but not getting any work done. Thanks for the insight!