Imagine this. The CEO (or another senior leader) approaches you with a new feature idea. Not as a suggestion — but as a directive.
👉 “We need this ASAP. Just build it.”
Sounds familiar? At this moment, you face a dilemma. Push back too hard, and you risk being seen as resistant or difficult. Comply without question, and you might waste valuable resources on an unvalidated idea, not to mention the effect it has on your teams’ morale.
So, how do you respond without immediately saying No while still steering the company toward outcome-driven decisions rather than feature-driven execution?
Step 1: Shift the Conversation from Features to Outcomes
When a CEO makes a request, their underlying goal is usually a business outcome, not the feature itself. Your job as a Product Manager is to uncover the real need.
❌ Instead of: “That feature doesn’t align with our roadmap.”
✅ Try: “I’d love to understand the problem this is solving. What’s driving this request?”
Step 2: Bring Data into the Discussion
Leadership responds well to data-backed arguments. If an idea isn’t validated, frame the conversation around learning first, building second.
❌ Instead of: “This is a bad idea.”
✅ Try: “Great idea! Before we build it, let’s run a quick test to see if it resonates with users.”
Example from My Experience
At Grover, a strong senior executive working closely with leadership once requested a major homepage change. Instead of immediately executing, I provided data from user research and analytics that showed the existing design was not the problem. The result? He dropped the request.
A year later, he told me that moment gave him a lot of respect for me — because I challenged a directive with evidence, not opinion.
Step 3: Propose a Low-Risk Experiment
Instead of outright rejecting a leadership request, reframe it as a learning opportunity. Dive into the Problem Space and find ways to explore.
❌ Instead of: “We don’t have time for this.”
✅ Try: “Let’s run a quick test to measure impact before investing full development resources.”
Tactical Approaches
- 🚀 Fake Door Tests: Launch a small-scale version (e.g., a landing page) to gauge interest and see how your users react.
- 🚀 Prototype & User Interviews: Figure out your customers jobs and their pain points. Conduct design sprints or mockup tests before building.
Step 4: Align on Decision-Making Criteria
Leadership may still push for a feature, even after testing. To avoid never-ending debates, establish agreed-upon decision criteria:
Questions to Ask:
- Does this align with our OKRs and company goals?
- What’s the expected business impact?
- What problem does it solve for users?
- What’s the opportunity cost of building this vs. another initiative?
By structuring conversations this way, you move from opinion-based to evidence-driven decision-making.
Step 5: Communicate Trade-Offs, Not Just Objections
CEOs and executives don’t like hearing “no.” But they do respond to trade-offs.
❌ Instead of: “We can’t do this.”
✅ Try: “To build this, we’d need to deprioritize X. Is this the highest priority for the business right now?”
Why This Works
- It forces leadership to weigh business priorities, not just pet projects.
- It shifts ownership of the decision back to them.
- It makes the discussion collaborative, not adversarial.
Final Thoughts: Product Leaders Facilitate, Not Just Execute
Pushing back on feature requests isn’t about rejecting ideas — it’s about ensuring the best decisions get made.
When a CEO says, “Just build it,” your goal isn’t to fight them. It’s to guide them toward customer-centric, outcome-driven product decisions.
✅ Highlight trade-offs and opportunity costs.
✅ Frame the request as an experiment.
✅ Agree on decision-making criteria.
✅ Use data to inform discussions.
✅ Uncover the real problem.
By applying this approach, you protect product integrity while maintaining leadership trust.
How did you handle such situations in the past? Please share.
Enjoyed this article? Let’s continue the conversation on LinkedIn!
I regularly share insights on Product Discovery, Outcome-Driven Product Management, and Strategic Product Leadership.
Follow me HERE and let’s connect!