Ok, I agree with some of what he's saying, he says: "It can wait a day". Well, yes. In theory. The truth of the matter is that if you're doing actual client wo

Ok, I agree with some of what he's saying, he says: "It can wait a day". Well, yes. In theory. The truth of the matter is that if you're doing actual client work, you have to contact the client, then you might have to pinball things with your programmer or your designer or whatever, those things take time. If they all wait a day, and the client waits a day for you, before you know it, it's been a week. Maybe two weeks, and you don't have a clue why it took so long. This is just one example. Of course this totally depends on what line of work you're in, but that's maybe my point. Not all companies are 37signals working on a SaaS product. If you take a week to respond and do something for your client and your competitor does it in a day, you're going to lose. Of course reducing interruptions is paramount for any business, but you can't get rid of them completely in most fields. You just have to control the interruptions, learn to distinguish between important and not so important stuff, keep as much communication in an asynchronous manner as possible, but when you need something asap, you need it asap. Sorry for the long winded response.