We scan new podcasts and send you the top 5 insights daily.
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.
Beyond saving developer hours, the true value of AI-driven efficiency lies in reducing rework. This frees up capacity for new revenue-generating projects. Frame the value not just as time saved, but as the business value of features you can now build instead (cost of delay).
In the AI era, traditional productivity proxies like lines of code are failing. A better measure is a team's ability to complete high-quality "at-bats": the full cycle from idea generation to building, feedback, and validation. This metric captures execution efficiency, team culture, and the ability to learn quickly.
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.
Superhuman's CEO advises against simply tracking AI costs, a practice he calls 'token maxing'. Instead, they evaluate the ROI of internal AI tools by measuring developer productivity metrics like feature delivery pace. This output-focused approach has doubled engineering velocity, justifying the AI spend.
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.
The rapid improvement of AI models creates a new internal benchmark for AI companies. If the underlying models are improving by 60%, internal operations must match or exceed that pace to stay competitive. This sets a new, demanding threshold for quality and speed.
As AI tools dramatically increase engineering leverage (2-3x), the traditional 5-engineer, 1-PM, 1-designer team structure breaks. The PM and designer become bottlenecks, struggling to manage what is effectively a 15-20 person engineering team's output, forcing a rethink of team ratios and roles.
CJ Hess says he left hourly consulting because his output rose while his pay fell. Alex Lieberman says Tenex's highest- and lowest-paid engineers differ by roughly 4x, not 10x. The hardest compensation problem is paying engineers for architecture and client meetings, not just coding. That nuance keeps the model from being pure piecework.
Don't rely on traditional project milestones to gauge AI progress. Instead, measure success through granular unit economics and operational metrics. Metrics like 'cost per release' or 'cycle time per feature' provide immediate feedback on whether your strategic hypothesis is valid, enabling rapid iteration.
The key to extreme productivity with AI coding agents isn't just speed. It's a fundamental workflow shift where engineers invest heavily upfront in creating detailed specifications, flipping the traditional 20% planning / 80% coding ratio to approximately 60% planning / 40% AI execution.