Returning to my own example, it's a similar commitment that enables me to succeed with fixed scheduling. I, too, am incredibly cautious about my use of the most dangerous word in one's productivity vocabulary: "yes." It takes a lot to convince me to agree to something that yields shallow work. If you ask for my involvement in university business that's not absolutely necessary, I might respond with a defense I learned from the department chair who hired me: "Talk to me after tenure." Another tactic that works well for me is to be clear in my refusal but ambiguous in my explanation for the refusal. The key is to avoid providing enough specificity about the excuse that the requester has the opportunity to defuse it. If, for example, I turn down a time-consuming speaking invitation with the excuse that I have other trips scheduled for around the same time, I don't provide details-which might leave the requester the ability to suggest a way to fit his or her event into my existing obligations-but instead just say, "Sounds interesting, but I can't make it due to schedule conflicts." In turning down obligations, I also resist the urge to offer a consolation prize that ends up devouring almost as much of my schedule {e.g., "Sorry I can't join your committee, but I'm happy to take a look at some of your proposals as they come together and offer my thoughts"}. A clean break is best.
( Cal Newport )
[ Deep Work: Rules for Focused ]
www.QuoteSweet.com