There once was a time in my life that I would assume some of my ideas or requests would automatically be squelched with a “no” answer. My assumption would actually limit me from even asking or discussing the request or idea. One thing is for sure -the answer will always be “no” to something that’s not asked.

I had to get over the fear of “no.” In light of many other things in work and care, being told no is not really that big of a deal, but when you’re told no over and over again, you can start to think your ideas are rubbish and simply stop generating ideas altogether. That’s not good for any organization.

“No” for the sake of “no” has never really set well with me; I have always wanted to know the why behind the answer. Most people are this way, which is why leadership communication is important to validate ideas and questions. Just because the answer is no doesn’t mean the idea or request wasn’t valuable. I’ve learned that both when I’m told no with an explanation or I do the same thing with those who follow me, often times a subsequent idea results to overcome the explanation’s barrier. It’s a beautiful thing – respectful, transparent communication.

Receiving a “no” answer is really no big deal, but it does take practice – just like everything else – to maintain professionalism and competency within the situation. “No” comes in all forms, but it mostly signifies the opportunity to grow – to research more, collect additional data, strengthen a business case. It’s a stepping stone rather than a stumbling block.

Get over your fear of “no.” Just ask.