Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / How to Recover When Your Boss Rejects Your Idea
Transcript
- Lucas: So you're in a meeting. You've prepped for days. You lay out your idea — maybe a new process, maybe a product tweak — and your boss says, 'That doesn't work for us' or 'We tried that before.' In front of everyone. And now all eyes are on you. Luna: That specific silence — the one where you can feel your face get warm — it's brutal. And the instinct is to defend yourself immediately, right? Lucas: Exactly. And that's exactly what kills your credibility. The moment you get defensive, you confirm the subtext — which is that you're attached to the idea as a reflection of your worth. So the first move is counterintuitive: say nothing for two full seconds. Luna: Two seconds feels like an eternity in a meeting. But it works because it signals composure. Lucas: Right. You're not frozen — you're processing. Then you say something like, 'That's helpful context. Can you help me understand what specifically doesn't land?' You flip from defending to learning. And that changes the entire dynamic. Luna: I love that framing. You're not arguing — you're inviting them to teach you. And most bosses actually want to teach, especially if they respect your intent. Lucas: There's a real example I use with my coaching clients. A senior product manager at Nike — let's call her Priya — pitched a sustainability tracking feature for the SNKRS app. Her VP killed it in under a minute in a quarterly review. Said the engineering cost was too high and the user data didn't support it. Luna: Ouch. In front of the whole product org, I'm guessing. Lucas: Twelve people. She felt her face flush. But she'd practiced this exact move, so she took a breath and said, 'Understood. What would the threshold need to look like for the data to make this viable?' Notice — she didn't ask to revisit the decision. She asked for the criteria. Luna: That's the key difference. She's not reopening the case — she's gathering intelligence for the next pitch. Lucas: Exactly. Her VP said they'd need at least 15 percent of beta users to engage with a sustainability badge within the first two weeks. Priya wrote that down. She spent the next quarter building a lightweight prototype with a two-person engineering team during a hackathon, got 22 percent engagement, and came back with a three-month phased rollout. That feature is now live and drives about 4 percent of weekly active user retention. Luna: And the VP probably remembers her as the person who took a no and turned it into a smarter yes. That's a career-defining reputation. Lucas: It is. And the structure is repeatable. Step one: absorb without flinching. Step two: ask for the specific criteria behind the rejection. Step three: go away, solve for those criteria, and come back. Luna: What about situations where the rejection feels personal? Like your boss says, 'This is naive' or 'You don't understand our business.' Lucas: That's harder. But the same move works if you detach from the tone. You can say, 'I clearly have a gap in my understanding. Can you point me to the data or the precedent that shapes your view?' You're not arguing the insult — you're asking for the evidence. And if your boss is reasonable, they'll supply it. If they're not, you've learned something about the culture. Luna: So the recovery isn't about the idea — it's about the relationship. You're showing you can handle feedback without ego. Lucas: Exactly. And that's a skill that compounds. Every time you handle a rejection well, you build political capital. People start bringing you into rooms because they know you won't melt down. Luna: Let's talk about the follow-through. You get the criteria, you go build or research — how long should you wait before circling back? Lucas: As long as it takes to meet the criteria — but no longer. Priya took a quarter. If you say you'll come back in two weeks, come back in two weeks. Don't let it drift. And when you return, frame it as, 'Based on our last conversation, I looked at X and Y. Here's what I found.' You're showing discipline and respect for their time. Luna: One thing I'd add: sometimes the rejection is actually correct. The idea truly won't work. And that's okay — you still get credit for how you handled it. Lucas: Absolutely. In fact, I'd argue that's the more common scenario. Most ideas get rejected for good reasons. But the person who can accept that gracefully and pivot to the next thing is more valuable than the person who fights every losing battle. Luna: There's also a subtle power move here: if you've done the work and the criteria shift, you can gently call that out. Like, 'I addressed the three points we discussed, but I understand the landscape has changed.' That shows you're paying attention to the broader context, not just your agenda. Lucas: That's a pro move. And it ties back to the core principle: the idea is not you. The rejection is not personal. Your reaction is the only thing you control. Luna: If today's episode helped you think about a recent rejection — or one you're dreading — we want to mention something quick. Lucas: Yeah. This show stays ad-free because listeners who find value here sometimes toss a few dollars our way. If today's approach was useful to you, the way to keep these episodes coming is a small contribution at buy me a coffee dot com slash fexingo. No pressure — just a way to keep the conversation going without commercials. Luna: We really appreciate that. Now, let's get back to the playbook. Lucas, you mentioned that Priya's VP gave her a numeric threshold. What if the rejection is more ambiguous — like 'it's not a priority right now'? Lucas: That's a classic. 'Not a priority' is often code for 'I don't see the value' or 'I don't trust the estimate.' Your move is to ask, 'What would need to change for this to become a priority?' If they give you a condition, great. If they waffle, you know it's a soft no, and you can park it and revisit in six months. Luna: Or sometimes it's a budget issue. They like the idea but can't fund it. In that case, you offer to pilot with existing resources. Lucas: Right. That's how Priya got her prototype built — she used a hackathon. The best ideas often start as side projects that prove themselves. Luna: One last scenario: what if the rejection comes from a peer, not your boss? A colleague who blocks your idea in a cross-functional meeting. Lucas: Same playbook, but you have less authority. So you lean more on curiosity: 'Help me understand your concern. What data would make you comfortable?' You're not trying to win — you're trying to find the overlap. And if there's no overlap, you escalate through your boss. Luna: That's a good note to end on. The recovery move works because it's respectful, curious, and forward-looking. It turns a moment of potential shame into a demonstration of leadership. Lucas: And the next time you pitch something and get shot down — and it will happen — you now have a script. Breathe, ask for the criteria, go solve, come back. That's how you turn a no into a not yet.