This is so true. At Vibinex (and even in GetMega, where I used to work earlier), we used a tool called Clockwise. It's main feature is that it optimizes the schedule of the entire team to maximize the number of focus hours on every engineer's schedule.
Not only that, but the fact that we use a tool like this (and pay them) also sends a clear message to everyone in the team (especially people not in the tech team) that we really value focus time and that we shouldn't be disturbed when we are in the flow.
On top of it, we also maintain that if, say as a PM, you want to get the attention of the developer. Then, if they are in the focus-time, then you must approach the EM instead of directly pinging or approaching the engineer. This way, urgent tasks are also handled without delay.
Great thought - thanks for sharing Avikalp. There should be certain communication processes defined to ensure the team gets their focus time while balancing urgent requirements.
This is so true. At Vibinex (and even in GetMega, where I used to work earlier), we used a tool called Clockwise. It's main feature is that it optimizes the schedule of the entire team to maximize the number of focus hours on every engineer's schedule.
Not only that, but the fact that we use a tool like this (and pay them) also sends a clear message to everyone in the team (especially people not in the tech team) that we really value focus time and that we shouldn't be disturbed when we are in the flow.
On top of it, we also maintain that if, say as a PM, you want to get the attention of the developer. Then, if they are in the focus-time, then you must approach the EM instead of directly pinging or approaching the engineer. This way, urgent tasks are also handled without delay.
Great thought - thanks for sharing Avikalp. There should be certain communication processes defined to ensure the team gets their focus time while balancing urgent requirements.
May the 'flow' prevails! :D