Why OKRs, agile, and their ilk fail with Jeff Gothelf
04/08/2026AI is reshaping product development faster than most organizations can even rethink how they work—and that gap sits at the heart of this conversation with product design guru Jeff Gothelf. Lou and Jeff explore why proven methods like Agile and OKRs so often become “process theater” instead of real change, and what it actually takes to shift organizations from output-driven cultures to outcome-driven ones.
Jeff explains that most transformations fail because incentives still reward shipping outputs, not creating real value. Meaningful change tends to emerge only in pockets led by leaders willing to experiment and treat ways of working as something to test and evolve.
They also explore how AI is shifting risk upstream—from engineering to vision, validation, and decision-making—making design and research more critical than ever. Along the way, they reflect on consulting as organizational therapy, the need to prove design’s value in the AI era, and why companies that relentlessly embrace new technology are best positioned to endure.
What You’ll Learn from this Episode:
- Why Agile, OKRs, and similar frameworks often fail to create real change
- The critical shift from measuring output to measuring outcomes
- The two traits shared by successful pockets of transformation in large companies
- How to run small, time-boxed experiments to change ways of working at scale
- Why AI makes design, research, and product thinking more valuable
- How to explain and prove the value of “thinking before the prompt” in AI-driven organizations
Q&A with Jeff Gothelf
This Q&A is drawn from this podcast episode.
Q: Why is this shift from outputs to outcomes so important?
A: Because outputs can look productive without actually solving the right problem. Outcomes force teams to ask whether their work is making a real difference.
Q: What does customer-centricity mean in practice?
A: It means starting with the customer’s problem, not the team’s solution. When teams stay close to customer needs, they make better decisions about what to build and what to measure.
Q: What is one of the biggest mistakes teams make?
A: Teams often fall in love with a solution too early. They rush to build before they fully understand the problem they are trying to solve.
Q: How do OKRs support this way of working?
A: OKRs are most useful when they help teams define success in terms of outcomes. They become much less effective when they turn into a list of tasks or deliverables.
Q: What is the biggest takeaway from the episode?
A: The takeaway is that strong product work depends on clarity, focus, and learning. Teams need to stay centered on customer value and measure whether their work is actually changing behavior or improving results.
About our guest
Jeff Gothelf is a product and strategy coach who helps organizations build better products, stronger teams and more adaptable cultures. With more than 20 years of experience, he brings deep expertise in product strategy, cross-functional collaboration, agile-friendly product design and experimentation. He has worked with companies like AOL, TheLadders and Neo Innovation to lead customer- centric transformations and deliver measurable business results.
Quick Reference Guide:
0:10 – Meet Jeff Gothelf; Lou and Jeff discuss bridging the gap between ritual and cultural change
7:44 – Good ideas without a clear understanding of why
9:42 – What it takes for organizations to successfully communicate and incentivize
15:21 – 5 reasons to use the Rosenverse
17:37 – Consultants validate insiders; AI shifts risk toward design clarity
24:20 – AI speeds output, but critical thinking, research, and testing prove designers’ value
27:50 – Jeff and Lou speculate on Amazon’s future
30:49 – Jeff’s gift for listeners
Resources and Links from Today’s Episode:
