Here's how to buy time and look smart

Leadership just told you to ship by end of quarter.

They don't care about "running a discovery sprint". Rightfully so.

But you know the product isn't ready.

Nobody talked to customers. Everything is an internal assumption.

But its worse - if you push back, you'll look like you're stalling.

So what do you do?

You need one sentence that reframes discovery as speed, not delay.

Here's what's inside:

• Exact script to use with leadership when they say "ship now"
• 3-steps to de-risk in 1 week without looking like you're stalling
• How to present evidence that earns trust and gets buy-in

Want to learn how to Prompt Engineer your Discovery sprint? Join my free workshop What is prompting? How to write a good prompt Leave having set up your own prompt Sign up for free

The script that changes everything

Most PMs push back with: "I need more time to talk to customers."

Leadership hears: "This PM is slowing us down."

To not look like you're stalling, say this:

"I want to make sure we're building the right thing so we don't waste engineering time. I think [Riskiest Assumption] could tank our launch. Do you think this is a risk? I need 1 week and 5 conversations to de-risk the bet."

Notice what this does:

• You're giving leadership a specific timeframe.
• You're accelerating success, not slowing it down.
• You're not asking for permission to "run discovery"—you're asking for permission to de-risk.

Here's how to execute on that promise.

3-steps to de-risk the launch

Step 1: Identify the Riskiest Assumption

You don't have time to validate everything.

Pick the one assumption that, if wrong, would kill the launch.

Write out all your assumptions about the product.

Then, ask yourself: "Which belief do I feel least confident about?"

That's the Riskiest Assumption to test.

​Use my Build with Conviction workbook to do this in <10 minutes.

Step 2: Run 5 conversations and synthesize with AI

You need 5 conversations with the right people.

Internal conversations count. Talk to Sales, Customer Success, or anyone who's close to the customer.

External conversations are better. Reach out to 10 people, get 5 on the phone.

Good questions:

• "Tell me about the last time you faced [problem]."
• "How are you solving it today?"
• "What's painful about that solution?"

After 5 conversations, feed your transcripts to AI with your Validation Stack.

Ask AI: "Did these interviews validate or invalidate my Riskiest Assumption?"

AI will give you patterns, quotes, and evidence.

Step 3: Run 5 conversations and synthesize with AI

Now go back to leadership with data, not opinions.

Leadership respects evidence.

You now have one of three answers:

1. Build: The assumption passed. You have evidence. Go build with confidence.
2. More Discovery: You need 2-3 more conversations to confirm the pattern. (If you're still here after 5-10 interviews, that's usually a Pivot.)
3. Pivot: The assumption failed. Congrats—you just saved the company months of wasted development.

Present it clearly: "Based on these conversations, here's what we should do next and why."

This is how you earn trust with leadership.

You didn't stall.

You de-risked the launch in 1 week and came back with a recommendation they can act on.

The Takeaway

Leadership doesn't want to wait for discovery.

They want to ship fast and hit metrics.

Use the script above to give yourself to de-risk the launch.

This reframes discovery as speed, not delay.

And makes you the smart PM.

From Insight to Action

• I built a cohort course to make every PM an expert in customer discovery. Check it out. 🚀
• Ask me Anything about Customer Discovery & Product - Sign up for free