Product: Behind the Craft: LaunchPod

AI Agents Fail for 2 Reasons. Crowdsourcing Solved Both. | Julia Dalton, SVP Product (Capacity)

Jeff Wharton — Tue, 05 May 2026 15:43:45 GMT

Our guest today is Julia Dalton, the SVP of Product at Capacity, an AI-powered support automation platform. Before that, we spent years at OneSpace, formerly known as Crowdsource, a crowdsourcing company where thousands of freelancers executed microtasks for major retailers. Routing rules, task chains, instruction validation, and more.

Today, that’s known as multi-agent orchestration. And Julia was doing it before it was cool.

In today’s episode, Julia shares:

How a PRP (product request prioritization) system she designed herself in one weekend transformed Capacity’s CS feedback by replacing the chaotic “firehose” of requests with a ranked, data-backed list
What running a human API layer taught her about prompt design, long before LLMs existed
And the truth most teams skip — that AI agents are only as good as their instructions. AI doesn’t fix bad data; it amplifies it, and teams need to audit their data before writing a single prompt

1. The two reasons AI agents fail (22:45)

At OneSpace, Julia’s team managed thousands of freelancers doing microtasks for large retailers at scale. The lessons learned were hard and expensive: if you send out 500 product descriptions with unclear instructions, you’ve paid for 500 things you can’t use.

“You could have the best instructions on the planet, the best prompt, but if your data is wrong, you’re going to get really, really terrible results.”

The two culprits? Bad instructions and bad data.

The product takeaway: You’re not the one doing the task — you’re architecting it. That distinction changes everything about how you design agent workflows.

2. Validate your prompts before scaling (11:39)

One of the most underrated moves at OneSpace: before deploying a task to thousands of workers, they’d run a separate mini-workflow with workers whose only job was to evaluate the instructions — not execute them.

Why?

Julia says:

“What seems clear to you and what you’ve communicated is oftentimes very unclear or not as clear as you thought to the audience or to the recipients.”

Her fix? Use a separate agent (or person) whose only job is to evaluate the instructions — not execute them.

Julia does the same thing now with agents: agent-to-agent evaluation runs, logging and scoring conversations, and humans doing test passes. Recursive validation before you ever go live.

The product takeaway: What seems clear to you is often unclear to your recipient, so make sure to build a feedback mechanism for your instructions before you scale them.

3. The PRP: A weekend project that untangled the feature request firehose (22:30)

Julia’s product team was drowning in requests from CS and revenue teams. Each submitter was convinced their ask was the #1 priority.

So, she built a structured intake system herself over a single weekend.

The result?

Structured inputs, auto-classification, ARR and retention impact weighting, and a triage layer within Customer Success before anything ever reached Product. The same signals that prioritize incoming work also let the team communicate the ROI of what they shipped.

“AI only amplifies the data — so if your data is wrong, it’s going to amplify its wrongness in a major way.”

The product takeaway: Data doesn’t just help you prioritize what to build — it helps you prove the impact of what you’ve already built.

Chapters

00:00 Introduction
02:10 Julia's career path to Capacity
04:18 Microtasking at scale
05:59 Jula explains her workflow chains
08:36 Designing routing rules
13:15 Two failure modes
13:56 Simulating and scoring agents
17:22 Recursive prompting in practice
20:27 Data and knowledge orchestration
23:55 PRP Feedback triage system
27:02 Impact and ROI from signals
30:15 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.

AI Isn't Breaking PM Teams. Overload is. Explained by Stanford PhD & CPO Jen Wang (Framework)

Jeff Wharton — Wed, 15 Apr 2026 13:11:11 GMT

Listen on:
YouTube | Spotify | Apple

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?”

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?

The Analytics Gap Most eCom Teams Don’t Know They Have | Raul Parquet, Dir. eCom (Princess Cruises)

Jeff Wharton — Tue, 07 Apr 2026 13:46:59 GMT

Listen on:
YouTube | Spotify | Apple

When you think about e-commerce, booking a cruise is about as complex as it gets. Our guest today has spent 20 years building analytics setups across the top companies in the industry, with the goal of making these transactions dead simple to understand.

Raul Parquet is the Director of e-commerce at Princess Cruises, where he’s helping to lead them into a more digital future where visa requirements, multi-destination itineraries, and endless customization options are something customers can actually complete online.

In this episode, Raul shares:

The unglamorous but vital elements of a complete e-commerce analytics stack, and the table-stakes things teams often skip
Why an Analytics team embedded inside product is a requirement, and the deployment discipline that comes with it
And how Princess Cruises is using AI behind the scenes to help their team work smarter — and why, when it comes to customers, simplicity will always matter more than technology

1. Why embedding analytics inside your product team changes everything (6:00)

When analytics lives outside the e-commerce team, data loses consistency and collaboration breaks down across UX, product, and merchandising.

Raul’s fix?

Embed analytics directly in the digital team and put them in every planning meeting — from strategy to development.

“When those analytics team members are within e-commerce and within marketing, everything flows together.”

The product takeaway: Structure before tools. Get the team right first, and the data gets better automatically.

2. The #1 deployment mistake product teams make (8:00)

Most teams instrument analytics after a feature ships, but Raul says that’s already too late.

Every migration, every feature, every release needs tagging built in before it reaches customers. Combined with a throttled rollout and A/B testing, this lets you catch problems early (when you can still iterate) rather than after a full launch.

“We don’t normally just launch anything. We test everything.”

The takeaway: Analytics isn’t a QA step. It’s part of the build.

3. How Princess Cruises is using AI right now (and where it’s still unproven) (17:23)

There are two sides to AI for any product team:

What you use internally to move faster, and
What you deliver to customers

Internally, Princess runs on Microsoft Copilot — automating reporting, surfacing insights, and building executive presentations. But every AI output still gets a human review before it drives a decision.

On the customer side, service automation is the low-hanging fruit. Questions like visa requirements can be answered on-site by an AI agent before they ever reach the call center.

But conversion inside the booking funnel? That’s still an unsolved problem.

The takeaway: Deploy AI where it’s proven, and be honest about where it isn’t.

4. The analytics gaps hiding in plain sight (18:00)

Raul’s most common diagnosis when he looks at an e-commerce analytics setup: teams that track A to B and C to D, but accidentally skip B to C — and unknowingly lose visibility into a large part of their funnel!

His advice for every product leader?

Understand analytics fundamentals yourself, and bring analytics SMEs into every new project at the start — before UX is finalized, and before development begins.

The takeaway: Completeness of coverage matters as much as depth of reporting.

Chapters

00:00 Simplicity Wins
01:44 Raul’s product background
03:50: Why cruises are one of the hardest ecommerce problems to solve
06:32 Embedding analytics teams into product
08:00 The #1 deployment mistake product teams make
13:29 Table Sstakes: What every ecommerce team should be monitoring
17:23 How Princess Cruises uses AI internally
18:00 The analytics gaps most teams don't know they have
19:47 The three-tool analytics stack for ecommerce
21:35 Simplifying complex bookings: The Tesla analogy
28:01 Where AI actually fits in the customer journey
32:35 Conclusion

What does LogRocket do?

How to Avoid AI FOMO like Patagonia | Angela Clark, VP Digital

Jeff Wharton — Tue, 24 Mar 2026 13:43:23 GMT

Listen on:
YouTube | Spotify | Apple

In this episode, we’re joined by Angela Clark, VP of Digital at Patagonia. Angela’s career spans 20+ years in retail and direct-to-consumer, from Pottery Barn and Levi Strauss to True Religion, and now one of the most mission-driven brands on the planet.

In this episode, Angela shares:

How her team is designing a customer journey that caters to the buyer on a 1:1 level, including Product Detail Pages that can speak effortlessly to either extreme of their customer base
Her playbook for managing AI-related “shiny object syndrome” and keeping your roadmap focused on the customer
And why Patagonia flipped the definition of “customer lifetime value” to align with their conservation-driven mission — even happily downselling you to a refurbished item instead of a newer, more expensive version

1. The PDP of one (3:10)

Patagonia’s Nano Puff jacket is bought by urban commuters and alpine climbers alike. And for years, both landed on the same static page.

Angela’s team is fixing that with layered “surface” pages that respond to what they know about you, from past purchases, browsing behavior, and how many times you’ve visited. The goal isn’t more tabs or filters; it’s a page that reorganizes itself around you.

“If I know that you’ve been to my site two times already and maybe the first time you actually read an article or you watched a video about something and the next time you did that, maybe then I can serve up storytelling content that might intrigue you more.”

Product takeaway: Don’t treat personalization as a feature toggle. Think in terms of surfaces: modular content blocks that can reorder, expand, or collapse based on user signals.

