AI Isn't Breaking PM Teams. Overload is. Explained by Stanford PhD & CPO Jen Wang (Framework)
Framework CPO Jen Wang shares why they scrapped their 2026 product roadmap in February and what behavioral science tells us about leading product teams through AI change without burnout.
Jen Wang holds a PhD from Stanford in behavior sciences, judgment, and decision-making. She built her product career at ThredUp, and now serves as Chief Product Officer and go-to-market lead at Framework.
That combination — behavioral scientist plus operating CPO — gives her a rare lens into the most urgent question in product leadership right now: how do you lead and build when the ground is shifting faster than anyone can follow?
In this episode, we talk about:
The decision-making behind why Framework scrapped their roadmap
Why iteration, not technical proficiency, has been the most important skill to drive AI adoption in teams
There’s actually a scientific reason why everyone’s so overwhelmed, and it’s called the “Zone of Absorption”
1. Why Framework scrapped its 2026 roadmap in February
Most product teams treat the annual roadmap as sacred.
When new model capabilities landed in early 2026 (particularly around how long AI agents could run independently), Jen went back to her team with an uncomfortable message: the roadmap they’d spent months building was no longer the right one.
The replacement wasn’t a new roadmap.
It was a new question: Imagine that the technology will get there (because it will). What are the core customer needs that will still exist after the technology gets there?
For Framework, that meant connecting to the physical, human moments that no AI model can change: helping customers understand, repair, and personalize a piece of hardware they actually own.
The product takeaway: Your roadmap is a bet on the future, not a contract with it. When the future changes faster than your planning cycle, the discipline is knowing when to scrap and restart, not how to protect what you already built.
2. The zone of absorption: Your team isn't resistant to AI; they're at capacity (6:30)
One of the most useful frameworks Jen brought to the conversation comes from leadership theorist Ronald Heifetz: the idea that people have an optimal zone of stimulation for absorbing change. If you’re under it, people will stagnate. Push them over it, and they hit a wall.
Before you diagnose your team as resistant to AI, ask whether you’ve simply exceeded their zone of absorption. The teams adapting fastest aren’t the most technically sophisticated — they’re the ones with a pre-existing culture of iteration and psychological safety.
3. Why AI makes core product skills more important, not less (17:00)
Jen draws a sharp parallel to the AB testing era. When Optimizely and similar tools made experimentation cheap and fast, teams tested everything — and gradually mistook the tool for the discipline. Backlash followed, and “product intuition” became a counter-trend.
AI is the same dynamic. You can now generate a dozen prototypes in minutes. But the speed of prototyping without clarity of the problem just produces more noise (and potentially more… slop).
“This actually makes the core skills around product even more important — really understanding what your user needs are.”
The product takeaway: In a world of infinite prototypes, the scarce resource is judgment and taste. AI raises the floor for execution, but it does nothing for the ceiling of knowing what to build.
4. Where AI is actually defensible as a product moat — and where it isn’t (23:00)
Every product leader is asking the same question right now: if AI levels the playing field, where does our advantage actually come from?
Jen’s answer is precise:
“Any sort of data that you have internally, or any sort of insights that are implicit to your organization — that is potentially defensible.”
Anything you can document is not defensible. If it can be written down, it can be replicated. What’s defensible is implicit institutional knowledge: the insights, data, and experiences unique to your organization that you previously couldn’t productize because it was too expensive or the quality wasn’t good enough.
The product takeaway: Stop asking “how do we add AI to our product?” and start asking “what do we know uniquely, and what can we now build around it that wasn’t possible before?”
Links
Jen's LinkedIn: https://www.linkedin.com/in/wangjennifer/
Framework: https://frame.work/
Resources
ThredUp: https://www.thredup.com/
Anthropic: https://www.anthropic.com/
Leadership Without Easy Answers by Ronald A. Heifetz: https://www.hup.harvard.edu/books/9780674518582
The engineer's ring: https://www.nspe.org/career-growth/pe-magazine/july-2009/called-order
Chapters
00:00 Introduction
03:29: Why everyone thinks they’re behind on AI
01:32: From Stanford behavioral scientist to CPO: Jen Wang’s path to product
08:17: “The zone of absorption”: The science behind AI overwhelm
11:41: Why Framework scrapped their 2026 roadmap in February
14:28: Choosing your AI toolset: When to experiment vs. When to commit
16:15: Rethinking engineering resourcing to make room for “process debt”
17:49: The A/B testing parallel: Is AI history repeating itself?
20:35: AI prototyping: Productive or underbaked ideas?
23:52: Finding your product moat in the AI world
27:13: The learning possibilities that AI opens up
29:10: Should product leaders take a Hippocratic oath?
30:57: Conclusion
What does LogRocket do?
LogRocket’s Galileo AI watches user sessions for you and surfaces the technical and usability issues holding back your web and mobile apps. Understand where your users are struggling by trying it for free at LogRocket.com.