From Gut Feelings to Evidence-Guided Product Teams – With Itamar Gilad

Most companies say they want to be data-informed.
But when it’s time to ship, intuition, hierarchy, or politics still rule.

In this episode of Product Founder, Itamar Gilad, former PM at Google and author of Evidence-Guided, joins Amir Rezaei to talk about building real evidence-driven cultures, why vision alone isn’t enough, and how his GIST framework helps teams make smarter decisions with less waste.

Let’s break it down.

Why Product Teams Are Still Frustrated

“There’s an epidemic of sadness in product. People want to modernize how they work but the company is too top-down.”

Itamar hears this from PMs and leaders every day:

  • “We want to experiment, but we’re not empowered.”
  • “Our roadmap is just opinions with deadlines.”
  • “We ship a lot but nothing seems to matter.”

He wrote Evidence-Guided to show there’s a better way.

Evidence-Guided book

Lessons From Google+: When Vision Isn’t Enough

“Even the smartest people in tech fall for the fallacy: ‘This idea must succeed.'”

Itamar saw it firsthand during the Google+ launch:

  • It was a top-down bet with huge internal momentum
  • Users gave clear negative signals but the org kept pushing
  • Eventually, Google+ failed. Slowly. Publicly.

“We needed to define better goals, explore multiple paths, and let the best ideas emerge from evidence not assumptions.”

Itamar Gilad – Amir Rezaei

The Gmail Tabs Story: Evidence Works

Compare that to Gmail Tabs:

  • Initially rejected by colleagues: “Why would anyone need this?”
  • Itamar started small: paper mocks, fishfood tests, internal pilots
  • Gathered both quant and qual data, improved UX
  • Launched with confidence and success

“One of my few 100% successful launches. Because we validated every step.”

The GIST Framework: Goals, Ideas, Steps, Tasks

GIST is Itamar’s framework for evidence-guided product development.

1. Goals – Start with outcome-based goals

  • Not “build X feature”
  • But “improve conversion by 20%” or “reduce churn by 15%”

2. Ideas – Treat solutions as hypotheses

  • Prioritize with ICE (Impact, Confidence, Ease)
  • Use the Confidence Meter to assess evidence strength

3. Steps – Test before building

  • Interviews, paper mocks, fake doors, concierge tests, MVPs
  • Pick your level of investment based on risk

4. Tasks – Build only what’s validated

  • Align with agile teams
  • Reduce delivery waste

“Don’t write 150-page PRDs trying to predict the future. Learn your way to the answer.”

itamar Frameworks

Balancing Vision With Validation

“Vision is essential. But so is discovery.”

Even the iPhone started as a rejected idea inside Apple.
Jobs was convinced only after seeing working demos.

And Apple, despite its anti-user-research stance, still does massive internal testing.

Your takeaway?

  • Vision is a compass, not a roadmap
  • Even visionary leaders must test and iterate
  • Evidence isn’t anti-creativity, it’s how creativity thrives

The Risks of Founder Mode

“Right now, AI hype is pushing many teams into old habits. We’re back to founder mode.”

Too many PMs are being told:

  • Just ship something
  • Move fast, validate later
  • Trust the founder’s gut

Itamar warns:

  • This leads to more Google+ situations
  • It undermines product culture
  • It increases waste
Author and coach

Evidence-guided isn’t slower. It’s smarter.

3 Ways AI Is Changing Product Work

  1. AI in the product – You must learn how to ship AI responsibly
  2. AI for productivity – Careful: don’t let AI write specs for you
  3. AI as a catalyst for change – Use AI to rethink workflows, not just speed them up

“Discovery isn’t optional anymore. It’s how we differentiate.”

Start Building Evidence-Guided Habits

“Ask this one question: What’s the evidence behind this decision?”

One simple habit:

“It’s not about saying no. It’s about saying, ‘We need to know more.'”

What Itamar Changed His Mind About

“I used to think PMs needed to be visionaries. Or CEOs of the product.”

Now?

  • PMs are facilitators of discovery, not oracles
  • Engineers should co-own outcomes
  • Stop spoon-feeding teams specs

“When teams understand the goals, they make better decisions than any PRD can.”

Want More?

Check out:

Want more insights like this? Subscribe to the Product Founder podcast and get weekly interviews with product leaders, founders, and creators who are building legendary products.

Enjoyed this post? You might also like some of our other deep dives with top product thinkers:
1) What’s the biggest misconception in product discovery today? | Teresa Torres
2) Why do many product teams waste feedback? | Matei Culcer

If you found this valuable, share it with your team or repost to help other builders!