2. Circularity on the same page (10:30)

Patagonia now surfaces new and used versions of the same product side by side — a move most e-commerce teams would never risk for fear of negatively impacting full-price sales.

Angela’s team made the call anyway, and they’re learning how customers actually behave when both options are visible.

“We’re fearless about being able to put those two side by side. And it’s been really interesting to learn how people are interacting with those two things, next to each other. We don’t want people to buy something that they don’t need. Or if there’s something that’s already made, that’s better for us, and it’s better for the environment than buying something completely brand new.”

Product takeaway: Brand values aren’t a constraint on product decisions — they’re a strategic differentiator. If your product team is making tradeoffs that quietly contradict your company’s stated mission, that’s a product problem. Align your roadmap to your “why,” and you’ll often find that customers reward you for it.

3. Cutting through the AI noise (25:00)

Angela has one of the more grounded perspectives on AI adoption you’ll hear from a senior digital leader. She’s skeptical of the headline-grabbing claims and willing to say so out loud.

At the same time, she’s not dismissing AI entirely. Her view is nuanced: the winners will be the people who figure out how to use it to work better — not the ones who move fastest.

“I believe the statement that the people who are gonna win in the long run are people who figure out how to use AI effectively to help them be more efficient in their work. But in a lot of spaces, it’s going to take time.”

Product takeaway: The pressure from boards and leadership to “do AI” is real — but it’s often unfocused. Your job is to translate that pressure into a specific, scoped problem worth solving. As Angela puts it, most organizations are still at the “figure it out stage.” Build trust by being honest about where you are, educating upward, and showing deliberate progress.

Chapters

00:00 Introduction
01:43 Angela's career journey
03:30: The PDP problem: Serving elite athletes & urban buyers on the same page
07:00: Building personalization through behavioral signals
09:30: Personalization: it's not a tech problem, it's a customer journey problem
00:15:30 How Angela built the foundation of digital at Patagonia
20:30: How to navigate slow-moving organizations
23:00: Redefining customer lifetime value around Patagonia's mission
26:30: AI FOMO — and why you're not actually falling behind
31:30: Conclusion

What does LogRocket do?

The Anti-Headcount Billion-Dollar eCom Playbook | David Cost, CDO (Rainbow Shops)

Jeff Wharton — Tue, 17 Mar 2026 13:11:54 GMT

Listen on:
YouTube | Spotify | Apple

How many engineers does it take to run the ecommerce site for a retail company that does over a billion dollars in revenue per year?

Well, if you’re Rainbow Shops, the answer is just 2.

Most ecommerce teams assume scale requires more engineers, more tools, more complexity. Chief Digital Officer David Cost has built something many people in ecommerce would say isn’t possible — a lean, fast-moving digital operation that runs on vendor partnerships instead of a massive internal team. Two engineers, hundreds of programmers’ worth of output, and none of the overhead that comes with scaling the traditional way.

In this episode, David shares:

A detailed, under-the-hood look at the specific vendors they use to stay so lean
His playbook for using strategic partnerships with vendors as an external dev team
How being a testbed for new tech gives them a competitive edge
And why their choice of ecommerce platform was vital in enabling Rainbow’s digital strategy

1. The anti-headcount playbook: running a billion-dollar e-commerce operation with two engineers (4:13)

Most e-commerce companies respond to competition the same way: hire more engineers, build more in-house, scale headcount. David’s team is doing the opposite:

“We use our two full-time internal engineers and then we partner with a lot of technology vendors who, in some ways, are almost extensions of our staff.”

The lesson for any product leader operating under resource constraints: headcount isn’t the only way to scale capability.

The right partnerships — not vendor relationships, but genuine partnerships where you influence the roadmap — can give you access to incredible infrastructure without the overhead of building or maintaining it yourself. This applies whether you’re running e-commerce, a SaaS platform, or an enterprise product team with a constrained budget.

2. How platform choice can be a strategic multiplier (4:45)

Rainbow spent over a decade on Demandware (later Salesforce Commerce Cloud) before making the decision to replatform to Shopify in 2021. That decision wasn’t just about features — it was about ecosystem leverage.

If you’re going to build partnerships with vendors who extend your stack, you need to be on the platform they’re building for first. In this case, that platform is Shopify.

“If you’re gonna develop a new piece of tech that’s gonna work in the e-com world, you’re gonna build it for Shopify first.”

Being a large retailer on Shopify — where large retailers are relatively rare — gave Rainbow something valuable: the ability to be a launch partner for new technology in exchange for influence over how that technology gets built.

This is a model any product team can adapt. You don’t need to be the biggest player in the room; you need to be the right partner for the vendors who are solving the hardest problems in your space.

3. A native mobile app — with zero mobile engineers (22:09)

Rainbow has a native iOS and Android app. Yet they have no mobile engineers.

Using a platform called Fuego, Rainbow essentially mirrors their Shopify setup into a native app experience for both platforms, complete with push notifications, with minimal ongoing lift.

“We pick up native apps along with push notifications, and in a world where we’ve already hit peak email and probably hit peak SMS, push is the next frontier.”

App users at Rainbow convert at higher rates, repeat purchase more frequently, and carry larger average basket sizes. About 20% of Rainbow’s customers prefer accessing the brand via app rather than browser. David’s view is that you can’t move people between those camps. You have to serve both.

The takeaway: There’s a class of capability that looks expensive and technically complex from the outside but has been commoditized by the right platform partner. Native apps used to be one of those expensive, high-maintenance investments. For teams willing to find the right partner, it no longer has to be.

4. Checkout is not where you innovate (27:21)

One of David’s strongest convictions: checkout is the last place a product team should spend engineering resources trying to differentiate.

At Rainbow, Shop Pay now accounts for nearly half of all transactions — a number that dwarfs Apple Pay (sub-10%) and has eroded PayPal from 20% to 10%.

The broader PM lesson here is about knowing where not to compete.

For every problem your product faces, there’s a version of that problem that someone else has already solved better than you ever will with your current resources.

The key is in identifying which those are — and getting out of the way. Shopify’s checkout is nearly impossible to replicate, and the teams that have tried to build proprietary checkout flows have paid for it in engineering debt and conversion rate underperformance.

Chapters

00:00 Introduction
02:14 David’s product journey
03:18 How Rainbow runs with only two engineers
04:13 Rainbow's decision to migrate from Salesforce Commerce Cloud to Shopify
10:16 How Rainbow uses AI to support a lean team
13:31 Rainbow's partnership with Lica for AI-generated product images
19:34 The future of personalization in ecommerce
25:14 Shop Pay and Rainbow's checkout features
28:32 Conclusion

What does LogRocket do?

The World’s Safest Driver Isn’t Human. Can Waymo Stop Traffic Deaths? | Chinmay Jain, Dir. Product

Jeff Wharton — Tue, 10 Mar 2026 13:34:58 GMT

Listen on:
YouTube | Spotify | Apple

40,000 people a year die from traffic accidents in the US. Our guest today is Chinmay Jain, Director of Product Management on Waymo's Driving Behavior team, who is working to make that number 90% smaller.

In this episode, Chinmay shares:

How he thought through leaving YouTube at its peak to join a moonshot company that could have civilization-level impact
Waymo’s actual AI eval process, using massive simulations based on millions of real-world driving miles to maximize edge cases, ultimately turning trust into their real product
And the misleading, but common, metrics Chinmay and his team learned to spot that could have seriously derailed Waymo’s progress

1. Leaving a sure thing for a startup with the power to change the world (3:06)

When Chinmay joined Waymo in 2018, the outcome was genuinely uncertain. This wasn’t a calculated bet on an obvious winner — it was a leap into the unknown.

“I always have tried to go back and work on something going from zero to one and be more present with that great opportunity to take it from zero to one.”

For Chinmay, Waymo’s mission tipped the scales: 40,000 people die in US traffic accidents every year. Waymo’s goal is to reduce that by 90%.

The lesson for PMs in any vertical: don’t just optimize for stability. The products that change industries, whether in healthcare, fintech, logistics, or consumer tech, are usually built by people who were willing to bet on something before it was obvious.

2. What to do when AI evals are high-stakes — or even life-or-death (5:50)

When Chinmay was at YouTube, a bad A/B test meant a feature didn’t ship. At Waymo, a bad eval could mean someone gets hurt. That difference fundamentally changes how you think about testing.

This is increasingly relevant across all of product management, not just autonomous vehicles. As AI becomes embedded in medical diagnostics, financial decision-making, and construction infrastructure, the stakes of evaluation are rising everywhere. The question isn’t just “did the metric go up?” — it’s “do we actually understand why, and are we measuring the right thing?”

