The Exec Asked for an ETA in the All-Hands. You Made One Up.

The CEO is on stage, wrapping up the quarterly all-hands. You’re halfway back in the room, thinking about lunch. Suddenly, you hear your name.

“And speaking of our new checkout flow, Sarah is here. Sarah, stand up. Great work from your team. When can we tell customers this is shipping?”

Two hundred pairs of eyes turn to you. Your engineering lead, sitting three rows ahead, slowly turns around with a look of pure terror. Your mind is a blank slate. There’s a plan, sure. There are dependencies. There’s a cone of uncertainty. But the CEO is smiling, waiting. The silence stretches.

“End of Q3,” you blurt out.

The CEO nods. “You heard it here first. End of Q3. Great stuff.”

You sit down, heart pounding. You just traded a year of your team’s credibility for 30 seconds of not feeling awkward.

A Guess Isn’t a Forecast. It’s a Debt.

That number you just invented isn’t an estimate. It’s a commitment, broadcast to the entire company. Marketing starts drafting launch campaigns. Sales starts whispering dates to prospects. Customer Success starts prepping their teams.

You just took out a high-interest loan from the Bank of Credibility, and your engineering team is going to pay for it.

When you inevitably miss that date, the damage is widespread.

• Your team is demoralized. They are forced to rush, cut corners, and burn out chasing an arbitrary deadline they had no part in creating.
• Your stakeholders lose trust. The next time you give a date, they’ll mentally add a few weeks to it. Your word is devalued.
• You look like you don’t know your own product. The one person who is supposed to have the master plan just proved they’re guessing.

Refusing to give a date on the spot feels like a failure of confidence. It’s not. It’s a demonstration of discipline. Your job isn’t to have every answer, but to have a process for finding the right one.

The Playbook: Redirect, Reframe, and Follow Up

You can’t just say “I don’t know.” That’s a career-limiting move. Instead, you need a prepared response that answers the unasked question—"Is this project under control?"—without committing to a date you can’t defend.

Here is the four-step play.

1. Acknowledge and Validate

First, show you heard the question and agree with its importance. This buys you a precious few seconds to think and shows respect for the person asking.

Say this: “That’s the number one question on our minds, too. We’re all incredibly excited to get this into customers’ hands.”

2. State What You Know for Certain

Instead of the unknown (the final date), talk about what is known. Focus on recent progress or the value you’re working to deliver. This shifts the focus from the calendar to the customer.

Say this: “Right now, the team is heads-down on the payment processor integration, which is the most complex piece of the puzzle. We just got the final API credentials from their team, which was the last major blocker.”

3. Frame the Next Concrete Milestone

You don’t know the final ship date, but you absolutely should know the next immediate step. Talk about that. It shows you have a plan and are focused on execution, not just wishful thinking.

Say this: “Our next step is to get a build into the QA environment for end-to-end testing. We’re targeting the end of next week for that.”

4. Promise a High-Fidelity Answer Offline

This is the critical move. You redirect the conversation from the public forum to the proper channel. You aren’t dodging the question; you are promising a better, more accurate answer later.

Say this: “That testing will give us the final data we need to lock in a firm date. I can circle back with you and the leadership team with a high-confidence timeline by Thursday.”

You just turned a moment of high pressure into a demonstration of competence. You validated the exec’s question, showed progress, articulated a clear next step, and committed to a proper follow-up.

No guesses. No chaos. Just good product management. Keep this script in your back pocket for the next time the spotlight finds you.