|
|
|
|
|
by p_l
1807 days ago
|
|
The problem is that most of that is work, sometimes considerable work. However sometimes interruptions are impossible to avoid, and also you need to do some of that work anyway. Generally you want at least the following two tools to handle it: "interrupt shield" mechanism - it involves having a set time for answering interruptions, and if you have more than one person on the team, having them cover different time frames as the point of contact person. Setting expectations about time frames for reaction etc and enforcing them. Which means not just making sure you answer on time, but also to ensure you don't unnecessarily overcommit. Do not create an expectation of jumping to it. |
|