Oh, so do I (and I'm more often on the receiving end, too). No question, there's a cost to being interrupted. Personally, I have to actively push back against

Oh, so do I (and I'm more often on the receiving end, too). No question, there's a cost to being interrupted. Personally, I have to actively push back against my own displeasure at being interrupted. At the end of the day, though, the value those interruptions bring to the project make them worthwhile. Problems are avoided before they become problems. Knowledge is transferred without forcing someone to learn it from the ground up themselves. Time is saved (maybe not my time, but project-time). (Obviously, if you're consistently being interrupted with low-value, easy-to-answer questions, that's a bit different... there comes a point where you say "ok, spend a bit more time, and if you can't get it then I'll work more with you")