DEV Community

Discussion on: Why knowing how to say "no" is important, and how to do it

Collapse
 
ghost profile image
Ghost

Good points but use with caution, specially with the "calendar check" I prefer that someone says not to me, then I know their answer. I my country, I don't know if is a cultural thing, nobody says no, always let me check, maybe; never no, so in your equations you have just a bunch of blurry half answers. Try to reuse a no not avoid it, a yes is a yes a no is a no. Said that, don't be a jerk about it. I find more useful a "no, but" and maybe suggest an alternative, or "not now" followed by a date not "in some murky future". Over the years and probably more because of my environment I appreciate clear concise answers. You mean no, well, say no, if you can think in an alternative, better. But if you can't let me just move on knowing that, now I know what my resources are instead os a dozen maybes that are most likely polites 'no' and I'll probably will find out too late.

Collapse
 
codingmindfully profile image
Daragh Byrne

A fair point. There are certainly cultural considerations I've not addressed! Saying "no" clearly is the ultimate way to do it really! These techniques can help you get there if you are not already used to it.

Speaking with authenticity is crucial to being taken seriously in the long run. So use these techniques, but say what you mean!