For this reason, Chinmay’s team runs massive simulations — built on millions of real-world driving miles — to stress test edge cases before anything touches the road.

For PMs building on top of ML — whether in consumer apps, B2B SaaS, or physical AI — this is the core discipline. You can’t rely on traditional A/B testing intuitions when your system is probabilistic. You need to define what “good” looks like before you can measure it.

3. The misleading metrics that could have derailed Waymo (14:52)

One of the most underappreciated PM skills is knowing which metrics to stop trusting. Vanity metrics are a well-known problem in consumer apps — DAUs that don’t reflect real engagement, NPS scores that mask churn risk. But in complex, high-stakes systems, the danger is more subtle.

The broader PM lesson: metric selection isn’t a setup task you do once at launch. It requires ongoing interrogation, especially as your product scales and user behavior evolves. Whether you’re running a marketplace, a fintech platform, or an enterprise SaaS tool, the metrics that got you to product-market fit may not be the ones that keep you successful as you scale.

4. What are the hardest things to teach a self-driving car? (24:41)

Two answers, both surprising:

Unprotected left turns: Massive negotiation happening in real time between cars, pedestrians, and intent. There's no one rule that resolves it cleanly. It's negotiation in real time
Pulling over: Looks simple, but requires the kind of human intuition that drivers must learn over years. Experienced Uber drivers learn pickup nuance over years (think the person hovering at the corner, the building entrance that's technically on the side street, etc.) It's tacit knowledge, built from thousands of micro-observations humans don't even consciously register

“It’s the same reason why can’t a robot can’t just fold a shirt — there are some aspects which are very easy for humans that machine learning systems have to really learn well.”

What seems obvious to your team — "just click here to get started" — may require years of learned context for your ML systems. The gap between your mental model and theirs is almost always larger than you think, which is why taking the time to comprehensively train your models is crucial.

Chapters

00:00 Introduction
02:01 Chinmay’s career journey
03:06 Chinmay’s decision to leave YouTube for Waymo
05:50 How does Waymo test its AI in the physical world?
07:59 Waymo’s layered evaluation system
12:07 Simulations and ML gains at Waymo
19:23 Waymo’s metrics for safety
21:59 Can Waymo make roads 90% safer?
24:36 What driving choices make training AI drivers the hardest?
27:10 Conclusion

What does LogRocket do?

The Cortisol UI: How We Fix FinServ’s Empathy Problem | Melissa Douros, CPO (Green Dot)

Jeff Wharton — Tue, 03 Mar 2026 14:15:06 GMT

Listen on:
YouTube | Spotify | Apple

Most financial products are optimized for transactions, not human emotion. For many people, this transforms an already fraught topic into pure anxiety.

Our guest today is building banking for what she calls the Cortisol UI.

In this episode, Melissa Douros, CPO at Green Dot, shares:

How finserv companies can design for the “Cortisol UI“ by building trust and experiences that reduce anxiety before the transaction
An experiment she ran for Discover’s 5% cashback program where test users collapsed under decision paralysis — proving that more choice can actually increase financial stress
How she flipped Great Wolf Lodge’s booking model from 70% call center to 90% digital while enhancing the human experience
And how Green Dot is navigating AI and agentic commerce without breaking the one thing banks can’t afford to lose: trust

1. Shame is a terrible retention mechanism (3:41)

Melissa’s career began in collections, where she learned something foundational about financial behavior.

“People generally don’t even have $300 saved. They’re one health scare away from complete financial ruin sometimes. So being in collections really helped me understand and try to help people prepare for these financial moments.”

Design financial products (or any high-stakes product) assuming users are anxious, underprepared, and trying their best. Empathy isn’t a brand layer — it’s core product strategy.

2. Design for de-escalation, not just transactions (9:49)

Melissa describes how many digital experiences accidentally increase stress — especially in finance.

“Every moment that we have with a customer is an opportunity to either delight and connect with the customer or to erode from a trust perspective.”

Too often, companies optimize for transactions (balance checks, payments, transfers) but neglect the emotional layer of trust. She calls this designing against “Cortisol UI,” interfaces that spike stress instead of reducing it.

3. AI should lower stress — not increase it (11:03)

Melissa is bullish on AI — but only when deployed responsibly.

“The research is still showing that in finance, people trust AI to do simple tasks for them, but not necessarily complex.”

At Green Dot, AI transcribes calls, analyzes sentiment, and reduces handling time — but humans remain accountable.

The goal isn’t flashy AI. It’s faster resolution, fewer mistakes, and proactive issue detection, ideally before customers even notice.

The takeaway:
The best AI experiences feel invisible. Lower friction. Faster resolution. Fewer surprises. If customers are noticing your AI too much, you may be doing it wrong.

4. Building to prevent decision paralysis (21:56)

In a previous role at Discover, Melissa helped explore giving customers the ability to choose their own 5% rewards categories.

Customers said they wanted it. But in practice?

“They were completely paralyzed by what to pick. Customers asked, ‘What if I don't choose the right category… What if my plumbing breaks, and I should have chosen home improvement after all?’”

The program was eventually scrapped.

The takeaway:
When money is involved, hypothetical feedback isn’t enough. User research needs to include real consequences, and sometimes, reducing choice increases confidence.

Chapters

00:00 Introduction
01:00 Melissa's finserv background and how she landed in product
05:10 How Green Dot builds trust as a financial services product
07:29 Building for the "Cortisol UI" to lessen user stress, especially in finance
9:55 Quietly fixing customer issues while not inundating them with feature releases
14:35 Green Dot moving compliance from the backend to a key part of the product team
16:20 Launching AI features in a high-risk industry
18:36 Decision paralysis and Discover's failed attempt at a 5% cashback reward program
24:57 How Melissa digitized Great Wolf Lodge's customer experience
30:51 Conclusion

What does LogRocket do?

The $500M Lesson from Amazon’s Homepage Redesign | Rahul Chaudhari (ex-Amazon, Kohl’s)

Jeff Wharton — Tue, 24 Feb 2026 14:34:47 GMT

Listen on:
YouTube | Spotify | Apple

How do you redesign the most visited e-commerce webpage in the world? Rahul Chaudhari helped reshape the Amazon homepage during his years as a product leader there, before becoming VP of Product and Technology at Kohl’s.

In this episode, Rahul shares:

Amazon’s “customer backwards” approach - and how he used it to unlock half a billion dollars of value on the Amazon homepage
The secret to product adoption: leverage existing customer habits to unlock new opportunities
And how Amazon and Google raised the bar for digital experiences so high that now every other product pays the price

1. Why customers expect Amazon-level experiences everywhere (05:10)

Rahul shared a simple but powerful insight:

“Why should I, as a consumer have different expectations from my digital banking or my insurance company or my fitness app, as compared to when I shop e-commerce.”

The bar doesn’t reset. If you force customers to relearn workflows and build different habits than they’re used to, that adds a tremendous amount of friction to their digital experience.

Takeaway:
Your competitors aren’t just in your category. They’re every great digital experience your customer has had this week.

2. Why “customer backwards” beats “solution forward” (8:40)

Rahul explains the difference:

“Customer backwards really is you start from the customer and then work backwards of that for anything that you wanna solve for. Instead of saying, ‘Hey, I have an idea and I wanna do this’, which is solution forward.”

When teams start with a solution, they get attached to it. When they start with the customer, they stay solution-agnostic.

The Amazon homepage shift required rethinking eligibility, exposure limits, shared measurement, and governance — all focused on customer signals, not internal priorities.

Takeaway:
If you’re optimizing surfaces around what your company wants users to do (instead of what users actually signal they want), you’re already creating friction.

3. How Amazon reclaimed 41% wasted impressions (12:20)

Rahul’s team at Amazon discovered that overexposure was killing impact.

“We reclaimed some 41% impressions that were wasted because of over exposure that led to, you know, hundreds of millions of dollars of incremental business impact for all of these programs.”

Different Amazon programs were optimizing for their own metrics — Prime subscriptions, Alexa units, Grocery adoption — but without shared guardrails.

The team introduced:

Common measurement across perception, habit, and economic impact
Exposure caps to prevent “hero blindness”
Governance to prevent any single team from monopolizing the placement

They also focused on adoption — not just first clicks.

“What we care about is not the one first action. First Action is great. But what we care about is, does that get you enough into being engaged with that program so that you’re adopted.”

Takeaway:
Define adoption precisely. If you only measure the first click, you’ll optimize for false positives and waste resources chasing short-term wins.

4. AI doesn’t change the problem — it changes the business model (19:10)

Rahul’s biggest AI insight wasn’t about tools — it was about business design.

Instead of asking “What AI tool should we buy?”, Rahul suggests asking how your business model changes in an AI world.

He also warns that AI needs structure before it needs models. If your data is scattered across systems without shared schemas, ontologies, and relationships, you don’t have an AI strategy — you have translation debt.

And as agentic shopping rises? The homepage may no longer be your homepage.

Takeaway:
AI isn’t about bolting on features. It’s about rethinking value creation and data foundations.

Links

Rahul’s LinkedIn

Chapters

00:00 Introduction
01:38 Rahul’s journey from marketing to product
07:41 Why you shouldn't aim to re-educate users after they've already developed shopping habits
09:13 Redesigning the Amazon homepage: The ‘customer backwards’ approach
21:00 How AI will change retail business models
24:46 Agentic commerce & what happens when ChatGPT becomes the homepage?
29:07 AI needs containers, not just models
37:02 Conclusion

What does LogRocket do?

Smarter AI Models Won't Fix Your Deployment | Maryam Ashoori, VP PM/Eng (IBM, Watsonx)

Jeff Wharton — Tue, 17 Feb 2026 14:54:45 GMT

Listen on:
YouTube | Spotify | Apple

In this episode, we’re joined by Maryam Ashoori, VP of Product and Engineering at IBM’s Watsonx platform.

With a background that includes 2 master's degrees in AI, a PhD in Systems Design Engineering, and named on over 30 patents at IBM, she’s been on the bleeding edge for over a decade. Currently leading the charge on Agentic AI and AI Governance at IBM, Maryam is a bridge between the theoretical frontier of AI and the messy reality of enterprise deployment.

In this episode, Maryam shares:

Why AI has been stuck in pilot purgatory for longer than expected, and what you need to do today for a successful enterprise deployment
Shenanigans on the “biggest, best model” crowd, and why often a smaller, more focused tool is the right choice
How to build an agnostic architecture that can handle the realities of an AI world where models advance faster than anybody can keep up

1. From AI as experimental “toys” to enterprise products (3:30)

When ChatGPT went mainstream, companies rushed to fulfill their boards’ demands for an “AI plan” — whatever that meant. But few companies started with the right question.

“They basically picked an application, a solution looking for a problem that it solves versus it has to be the way around: how can I benefit from this technology?”

Why this matters: AI excitement doesn’t equal value. The shift from experimentation to production starts with defining the business problem, not retrofitting AI onto your roadmap.

2. Who’s accountable when an agent goes rogue? (7:10)

Where enterprises previously had a FOMO (fear of missing out) if they didn’t have an AI strategy, now they have a fear of messing up. They’re worried about being on the front page of the news for AI mishaps.

Maryam shares a question her client advisory board raised. It’s the one product leaders should be obsessing over:

“Something goes wrong in front of the users. Who is accountable here?”

Agents introduce autonomy, which introduces ambiguity. And ambiguity introduces risk.

Before shipping AI agents, leaders need clarity around accountability, guardrails, and governance workflows.

3. Latency will kill your AI product faster than cost (20:40)

It’s tempting to obsess over model cost. But Maryam reframes the conversation such that cost is a signal, and latency is the real user killer.

She shared an example of an insurance chatbot that added LLMs behind the scenes. The new response time?

40 seconds.

It was practically unusable.

Why this matters: No customer wants to wait 40 seconds for a chatbot response. Optimizing for compute isn’t just about margin; it’s about user experience, energy consumption, and architectural design.

4. The role of the product manager is changing (16:20)

Maryam describes how the traditional PM → PRD → engineer workflow is already blurring:

“The product manager with AI assisted coding, they code, they build. They have an army of agents that is at the prototype level now, but is gonna keep getting better every day.”

With that shift comes a new mandate:

“We need to do more thinking than doing because doing, we can pair it up with AI.”

Takeaway: The next generation of PMs won’t just write PRDs. They’ll design for agents, think in abstractions, and orchestrate systems.

Final thoughts

If you’re a product leader building with AI today, the question isn’t:

“Which model is best?”

It’s:

“Is our system designed to evolve?”

Resources

Chapters

00:00 Introduction
02:27 Maryam's product and AI journey
04:08 AI pilots, ROI, and the rise of agents
08:01 Production fears, security, and accountability
10:49 Agent reliability
16:35 AI PMs & observability: Measuring outcomes in non-deterministic agent workflows
20:12 Why compute optimization matters
24:49 IBM's model-agnostic architecture
29:14 Conclusion

What does LogRocket do?

Using AI to Preserve 140 Years of History at the LA Times | Deepika Manglani, VP Product (LA Times)

Jeff Wharton — Wed, 04 Feb 2026 16:19:01 GMT

Listen on:
YouTube | Spotify | Apple

In this episode, we’re joined by Deepika Manglani, VP of Product and Program Management at the LA Times. Deepika’s career in media spans over 15 years, culminating in her current role, where she’s bringing the 140-year-old institution into the future.

In this episode, Deepika shares:

How her team is using AI to preserve a unique trove of historical data, over 12 million pages of news archives from as far back as the 1800s
What this digital archive and maturation of AI enables for future storytelling, media innovation, and news personalization
Why combining product and program management was critical to navigating massive transformation at the LA Times through a period of heavy M&A activity

1. Rebuilding a 140-year-old institution from scratch (3:10)

When the LA Times was sold in 2018, the newsroom stayed, but the technology backbone didn’t.

That meant rebuilding everything: networks, HR systems, billing, platforms, and products, while publishing daily.

“Imagine what that means. No network, no infrastructure, no products, no platforms, no people. And yet the newsroom has to run 24/7 for a 140-year-old company.”

To make it work, she merged product and program management into one organization — aligning vision, execution, and delivery under a single mission.

The takeaway: transformation isn’t about shiny tools. It’s about building operational foundations that let journalism survive and scale.

2. Why generative AI wasn’t good enough for history (10:45)

The LA Times has more than 12 million archived articles, many trapped in low-quality scans and microfiche.

Early estimates to re-digitize them ran the team millions of dollars before a multimodal AI solution arrived.

Even then, however, the team needed an AI tool that wasn’t “too smart” for this use case. Because when they “thought,” the tools hallucinated or altered facts:

“The problem is when these AI models start understanding the context, that’s when they start thinking. And if you don’t want them to think, you gotta eliminate that part.”

So her team deliberately chose a non-generative, OCR-style model that just copied text.

The takeaway: Picking the right model doesn’t mean choosing the shiniest new tool on the market, but the one that will best fit your use case.

3. Turning archives into living storytelling tools (15:30)

Today, the LA Times has already digitized 300,000+ articles, with a goal of 500,000 in the near term.

Once complete, these archives won’t just sit in storage — they’ll power modern journalism.

Deepika explains how historical context can reshape coverage of major events:

“If we can stitch that together… what happened back in [the 1994 World Cup] versus right now in 2026, that would make the story more interesting.”

Instead of researchers spending days digging through records, journalists will be able to search decades of history instantly.

With semantic search, archives become an active reporting tool, not just a museum.

4. The future of personalized news (25:10)

Beyond preservation, Deepika is thinking about how news consumption itself should evolve.

She wants media to learn from platforms like Spotify and TikTok without sacrificing credibility.

“I would love to have an app that reads news to me based on my history of reading.”

The infrastructure being built today — archives, metadata, personalization systems — makes this future possible.

Chapters

00:00 Introduction
01:49 Deepika's career journey in media and product leadership
03:03 Building from scratch at LA Times
07:19 Digitizing historical archives
10:34 Challenges and innovations in AI and OCR
22:29 Future prospects and personalization in news
26:52 Conclusion

What does LogRocket do?

Designing for Attention: How CrossFit Builds Product for Community-Led Growth | Ben McAllister, CPTO

Jeff Wharton — Tue, 27 Jan 2026 14:56:02 GMT

Listen on:
YouTube | Spotify | Apple

TL;DR

In this episode, we’re joined by Ben McAllister, the Chief Product and Technology Officer at CrossFit, and one of the most thoughtful product leaders I’ve had the pleasure of speaking with.

Ben’s path is anything but linear: with a degree in physics, a short stint in consulting, and time spent as a creative director at a design agency before moving into senior product roles at Under Armour. Now he’s shaping one of the world’s most iconic fitness ecosystems.

In this episode, Ben shares:

Why attention is the ultimate currency in product design, and how to design for the “spotlight” versus the periphery
The “Infovore” Advantage: Why the best product leaders borrow ideas from outside the tech world
How to build a cohesive product strategy for a complex, decentralized network like CrossFit’s global community of affiliates and athletes

1. Why usability testing often misses real-world behavior (8:45)

Ben explains why passing usability tests doesn’t mean a product will succeed once users are on their own – especially in consumer products.

“The problem with things like that often is like, yeah, but like in the real world, no one’s going to prompt them, right?”

What matters isn’t whether users can complete a task – it’s whether they’ll notice it, feel motivated to engage, and understand why it matters.

2. Product design is an exercise in managing attention (10:30)

Ben frames product design as a balance between two kinds of attention:

What users consciously focus on
What subconsciously pulls them in

The key insight: Users don’t fully control where their attention goes, and product teams need to design with that reality in mind.

“You have two ways of attending the world. You have a broad scope of attention, and then you have the spotlight that’s a little bit more consciously directed.”

3. Product teams can’t outsource attention to marketing (12:15)

One of Ben’s strongest takes is that product leaders can’t treat attention as someone else’s problem:

“One of my pet peeves is a PM kind of like complaining. ‘We didn’t get enough marketing.’ You knew that when you built this feature.”

Instead, Ben argues that product leaders must take responsibility for how awareness and motivation are created.

“If attention is what matters, you have to become aware that something exists. You can’t just assume that somebody’s going to walk in the door and use this product.”

4. The CrossFit Open reveals what users actually value (20:40)

One of the most surprising insights Ben shares in this episode comes from analyzing traffic during the CrossFit Open, an annual competition designed to test participants’ fitness globally while fostering community with local gym affiliates.

“Most of the traffic is people going to the leaderboards and predominantly looking at their own scores from this year, from last year, from ten years ago.”

So what do you do with an insight like that?

Should CrossFit double down on performance and competition – or lean further into community and participation?

Regardless of the answer, the product team’s job is to ask these questions and truly understand their users. They can’t build with the assumption that users’ behaviors will fit their expectations.

Chapters

00:00: Introduction
01:27: Ben’s non-linear career path: From physicist to product leader
03:23: The “infovore” mindset in product management
06:00: Storytelling, juxtaposition, and the science of learning
08:48: Designing product for attention
12:00: Why product leaders shouldn’t ignore marketing
15:10: CrossFit’s origins as an internet-native brand
19:44: What is the CrossFit Open?
26:02: Conclusion

Resources

What does LogRocket do?

How AI Can Eliminate the “Chaos Tax” in Enterprise Software | Karthik Viswanathan (TalAiro)

Jeff Wharton — Tue, 20 Jan 2026 14:58:15 GMT

Listen on:
YouTube | Spotify | Apple

TL;DR

In this episode, we’re joined by Karthik Viswanathan. Formerly a product leader at AT&T, Macy’s, and Optum, he’s now the founder of TalAiro, an HR tech startup that is rethinking the operating system for recruiting.

Karthik argues that the hidden failure of the modern tech stack is forcing the user to serve as a “manual integration layer. He explains how the push to “unbundle” features results in a “Chaos Tax”— consuming 40-60% of the workday with fighting disconnected tools rather than doing their jobs.

Beyond that, Karthik also discusses:

How AI can make work more human: Why the true value isn’t in replacing jobs, but automating the “devil’s cut” of administrative work
The journey from enterprise leader to founder: What building TalAiro from scratch taught Karthik about prioritization after years of leading enterprise product orgs, such as focusing on the 20% of workflows that drive 80% of the value

1. The “Chaos Tax” is the invisible cost of “unbundling” (3:10)

Karthik’s core idea: specialization sounded great on paper… until humans became the integration layer (or, the glue). Instead of these tools filling in the gaps where necessary, they’ve become too overwhelming for teams to juggle.

Karthik describes a world where:

Teams use 9–10 tools daily
They pay hundreds per month
They often use 10–20% of what those tools can do
Every copy/paste, reconciliation, and context switch quietly drains decision quality

“It’s like when you go to a happy hour or when you actually make a good barrel of bourbon. It’s a devil’s cut, right? It always seems to just evaporate and then we wonder where that invisible time went.”

The takeaway: Tool sprawl doesn’t just waste time, it lowers decision quality and forces people to justify worse decisions because they’re out of bandwidth.

2. Pushing back on the idea that complexity is the “price you pay” for top-tier systems (6:20)

Karthik asks, if consumers can buy a Tesla in a few clicks, why do we accept other workflows that are incredibly complicated?

When teams are stuck in tool sprawl, and systems don’t connect, each tool:

Has its own dataset
Has its own “AI chatbot” (because of course it does)
Tells a different story

And instead of intelligence, you get noise.

3. Karthik’s product rule: If it matters, it must take 3 steps or less (or be automated) (12:30)

One of Karthik’s most practical constraints is simple: if a workflow matters, it should be automated or doable in three steps. He also sets a speed bar — most tasks in their mobile experience should take about 45 seconds.

The goal is fewer clicks, faster decisions, and less product bloat.

4. The AI question leaders should ask is not “what can we replace?” (15:05)

Karthik argues AI can actually make work more human, because it removes the admin sludge that steals emotional bandwidth.

“I really want leaders to stop asking what can AI replace, and start asking: what human potential are we wasting today?”

When your day is spent reconciling tools and chasing the “real” answer, you burn your best thinking on noise instead of judgment.

The takeaway:

AI should protect human judgment, not replace it
The goal is dignity and time back
Automation should remove the tedious work, so humans can do the human parts

Chapters

00:00: Introduction
2:37: Karthik's product background
4:47: The "chaos tax" and how tool sprawl negatively impacts product efficiency
6:23: Challenges in HR tech
11:36: Working backwards from customer problems to build your digital solution
14:49: How TalAiro differentiates itself as an HR tool
17:41: The role of AI in enhancing human potential
25:44: Karthik's transition from enterprise to startup leader
32:23: Conclusion

What does LogRocket do?

April Dunford’s 1 Killer Question to Expose Weak AI Product Positioning

Jeff Wharton — Tue, 13 Jan 2026 14:44:12 GMT

Listen on:
YouTube | Spotify | Apple

TL;DR

April Dunford, the best-selling author of “Obviously Awesome” and “Sales Pitch,” joins LaunchPod to break down why most AI product positioning collapses when you take a closer look. She has spent 25 years as a startup executive and consultant, helping companies stop guessing and start winning. In a world where everyone states, “We have AI,” April explains how to expose weak differentiation and anchor your story in outcomes competitors can’t match.

In this episode, we cover:

Why positioning is a product problem and how undefined positioning leads to wasted roadmaps, “not good enough” feedback from Sales, and engineering teams burning out on features that don’t win deals
Why “we have AI” is no longer a differentiator, and what to focus on instead
The one killer question that instantly reveals whether a product’s claims are real
Why April loves when competitors lie, and how to ethically trap competitors who over-promise features
And finally, how to sell the “glorious future” without losing the deal you need to close today

1. Why most AI positioning sounds the same (12:20)

We’re past the phase where adding a chat interface or sprinkling AI into a roadmap turns heads. As April puts it, AI has become table stakes — and that’s exactly why positioning has gotten harder.

When every vendor says they’re “AI-powered,” buyers don’t hear differentiation. They hear noise:

“Just saying, ‘Oh, I got a chat interface for this thing.’ Who cares? Nobody cares. Everybody’s got one of those.”

What actually wins deals isn’t the presence of AI, but the specific value it unlocks — and whether that value is something competitors can’t deliver.

2. The killer question that exposes weak AI claims (16:42)

April explains that the fastest way to cut through vague positioning is to teach buyers how to pressure-test vendors themselves.

Rather than arguing feature by feature, the goal is to equip prospects with a simple question that reveals the truth behind the claim. When competitors overreach, the question does the work for you — and credibility collapses instantly.

“The right question is not why everybody loves us so much. The right question is: why pick us over the three other people on the short list and the status quo? What can we do for the business that they can’t?”

This is where strong positioning becomes a sales weapon, not a marketing slogan.

3. Why differentiated value beats AI features every time (15:00)

A recurring theme in this episode: companies often jump straight to talking about value without anchoring it in competitive reality.

The real question isn’t: “What value do we deliver?”

It’s: “What value do we deliver that others on the shortlist cannot?”

AI only matters insofar as it amplifies an advantage you already have — proprietary data, workflow depth, integration, or speed to outcome. Without that anchor, AI becomes interchangeable.

4. Positioning for now vs. Positioning for later (32:56)

April also tackles a tension product leaders feel every day: balancing long-term vision with short-term revenue.

“There’s things we’re worried about for the here and now, and then there’s things we’re worried about in the future. We might make a decision today that says, okay, today we’re positioned around this. That doesn’t necessarily mean that’s the way we win forever.”

Strong teams can hold both:

Positioning that wins deals today, against today’s competitors
A future vision that guides the roadmap without confusing the market

Blurring those two is how teams lose focus, burn out engineers, and stall sales momentum.

Chapters

00:00: Introduction
01:45: April's journey from engineering to marketing to product positioning expert
06:47: The shifting landscape: Position from COVID to the AI era
08:23: Moving beyond "AI washing" to find differentiated value
17:45: Defining your true competitive landscape
22:20: How to be worth your customers' migration risk
25:58: Why April likes when competitors "lie" about their capabilities and features
32:05: Why positioning is critical for product and engineering alignment
36:05: April's new book details

What does LogRocket do?

Is Dashboarding Dead? How AI Is Changing Analytics UX | Robert Henkhaus, VP of Product (Enverus)

Jeff Wharton — Tue, 06 Jan 2026 14:26:56 GMT

Listen on:
YouTube | Spotify | Apple

TL;DR

From U.S. Army sniper to VP of Product, Robert Henkhaus knows a thing or two about high-stakes decision-making. Today, he’s a product leader at Enverus, the software platform guiding billions of dollars in global energy capital.

Fresh off Enverus’ acquisition by Blackstone, Robert joins us to discuss how to innovate when the pressure is on.

In this episode, we cover:

Why “Black Box” AI Fails: How Enverus builds trust with investment stakeholders by forcing AI to “show its work” on multi-million dollar recommendations
The Death of the Dashboard: Robert’s hot take on why AI will soon make traditional charts obsolete
Surviving Acquisition: The “60-Day Horizon” strategy Robert uses to keep team velocity high amidst Private Equity uncertainty

1. Why AI explainability isn’t optional when decisions cost millions (5:37)

At Enverus, customers aren’t asking AI trivia questions; they’re deciding where to deploy tens or hundreds of millions of dollars in capital.

That changes everything.

As Robert explains, many Enverus clients (like geologists) already spend their careers defending interpretations of incomplete data. AI doesn’t remove that responsibility – it amplifies it.

“If you do interpretive work based on something you can’t really see, you have to explain yourself in great detail… AI gives them an answer, but you still have to give them the plan. How did you arrive at that answer?”

The takeaway:

AI answers aren’t enough
Users need to see the reasoning, sources, and steps
Trust has to be earned inside the workflow, not after the fact

2. High-stakes AI can’t live in a chat box or sidebar (6:47)

Early on, Enverus experimented with chat-style AI (like everyone else). But they quickly hit a wall.

“Anyone can toss a chat out there. Chat’s cheap.”

What didn’t work was bolting AI onto an already-dense B2B interface and expecting users to trust it.

Instead, the team rebuilt the experience around progressive disclosure:

Fast answers for users who just need direction
Deep explainability for users who need to defend decisions

That includes:

Linking AI responses directly to Enverus’ research
Showing the full plan that the AI used to reach an answer
Exposing backend logic (e.g., SQL queries) to advanced users

3. From dashboards as insight engines to dashboards as proof (17:53)

One of Robert’s hottest takes during the episode was that AI might eventually even kill traditional analytics and dashboards.

“If AI can skip the step and just give you the insight — and you trust it — we don’t need analytics anymore. Dashboarding might be going away.”

Instead of users digging through charts to find answers, the model flips:

AI surfaces the insight
Dashboards show how the answer was derived

At Enverus, this means:

AI-generated dashboards open pre-filtered and scoped
Users immediately see what changed and why
Analytics become validation, not discovery

4. Keeping the team moving through acquisitions and periods of transition (19:36)

Enverus was recently acquired by Blackstone — a moment that often slows teams down, even when the business is healthy.

Robert’s solution: shrink the planning horizon.

“Instead of thinking about the next year, reduce the horizon. What will still be true in 60 days?”

In practice, this looks like:

Focusing on customer truths that won’t change
Defining clear 60-day goals and outcomes
Giving teams explicit decision rights within that window

Chapters

00:00 Intro
04:23: Product innovations at Enverus
05:33: AI in the energy sector: How Enverus is implementing AI in oil and gas operations
8:17: Progressive disclosure and using AI to improve the user experience
12:09: Product engagement scores: How Enverus tracks success metrics
16:51: How internal teams are engaging with AI at Enverus
19:23: Are dashboards dead? How AI is transforming analytics
21:06: Enverus’ recent acquisition by Blackstone
29:31: Conclusion

What does LogRocket do?

Lessons from the Launch that Became a Silicon Valley Punchline | Berni Fisher, VP Product (Appcues)

Jeff Wharton — Tue, 23 Dec 2025 15:29:33 GMT

Listen on:
YouTube | Spotify | Apple

TL;DR

Today, we’re joined by Berni Fisher, VP of Product at Appcues. Berni has led product at some of the most complex, high-stakes companies in tech, including Apple, Amazon, and ButcherBox.

She was also one of the first 50 employees on the Apple Maps team during its infamous 2012 launch.

In this episode, Berni shares:

What it’s like to ship a product failure so big it becomes pop culture
How Apple responded internally, and how they rebuilt trust with customers
The product rigor behind scaling a complex subscription business at ButcherBox
Why Appcues is letting customers (not hype) drive its AI roadmap

1. “All hell broke loose:” Launching Apple Apps in 2012 (8:00)

Berni joined Apple Maps just weeks before it was announced at WWDC 2012.

Six months later, it shipped — and immediately became one of the most criticized product launches in tech history.

What happened next surprised her.

Instead of panic or blame, leadership pulled the team together:

“Leadership came in, they sat us down. They wanted to understand our point of view on what had happened. And then together we committed to getting through it.”

The lesson:

Identify the highest-impact failures
Fix what affects the most users first
Balance short-term mitigation with long-term strategy

2. When “good enough” isn’t acceptable (14:47)

Apple Maps permanently changed how Berni thinks about quality.

“That was the first time I had worked somewhere where there wasn’t this idea of ‘good enough.’ That wasn’t acceptable.”

Under intense scrutiny, the team rebuilt Apple Maps piece by piece:

Working with data providers while building internal overrides
Launching Apple’s own field-collection fleet
Raising the bar on what “ready to launch” actually means

Even today, Berni still uses Apple Maps and smiles when people are surprised.

3. Rebuilding checkout weeks before Black Friday at ButcherBox (22:53)

At ButcherBox, Berni faced a clear problem early on: an outdated, high-friction checkout flow. The challenge was timing: the team was mid-Shopify migration and heading into Black Friday and Cyber Monday, the most critical weeks of the year.

Instead of waiting, she made the call to recalibrate checkout anyway, with risk controls in place.

“We were pushing hard to hit Black Friday, Cyber Monday and make sure that we were ready to go. The uplift was incredible — double-digit conversion just by simplifying checkout.”

What product leaders can learn from this: Don’t wait for perfect timing. Assess risk and ship when the upside is clear. And staged rollouts and fallback plans make bold decisions safer.

4. Letting customers lead the AI roadmap at Appcues (26:58)

At Appcues, Berni and her team took a different approach to AI than most. Instead of starting with the technology, they started with customers.

Using their own in-product messaging, Appcues asked customers:

Which problems matter most?
Where would you trust AI?
Where wouldn’t you?

“We were very surprised by where customers said they were willing to trust AI — and where they weren’t.”

The result?

That input led to Captain AI, now one of Appcues’ most successful launches — without a major marketing push.

“It has been the most successful launch we’ve had in terms of usage.”

Chapters

00:00 Introduction
01:43 Berni Fisher's product journey
04:44 Challenges and Lessons from Apple Maps
15:26 Transition to ButcherBox
17:27 Innovations and Customer Focus at ButcherBox
24:35 AI Innovations at Appcues
27:34 Conclusion

Links

What does LogRocket do?

Why Top-of-Funnel Traffic is Dead (& How TED is Replacing It ) | Tricia Maia, Head of Product (TED)

Jeff Wharton — Wed, 17 Dec 2025 14:58:54 GMT

Listen on:
YouTube | Spotify | Apple

TL;DR

Today, we’re joined by Tricia Maia, Head of Product at TED. We all know TED Talks — but behind the scenes, TED is undergoing a massive product transformation to adapt to a post-AI media landscape. In this episode, Tricia Maia, Head of Product at TED, pulls back the curtain on how they’re solving the “discovery” crisis facing digital media today.

Tricia shares:

Why “views” are dead: Explaining why TED is abandoning top-of-funnel traffic as their North Star metric and shifting focus to “depth,” completion rates, and account signups to combat volatile search algorithms
AI that actually scales: How TED is using advanced AI auto-dubbing — not just subtitles — to clone speakers’ voices into other languages, driving 2-3x better performance
The “gap” strategy: The challenge of connecting a decentralized ecosystem of free users and volunteers at TEDx with an ultra-premium live experience that can cost up to $12,500 per ticket

1. What does “product” even mean at TED? (3:00)

When people hear “Head of Product at TED,” the first question is usually the same:

What does product even mean there?

As Tricia explains, TED’s product surface area spans three distinct worlds:

Events: Ticketing, attendee apps, staff tools, and in-person experiences for flagship TED and TEDx conferences
Media: Distributing talks across TED.com, mobile apps, YouTube, podcasts, and social platforms
Impact initiatives: Supporting global programs like the TED Fellows program, translators, and TEDx organizers

The Product team at TED isn’t just shipping features; it’s enabling connection, discovery, and participation at a global scale:

“We’re a small team, but we cover product management, design, data, analytics, and even community support. All of that lives inside product.”

2. The metric (views) TED relied on for years is breaking (15:30)

For most of its history, TED’s north-star metric was simple: talk views. More views meant more reach, more impact, and more ad revenue. But that model is cracking.

As discovery shifts toward short-form platforms, AI-generated search, and algorithmic feeds, Tricia says views alone no longer reflect real value or real engagement.

“Is someone just clicking on a talk? Or are they actually consuming the idea?”

TED is now questioning long-held assumptions and exploring metrics like:

Completion rates
Repeat engagement
Account signups
Authenticated sessions
Long-term retention across platforms

What product leaders can learn from this:

Legacy metrics can quietly become vanity metrics
The numbers that once mattered may no longer be the ones you can control
Depth of engagement often beats raw reach

3. Monetization without a paywall (18:45)

Tricia says TED will likely never paywall its core content; this is fundamental to their mission.

So how does a nonprofit media organization survive when traffic becomes unpredictable?

Tricia explains how TED is diversifying using:

Memberships (starting at $5/month)
Events (from local TEDx to flagship conferences)
New products, including games
Continued advertising

The real shift is moving from anonymous audiences to known, connected users.

“If someone is anonymous, we can’t really serve them well. Once they tell us who they are, we can actually give them something relevant.”

What product leaders can learn from this:
Sustainable growth isn’t about squeezing more out of top-of-funnel traffic. It’s about building trust, identity, and ongoing relationships.

4. How AI is expanding TED’s mission (31:00)

One of the most exciting parts of TED’s recent evolution is its AI-powered auto-dubbing initiative.

TED partnered with AI voice and lip-sync technology from Panjaya to translate talks into several languages, all while preserving the speaker’s voice, tone, and presence.

The results?

Dubbed talks perform 2–3x better than subtitled versions
Entirely new global audiences are discovering TED for the first time

For TED, this isn’t just efficiency; it’s mission alignment at scale.

Why this matters:
AI isn’t just accelerating teams internally; it’s unlocking access to ideas for people who were previously excluded.

Chapters

00:00: Introduction
02:01: Tricia Maia’s journey to leading product at TED
03:51: Understanding TED’s product and media strategy
11:30: What does “product” mean at TED?
13:55: How TED is adapting to the changing media landscape
14:41: The impact of AI on TED’s operations
17:01: The importance of user engagement and metrics beyond vanity metrics
26:12: Connecting TED’s digital and in-person event audiences
34:19: Innovations in AI auto-dubbing TED talks
39:11: Conclusion

Links

What does LogRocket do?

Make the C-Suite Think Like a Startup (Without Getting Fired) | West Stringfellow, VP Product (ex-Target, Blackhawk)

Jeff Wharton — Tue, 09 Dec 2025 14:32:10 GMT

Listen on:
YouTube | Spotify | Apple

TL;DR

Today we’re joined by West Stringfellow, VP of Product at Blackhawk and former VP of Innovation at Target. West is a master of managing up, having spent his career driving transformation at major enterprises while also founding multiple startups. One of them was acquired by Target, where he went on to become VP of Innovation and launch the company’s still successful startup incubator.

In this episode, West shares:

How he helped a Fortune 100 retailer think and act more like a startup using his years of founder experience and data-driven strategy
Why aligning with executive incentives and real business goals is the fastest way to unlock innovation and get the C-suite to trust your product strategy
The playbook he now uses at Blackhawk Networks to drive AI adoption in a regulated enterprise by empowering AI “culture carriers”

1. Big companies and startups struggle with the same problems (8:40)

Before West ran innovation at a $77B company, he was a startup founder. He discovered something interesting:

Startups and enterprises have the same concerns. They both ask:

Who is the customer?
Where is the competition going?
Where is the market moving?
How do we grow — fast?

Why this matters:
If every company struggles to find growth, product leaders with founder experience can become some of the most valuable innovators inside the enterprise.

2. Managing up without getting fired (09:39)

West has built his career on helping giant organizations move faster, without getting shut down by bureaucracy. One of his most famous moves was printing 300+ copies of his product strategy and hand-delivering them to every executive at Target.

His advice: don’t make it about you, make it about the business.

“I approached sharing this information with Target purely from a place of, Hey, I’m sincerely trying to help you grow your business. Nothing in the data that I shared with them was my opinion.”

What product leaders can do:

Frame every idea around revenue, efficiency, or customer value
Lead with data, not opinion
Make executives the first customers of your idea

3. Speak the language of incentives (13:28)

To influence executives, you first have to understand them:

“Figure out who they are, figure out what they care about, and help them do their jobs. That’s what they really care about.”

West shares that Target’s CEO, Brian Cornell, loved that his data-driven strategy was refreshingly clear:

“Brian said, By the time things get to my desk, all the data has been sandblasted out of them… It’s so refreshing to see the data.”

What product leaders can do:

Map your strategy directly to business-critical KPIs
Execs are busy; give them just enough detail to understand the strategy

4. Transforming a regulated enterprise with AI, one “culture carrier” at a time (26:13)

At Blackhawk, West is leading AI adoption in a heavily regulated financial environment. Instead of top-down mandates, he empowers the naturally curious first:

“Those are the people who are the best to empower. They will carry the culture further in the organization than anyone could ever push.”

The metric he cares about most?

“When I see the light in the team’s eyes… when they do it for the first time, and they go, Oh my gosh. Everything is about to change.”

What product leaders can do:

Start with your AI early adopters
Teach the process of working with AI, not just the tool
Build a peer-to-peer community that lifts the entire org

Chapters

00:00: Introduction
01:17: West’s career journey
02:08: Project Goldfish and West’s startup background
05:43: Making product and strategy decisions at Target
06:25: West building a Techstars Startup Accelerator
08:39: How West’s work at Target inspired his startup, HowDo
09:44: How did West “manage up” at Target?
17:05: An introduction to Blackhawk
21:02: Digital transformation with gift cards
23:44: How Blackhawk is using AI
30:29: Big AI wins
33:09: Conclusion

What does LogRocket do?

Why PMs are Leveling up into AI Product Engineers | Sarah Jacob Singh, CPTO (Medbridge)

Jeff Wharton — Tue, 02 Dec 2025 14:38:41 GMT

Listen on:
YouTube | Spotify | Apple

TL;DR

Today, we’re joined by Sarah Jacob Singh, CPTO at Medbridge, a digital healthcare platform.

In this episode, Sarah shares:

Why AI means all companies have to act like startups again, with product more tightly integrated from engineering all the way to go-to-market
How many Product Managers are evolving into Product Engineers - building prototypes, shipping code, and helping developer teams innovate faster
The ways Medbridge is leveraging AI-enabled Product Engineers to ship big bets weekly instead of quarterly

1. Product teams can’t ship great products alone (3:00)

Sarah learned early in her career that building a product isn’t enough. If GTM teams don’t fully understand what’s shipping, customers won’t either:

“It’s not enough to just kind of be siloed and build it. You have to work with product marketing and sales enablement to make sure that all of the great stuff that’s being built is actually being delivered to the sales team in a way that you want them to talk about.”

What product leaders can do:

Put product and GTM in the same weekly operating rhythm
Prioritize message clarity as much as feature delivery

2. AI shifts the bottleneck from engineering to product and customer validation (9:43)

Engineering isn’t the slow part anymore:

“We’re seeing huge shifts in the ability to just literally deploy code way faster.”

But faster code is useless without faster learning:

“The engineer’s time should be focused on what is complicated, and then getting the customer feedback. The feedback loop also now becomes smaller.”

What product leaders can do:

Move engineers into the discovery cycle, not after it
Give PMs tools and skills to close the loop themselves
Treat customer validation as the true velocity constraint

3. AI is breaking the old boundaries between product and engineering (10:00)

Sarah says, “This idea of there needs to be tension between product and engineering — I think that is a very outdated idea in the age of AI.”

Teams are suddenly able to move faster than their development processes allow, and roles must evolve to keep up. Sarah’s own role, as both a Product and Technical lead, demonstrates this collaboration.

What product leaders can do:

Normalize PM-built prototypes so engineering only tackles the complex problems
Co-own success: shared roadmap, metrics, and user outcomes, not just delivery milestones

4. The rise of the “Product Engineer” (11:50)

Sarah predicts a major shift in R&D org structures:
→ PMs writing small code changes
→ Engineers joining customer calls
→ Joint ownership of prototypes, MVPs, and learning

“Somewhere in the middle is going to be this AI-enabled product engineer. I bet 10 years from now, that is the primary position in R&D.”

At MedBridge, it’s already happening:

“The MVP will be built by the PM. Then, the engineer can go back and be like, I know exactly what to do to make this a post-MVP product.”

Why this matters
Fewer hand-offs → less misinterpretation → faster validation.

Chapters

00:00: Introduction
01:53: Sarah’s career journey
03:56: The expanding role of product management
08:22: The impact of AI on product and engineering
11:35: Prototyping and feedback loops
17:20: AI adoption in healthcare
19:04: What is the “product engineer”?
22:47: In-house vs. Purchased solutions
29:13: Medbridge’s upcoming hackathon
30:54: Conclusion

What does LogRocket do?

A Serial Founder’s Guide to Pivots, Exits, and AI | Raj Singh, VP of Product (Mozilla)

Jeff Wharton — Tue, 25 Nov 2025 14:12:15 GMT

Listen on:
YouTube | Spotify | Apple

TL;DR

In this episode of LaunchPod, we’re joined by Raj Singh, VP of Product at Mozilla, a serial founder with several startup exits and a career defined by pivots, hard-earned product lessons, and deep expertise in AI, browsers, and the future of the web.

In this episode, Raj shares:

How his companies navigated multiple pivots, with innovations from ChatGPT and Zoom leading most recently to an acquisition by Mozilla
What makes “agentic browsers” the next major interface for the web, and how they could change everything from ad models to API access
Why Mozilla’s stewardship of Gecko, one of only three major browser engines, is essential to keeping the internet open in the age of AI

1. Pivoting is about market truth, not persistence (3:15)

Raj’s entire founder journey is defined by pivots and the reality that the first idea is almost never the right one. He explains why segmentation mistakes nearly killed his last startup: they built meeting-summarization for the wrong quadrant: internal, multi-party meetings with low reference value. The high-value use case (external 1:1s) was hiding in plain sight.

Then, when COVID hit, they pivoted again — into video communication. And when Zoom took off instead, Raj’s team pivoted… again.

It’s a skill to recognize when your idea isn’t quite right, reframe it, and rebuild around a clearer market insight. And each shift came from Raj’s willingness to ask:

“What if our core assumption is wrong?”

What product leaders can do:
Build a muscle for market refactoring. Instead of asking “How do we make this idea work?” ask:

Where is the real usage?
Who gets the most enduring value?
What job is the product actually doing today vs. what we hoped it would do?

2. Remove product debt as ruthlessly as tech debt (7:58)

One of Raj’s strongest insights is that product teams don’t just accrue technical debt — they accrue product debt.

“The issue is what I call people think of technical debt, but I call it product debt or sunk cost.”

What product leaders can do:
Audit your product for “emotional attachment features.” If your team can’t explain why something still matters today, cut it. Treat removal as a core product skill, not a failure.

3. The rise of agentic browsers (19:00)

Raj believes we’re entering a shift as big as mobile. He says, “This is the new interface for the web.” AI-first, agentic browsers are about to redefine how users search, navigate, and take action on the web.

Why this matters:

Browsers hold the deepest intent data
Agents can act on a user’s behalf
The ad-based internet breaks when agents (not people) are viewing content

It’s why Amazon issued cease-and-desists to AI browsers. And it’s why the browser category is suddenly hot again after a decade of stagnation.

And it’s why Mozilla’s role matters more than people realize.

What product leaders can do:
Prepare for a world where your product is consumed through an agent, not a user. Rethink funnels, data, ads, SEO, and onboarding with this future in mind.

4. The strategic role Mozilla plays in an AI-first internet (26:42)

With Chrome dominating, most people forget that only three major rendering engines exist: Chromium, WebKit, and Mozilla’s Gecko.

Raj makes it simple:

“We are kind of the check and balance… because we are one of the major rendering engines. We’re one of the three.”

Without Mozilla, the web becomes far easier to monopolize, and far easier for AI-infused browsers to optimize around proprietary markup controlled by one company.

What product leaders can do:
Don’t underestimate the power of open standards. The future of AI interfaces will be built on the decisions these rendering engines make today.

Chapters

00:00: Introduction
01:50: Raj’s entrepreneurial journey
03:52: The evolution of meeting summarization tools
07:51: Raj’s product pivot
08:26: Adapting to video communication during the pandemic
16:05: Pulse’s viral growth and Mozilla acquisition
20:25: AI and browser integration
27:10: Mozilla’s role in browser innovation
30:58: Conclusion

What does LogRocket do?

When CPO Becomes CMO: The Expanding Role of Product Leaders | Karen Chao (Flowspace)

Jeff Wharton — Tue, 18 Nov 2025 14:54:53 GMT

Listen on:
YouTube | Spotify | Apple

TL;DR

In this episode of LaunchPod, we’re joined by Karen Chao, Chief Product Officer at Flowspace, where she also leads marketing — a dual role that reflects a growing trend in how product leaders are being asked to operate.

Karen shares:

How she became both CPO and Head of Marketing, and why combining the two improves alignment between product and GTM
How Flowspace’s product team uses AI tools like Claude, Cursor, and coding agents to accelerate discovery, prototype faster, and ship small bug fixes
Why product leaders need to prepare for AI-powered go-to-market automation, and how marketing functions will evolve as AI takes over more operational and analytical work

1. Use AI to improve discovery, not just delivery (3:48)

Karen’s team doesn’t treat AI as a feature add-on. They use it from the first moments of discovery, from competitive research, early ideation, to pressure-testing product thinking before getting engineers involved.

“We’re using Cursor and Claude hooked up to our code base. They help us ask questions we might ask our tech lead.”

By interrogating the codebase directly through AI, PMs enter engineering conversations with clearer requirements and fewer blind spots.

What product leaders can do: Treat AI as your first reviewer. Run PRDs, problem hypotheses, and early ideas through AI agents before any refinement meeting. You’ll reduce churn and increase decision clarity.

2. Let AI handle the tiny things engineers shouldn’t (6:57)

Flowspace’s PMs now use coding agents to handle the “microfixes” that traditionally rot in the backlog: missing fields, copy inconsistencies, small logic tweaks, etc.

“Some folks on my team have gotten really into these coding agents and are actually starting to push out code fixes. Obviously it goes through the typical development cycle, but those are things we can do instead of sending it to the engineer.”

These are changes too small to distract engineers with, but meaningful enough to remove friction from the product.

What product leaders can do: Create a category of AI-owned quick wins. Let PMs use coding agents to ship tiny fixes that unblock customers without pulling engineers out of flow.

3. When product leaders get asked to “do more with less” (15:11)

Karen’s marketing leadership role came to her because Flowspace needed tighter alignment across product, messaging, funnels, and customer understanding. This reflects a broader shift: product leaders being asked to absorb more GTM responsibility.

“Marketing seemed like an opportunity to bring product and marketing closer. Taking over marketing is only gonna make me a better product leader.”

What surprised her most was how naturally product thinking transfers to marketing: customer insights, funnel logic, problem-solving, and data-driven decision-making.

What product leaders can do: Increase collaboration between product and GTM. Even without owning both, run shared funnel reviews, shared customer interviews, and shared alignment rituals.

4. Marketing’s next transformation will be AI-powered (17:56)

As Karen dug deeper into marketing, she immediately saw the next frontier: AI-driven automation across lead qualification, funnels, and operational tooling.

“I think every person in their function and every function needs to be thinking about how AI can help them be more effective going forward in this new way of working.”

She also encountered the “spaghetti” of today’s marketing tooling — many systems, loosely connected, creating operational drag.

What product leaders can do: Treat AI as marketing infrastructure. Adopt agentic lead qualification, automated segmentation, funnel diagnostics, and smarter multi-tool orchestration.

Chapters

00:00: Intro
02:06: Karen’s career highlights
03:59: How Karen and Flowspace are using AI in their team workflows
15:11: The intersection of product and marketing
22:13: What’s surprised Karen most about transitioning from product to marketing
29:12: Conclusion