We scan new podcasts and send you the top 5 insights daily.
CJ Hess says models now reach roughly 90% of a solution once given the right context. He expects Tenex to value the work of sitting with a customer, capturing their brain dump, and feeding it to the model. Story points remain the anchor, but the unit may evolve.
Even roles far from the customer, like engineering, make countless micro-decisions. Without an intuitive understanding of customer pull—what they're trying to achieve and why they're blocked—these decisions will likely miss the mark, even when just following a requirements document.
As AI models become increasingly powerful, the primary bottleneck shifts from the agent's capabilities to the user's ability to understand and leverage them. Building a user's mental model of what's possible can unlock more value than incremental UX improvements.
Many engineers start by wanting to work on cutting-edge, abstract technical challenges (like LLM memory) but later pivot to finding greater satisfaction in applying that technology to solve concrete customer problems with measurable business impact, a common 'metamorphosis' in their careers.
As AI dramatically accelerates building, the bottleneck shifts from development to customer validation. This necessitates a cultural shift where the entire product team, not just PMs or researchers, interacts with customers weekly to keep pace.
Alex Lieberman says fears that engineers would sandbag story points or ship unchecked code never materialized. Tenex pairs output-paid engineers with AI strategists who are measured on customer retention and growth. Those incentives sit at odds, so strategists police quality and scope while engineers optimize for output.
When everyone on the team shares the same deep understanding of the customer's world, communication can be imperfect. The shared context fills in the gaps, preventing the "translation errors" that plague teams trying to operate from detailed specs alone.
AI tools now handle much of the data ingestion and synthesis that PMs traditionally managed. The modern PM’s value lies in using this AI-surfaced customer context to make high-leverage trade-off decisions and bridge the gap with go-to-market teams.
Alex Lieberman says Tenex revisits story-point criteria at least once a quarter because model improvements change the value of a unit. CJ Hess estimates engineer output roughly doubled from the Opus 4.5 moment to Opus 5.5. That 2x productivity shift feeds directly into how projects are estimated.
The proliferation of AI has dramatically reduced development time, shifting the primary constraint in product delivery from engineering capacity to the customer's ability to learn and integrate new features into their workflow. More output no longer guarantees more value.
With AI accelerating development, the limiting factor for shipping value is no longer engineering speed. The real challenge has shifted to the customer's capacity to adopt, implement, and train users on the constant stream of new features, making customer success and enablement paramount.