From an organizational perspective, this is horrible advice:
> Let me tell you clearly. “No” is a complete sentence. It requires no explanation or defense.
The "It requires no explanation or defense" part is just plain wrong. If someone asks you to do something in an organization, it's fine to say "No", but an explanation is nearly always expected. And this explanation is critical, because often time the answer is something like "I don't have time", when a positive, helpful rejoinder would be "What else would you like me to stop doing if you want me to do this other thing."
This advice really just seems to my like something the "arrogant tech support guy" from SNL would say.
> Let me tell you clearly. “No” is a complete sentence. It requires no explanation or defense.
The "It requires no explanation or defense" part is just plain wrong. If someone asks you to do something in an organization, it's fine to say "No", but an explanation is nearly always expected. And this explanation is critical, because often time the answer is something like "I don't have time", when a positive, helpful rejoinder would be "What else would you like me to stop doing if you want me to do this other thing."
This advice really just seems to my like something the "arrogant tech support guy" from SNL would say.