Emrecan Dogan is a trained industrial engineer who has spent his career applying systems thinking to product management, and as Chief Product Officer at Glean, he has found the perfect laboratory for it. Glean is an AI assistant and platform for the world’s largest enterprises, and the same principles Emrecan uses to think about building AI products, where fixing one bottleneck immediately moves the constraint somewhere else, are the principles he uses to think about how product organizations should be designed and how PM careers should evolve. In this episode of Product Talk host Sonjoy Ganguly sits down with Emrecan to talk about why the correlation between how many features you ship and the value you create may actually be getting weaker in the AI era, why he believes the super IC PM is the defining career opportunity of this moment, and how Glean runs a product org where autonomy is taken, not given, and where the product itself tracks organizational intelligence in real time.
In this episode, we cover:
(2:25) Why AI makes judgment, systems thinking, and customer insight more important, not less
(2:25) The bottleneck framing: why fixing one part of the PM assembly line just moves the constraint somewhere else
(7:58) What stays the same about PM and what is changing, and Emrecan’s favorite interview question to test candidates on it
(11:08) The CPO’s real job in a founder-led company: unlocking and translating vision, not defining it
(15:47) The skills Emrecan hires for: customer obsession, AI fluency, systems thinking, judgment, and taste
(19:40) Why the correlation between feature shipping volume and actual value creation is weak, and what that means for how PMs should measure themselves
(21:39) How Glean balances enterprise predictability with frontier-speed shipping, and the autonomy model that holds it together
(25:21) Pod design, colocation decisions, and why Emrecan has 28 direct reports and almost no recurring one-on-ones
(29:50) How Glean uses its own product to track organizational progress, prepare for one-on-ones, and replace status reporting
Blog and detailed episode notes: [link]
