Earlier quoted context omitted.
I love that idea! We are talking to a lot of people in Product roles to do just that. Basically blocking times or days out with no interruptions, as well as giving them the insight to protect their teams so they can work.
That sounds interesting - got me thinking a little more about this. I wonder if simply by making the information available on when people are in flow state, a lot of flow state interruptions could be reduced, even without reducing the number of meetings. In particular, encouraging scheduling a meeting at the beginning / end of a flow state period rather than slap bang in the middle would have a big impact. For exampl…
Second, you can't just move meetings around, in my experience. Once something is scheduled, it calcifies; it's too much work coordinating time zones and schedules, and if you push something up, most people that were planning on it being later will be even more unprepared to discuss than usual.