Why "I Didn't Hear Anything New" Is the Product Leader's Real Win - Product Builder Podcast episode with Eyal David
00:04:07

Why "I Didn't Hear Anything New" Is the Product Leader's Real Win

Host: · Guest: Noa Ganot

In this episode

  • Tell yourself the story of why you're doing something before you ask others to execute it — it's a hard exercise that people avoid, but it's the foundation of any convincing strategy.
  • A good story is built through patient draft work, sentence by sentence ("ping pong"), until you yourself read it and believe it — and you eliminate the holes in the plot.
  • When a CEO says "I didn't hear anything new here," it may be a sign of success: you hit exactly on his real intent and organized it so that management finally understands it too.
  • A product leader is responsible for leading the company in the right direction, not just running the product department — it's far too easy to sink into day-to-day management and miss this.
  • Product in a product company is the central business instrument; if the product can't be sold and can't deliver results, you're building pretty things in the sand.

Episode Description

Noa Ganot breaks down why product managers fail to move the executive team: it's not a shortage of slide decks, it's the lack of a story that explains the why. Through an anecdote about a VP Product who presented at a management meeting and heard the CEO say "I didn't hear anything new here" — which was actually the win — she shows how to build the logic of a story that leads the company in the right direction, and why that is the essential job of the product leader, not just running day-to-day operations.

Read the full transcript
Full transcript with speakers and timestamps

Selected quotes

“Product in a product company is the central business instrument the company decided to take to the world and achieve its goals with.”
— Noa Ganot
“If you're a product leader who doesn't know how to be sold and doesn't know how to bring the company to results, it's a bit like you're playing in the sand and building pretty things.”
— Noa Ganot
“The very fact that he said he didn't hear anything new — as far as I'm concerned that's excellent, because it means we hit on something he really meant.”
— Noa Ganot

Questions & answers

Why do you even need to tell the why, rather than just present a plan?

Because giving the "why" answer is usually not self-evident — there are a million holes in the plot. A story that explains why these steps will bring us to the desired point is what makes people believe and get on board, as opposed to a deck that only describes what you're doing.

How do you actually build the story?

Through close, shared draft work, going sentence by sentence: what do I understand from this sentence, did I understand you correctly or is something else hidden here — until you put the logic of the story in order and everyone reads it and believes it.

The CEO said he didn't hear anything new — is that a failure?

Not necessarily. According to Noa it's actually excellent: it means you hit on what the CEO really meant. In the case she described, an hour after the CEO left, management thanked the VP Product for finally making them understand where he was heading with the "platform."

Why should the VP Product specifically be the one to tell the story?

For two reasons: product is much more than the output of the sprint — it's the company's central business instrument, and the product leader is responsible for it; and as a product leader, your job is to lead the company in the right direction, not just to run the product department.

Product Management VP Product Product Leader Strategy Storytelling CEO Product Leadership Tachles Episode