The Anatomy of a Bad “No”
...and how one word from a CEO taught me everything about how to give—and receive—rejection.
So, I remember one particular Monday morning years ago.
I arrived at work early after spending most of the weekend working on an idea that initially came to me Friday night while watching TV. It was one of those moments when, if your head flew back, it would have made sense, as that idea just struck me.
Over the next few days, I constructed a narrative, a budget, and revenue models. I even researched the space and built out my elevator pitch.
By the time Monday morning rolled around, I was jumping to present it to my CEO.
I chose not to ambush him on his way into the building, but to wait until he was done making his “rounds” of the staff and had a cup of coffee. Once I knew he was safely behind his desk, I gathered up my materials and knocked on his door.
He looked up from his computer long enough to realize it was me and turned back to the screen before verbally acknowledging it was me.
I explained that I had this great idea that came to me while watching TV and that I wanted to walk him through it. If he was annoyed by my presence, I couldn’t tell. He told me to take a seat at his conference table and that he would join me as soon as he was done sending an email.
A few moments after I sat down, he joined me with a jovial “What’s on your mind?”
I again explained that the idea came to me while watching TV and that I had spent the weekend researching it, building out revenue projections, a 3-year budget, and a competitive analysis.
I walked him through everything, even at one point, nailing the elevator pitch that I had practiced in front of my wife, the bathroom mirror, the car mirror, and even the mirror in our office bathroom.
Whether it was 15 minutes or over an hour, I really couldn’t tell you. All I know is that when I reached the end, I sat back, took a sip of water, and waited for his encouraging and supportive words.
He looked at me, surveyed the papers now strewn across his conference table and back at me without saying anything.
So I spoke first.
“So, what do you think? Isn’t this great?”
Still nothing.
“It makes sense, no? Can we do it?”
At that moment, he drew a breath, I think he looked at his watch, before looking at me again and saying:
“No.”
And that was it. No.
He didn’t ask for any additional changes or refinements. He just said “no.”
I must have been a bit stunned, but I started gathering my materials, which he took as a sign that I was leaving. He stood up, muttered something along the lines of “thanks for the effort,” before walking back to his desk.
I headed back to my office, trying to figure out what “no” meant.
It wasn’t the first time in my career that I had received a “no” to an idea.
But I have realized that a “no” without a “here’s why” is the worst kind of no.
So, in the many times since that I have replayed that moment in my head, I’ve tried to figure out how he could have done it differently. And just as importantly, how could I have done it differently?
But let’s start with him, the CEO.
The Leader’s Mistake: When “No” Is a Full Stop
Look, I get it. The job of a leader is full of tough decisions. You can’t say ‘yes’ to every idea that comes your way. It doesn’t matter how much time you spent on it over the weekend.
But the ‘no’ that he gave me wasn’t just a ‘no.’ It was a door slamming shut. It was a full stop.
A good leader knows a ‘no’ should never be a full stop. It should be a redirection. It’s a teachable moment. A clarification moment. Or a pivot moment. He had so many other options and, more importantly, all of them were better than the silent treatment.
1. The “No, because...” (The Strategic No)
He could have given me the “No, because...” This is the strategic ‘no.’ It’s the one that actually respects the work you just spent hours on.
It might have sounded like, “No, because our entire R&D budget is tied up for the next six months.” Or “No, because this is a mission creep we can’t justify right now.”
When you get a ‘no’ like this, you aren’t just being told ‘no.’ You are being taught. You are getting a peek right into the heart of the business strategy. Right into the leader’s head. The next time you come to that person with an idea, it’s that much better because of this no.
2. The “Not now...” (The Timing No)
That’s the ‘no’ that’s really about timing. He could have looked me straight in the eye, after praising all the work I had done (see a lot of ‘could haves’ here), and said, “This is great work, I see the passion and the time you have put in, but we don’t have the resources to do it right now. We would be doing you and this project an injustice. Can you bring it back to me in the third quarter?”
A ‘no’ like that affirms the work. It affirms the idea. It keeps you in the game and tells you your work has value, even if the timing is wrong.
3. The “No, but...” (The Pivot No)
Then there’s my favorite, if such a thing exists. The “No, but...” This is the ‘no’ with a pivot.
“No, we can’t fund the full proposal. But that competitive analysis you did? We need more like that. Can you pare back everything else and focus on just that piece?”
The ‘no, but’ is gold. It turns the person who just got shut down into a problem solver. It takes the leader, who probably also had an idea without the budget or resources, and actually did something with it. That’s true leadership.
My Mistake: How I Let “No” Win
But it wasn’t just the CEO who had done it wrong. I had, as well.
My response was as much of a dead end as his was. I was stunned, so I grabbed my papers and left. I left, period. I returned to my office to try to figure out what his ‘no’ meant.
That was the mistake. I let his ‘no’ end the conversation.
Instead, I wish I had just taken a breath, a single one, and got curious instead of defeated.
Ask “What,” Not “Why”
I wish I hadn’t asked, “Why not?” That just sounds defensive. It puts the leader on the spot. Instead, I should have asked, “What?”
“Thanks for the clarity. I want to learn so what was the biggest obstacle for you? Was it the budget, the timeline, or was it the strategic fit?”
See the difference? You’re not arguing. You’re collecting data points for your next pitch.
Salvage the Parts
I also could have tried to salvage the parts. My idea was an all-or-nothing package deal, right? The research, the budget, the story. But the package may have been a ‘no’ but were the pieces a ‘no’ too?
“While I think the project overall is a no, was the research I did on our competitors useful? I’d be happy to share that with our marketing team.”
This says you are mature and that you care more about the company’s success than your own idea’s success.
A ‘no’ is just a moment in time. It’s a data point. The mistake, for both the leader and the person getting a ‘no,’ is treating it like a final judgment.
It’s not. It’s just the start of the next conversation.
What do you think? Have you ever received a “no” that taught you a valuable lesson? How do you handle giving or receiving rejection?
P.S. - If you found this post helpful, would you please consider restacking it and sharing it with your audience?
This spreads the word and keeps me writing the types of content that you have enjoyed.