app_store_button

google_play_button

DK - Details page - Device banner - 894x1036

Lyt når som helst, hvor som helst 

Mind the Product

The Product Experience features conversations with the product people of the world, focusing on real insights of how to improve your product practice. Part of the Mind the Product network, hosts Lily Smith (ProductTank organiser and Product Consultant) & Randy Silver (Head of Product and product management trainer) “go deep” with the best speakers from ProductTank meetups all over the globe, Mind the Product conferences, and the wider product community.

The Product Experience

Jonathan Evens is a product lead at Google DeepMind, where he has spent more than a decade applying machine learning and AI across industries — from the smart grid at AutoGrid, to detecting roads and buildings from satellite imagery at Planet, to recommender systems, Google Search's AI Overviews and AI Mode, and now live avatars. He is also an advisor to the Evens Foundation, where he is building a "digital citizenry": a democracy sandbox that uses synthetic citizens to pre-test how the public might react to a policy before it is written.

Jonathan returns to The Product Experience, where hosts Lily Smith and Randy Silver pick up the conversation they started at MTPcon London, to dig further into what actually separates an AI product manager from a product manager who simply uses AI tools, why product principles have to come before evaluations, and how synthetic users can help — and mislead — at very different scales of product.

We discuss:

1. Why "AI product manager" has become a near-meaningless label, and the two distinct roles hiding underneath it: the modelling product manager working on core model capabilities, and the AI feature product manager building AI-powered products

2. Why using an LLM as a thinking partner or a coding assistant does not make someone an AI product manager — it makes them a product manager using AI tools, full stop

3. How Google Search's North Star metrics have stayed constant even as the proxy metrics beneath them — side-by-side win rates, user ratings, RLHF signals — have had to be rebuilt from scratch

4. Why product principles, not evaluations, are the real starting point for any AI feature, and how Google Search resolved the problem of trustworthy sources disagreeing on basic facts

5. How Google Search builds trust into its AI Overviews through sourcing, citation placement and UX cues such as highlighting, so users can judge at a glance what to verify

6. Where synthetic users genuinely help — cold-start problems, privacy-sensitive research, automated regression testing — and where they fall short

7. Building the Evens Foundation's "digital citizenry", and the core technical problem behind it: AI-generated personas that are less diverse and more extreme than real people

8. How team size and structure differ between a fully resourced lab like Google DeepMind and a resource-constrained non-profit team, and why Jonathan resists a single answer for the "right" team size

9. How the product manager's job is shifting as engineers absorb more of the evaluation work themselves through prompting and iteration

10. Jonathan's advice for product managers building AI features, and his case for following the Makers Manifesto

 Key takeaways

 • "AI product manager" covers two distinct jobs. The modelling product manager defines and measures a model's core capabilities — factuality, reasoning, long context — and that role is concentrated almost entirely inside frontier labs. The AI feature product manager builds a product or feature on top of an existing model, and needs domain expertise and user empathy far more than technical depth. Conflating the two is why the title has become so diluted.
 • Using an LLM to think faster or write code faster does not make someone an AI product manager. It makes them a product manager using AI as part of their toolkit — the same as any other knowledge worker. The distinction matters because it clarifies what skills are actually being tested.
 • Product principles have to come before evaluations, not after. Before Jonathan starts building an eval set for a new product, he first asks what the product is meant to feel like and what values it should encode. Google Search's response to sources disagreeing on a monument's construction date, or to large language models hallucinating at scale, came from principles about trustworthiness established before any metric was built.
 • Trust in an AI feature is built through sourcing and interface design as much as through the model itself. Google Search's AI Overviews are constrained to draw only from ranked, trustworthy documents rather than the model's own memory, and users are given UX signals — citation placement, highlighting — that let them judge at a glance how much to verify.
 • Synthetic users add genuine value in cold-start scenarios, privacy-sensitive research and automated regression testing. Where they fall short is diversity: AI-generated personas tend to be less varied and more extreme than real people, which is the central technical problem behind the Evens Foundation's digital citizenry project.
 • There is no fixed answer to the right team size. Jonathan sees a gradient, from a senior developer working entirely alone, up to the Evens Foundation's single product manager with AI-assisted development skills, up to a fully staffed Google team — with the deciding factor being how unsolved the underlying problem is, not company size.
 • As engineers absorb more evaluation work themselves through prompting and iteration, roles are blending. What still sits with product management is the judgement calls that follow from product principles — deciding, for example, which technical trade-offs actually matter to the use case, rather than which are easiest to measure.

Features links

- Evens Foundation — https://evensfoundation.eu

- Makers Manifesto — https://makersmanifesto.org

- Google DeepMind — https://deepmind.google

- AutoGrid — smart grid AI company where Jonathan began applying machine learning to industry

- Planet — satellite imagery company where Jonathan worked on automated road and building detection

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Our Hosts
Lily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She’s currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. 

Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury’s. He participated in Silicon Valley Product Group’s Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He’s the author of What Do We Do Now? A Product Manager’s Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon’s music stores in the US & UK.

What is AI product management, really? Jonathan Evens (AI Product Lead, Google DeepMind)

Kirsten Mann is a board director, product leader and, with this episode, a three-time guest on the podcast. Last time she was here, she was building Vizory, an AI tool that helps company directors get through board packs. This time she's back to explain why she isn't building it any more. Talking to Randy Silver, she walks through exiting Vizory, the friction tests she ran before writing a line of code, and why she now believes distribution, not the build, is where most AI products actually die.

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Key takeaways

 1. Before writing a line of code, Mann tested for force rather than sentiment: she asked directors for two confidential board packs and an audio recording of themselves reviewing one, and only started building once 10 people agreed to do it. Coffee-shop enthusiasm is cheap; handing over a company's most sensitive document is not.
 2. Vizory's most-loved feature in demos, cross-pack search, was barely used once shipped. Directors said they wanted it and reacted strongly when they saw it, but in practice they went straight to an automated triage view instead — a clean case of stated preference diverging from revealed preference.
 3. Board software runs on quarterly, not weekly, cycles, and trust compounds slower than value does. Mann modelled two review cycles before directors would rely on the tool; in practice it took three, meaning some customers on quarterly boards needed close to a year before the value became obvious, a timeline no 30-day trial can accommodate.
 4. Pricing got caught in a double anchoring trap. Directors first benchmarked Vizory against the $20-a-month ChatGPT and Claude price point, so Mann positioned against the cost of a governance failure instead, then created a second anchor by pricing early pilots at $150 a seat against a $300 target, which made the later increase read as a 100% price rise.
 5. Cutting friction is the wrong instinct early on. Mann deliberately added friction, asking for sensitive documents and charging as early as possible, to separate real demand from polite interest, arguing that most founders run tests designed to confirm they're right rather than to find a reason to stop.
 6. Mann's main lesson for other founders is that distribution is now the product problem. AI has collapsed the cost of building software but done nothing to the cost of reaching people who trust you, which is why she pushed to add distribution, adoption and willingness to pay as a third discipline in the Makers' Manifesto, alongside building the right thing and building it right.
 7. Multi-model products carry a new operational risk. One of Vizory's AI "judges" silently stopped being selected because the underlying model had been deprecated overnight without warning, a reminder that model drift means the QA and evals work never really stops, however fast the initial build was.

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Our Hosts
Lily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She’s currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. 

Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury’s. He participated in Silicon Valley Product Group’s Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He’s the author of What Do We Do Now? A Product Manager’s Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon’s music stores in the US & UK.

What I learned from building, and exiting a startup — Kirsten Mann (Strategic Advisor)

April Dunford is the positioning expert behind Obviously Awesome and a former repeat vice-president of marketing across seven venture-backed startups, most of which were acquired. Over the past decade she has advised roughly 300 B2B technology companies, all with sales teams, on how to position themselves against the competition. In this episode she joins hosts Lily Smith and Randy Silver to explain why so many companies are repositioning at once, how a strong point of view on the future underpins good positioning, and why the story a company tells about itself is a decision for product and sales, not just marketing.

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Key takeaways

 1. Positioning is a company-wide decision, not a marketing exercise. Dunford's own experience repositioning a spreadsheet tool as an embeddable database shows how it reshapes pricing, sales motion and even the product roadmap, not just the words on a website.
 2. Major shifts such as the move to AI force widespread repositioning because customers no longer have a stable set of alternatives to judge value or price against, and both AI-native companies and traditional SaaS businesses are wrestling with where they now sit.
 3. Intercom's rebuild of its support product around Fin shows how staying anchored to the customer's underlying job, resolving a ticket, can guide a genuine AI-first redesign rather than a bolt-on feature.
 4. Companies need a clear, credible point of view on the future of their market, or customers facing genuine uncertainty will simply freeze and delay buying decisions.
 5. A compelling vision of the future has to flow from a company's real differentiated value, not be reverse-engineered to flatter its current position.
 6. Selling too far into a hyped future risks stalling deals, so the message needs a maturity model that shows customers a credible, low-risk path from where they are today to where the market is heading.
 7. Positioning should be revisited on a disciplined schedule rather than settled by whoever argues loudest in the room, and Dunford recommends a structured check every six months on competitors, differentiators and value themes.
 8. Customer advisory boards, quarterly executive account calls and a company's own sales team are the most reliable early-warning systems for shifts in budget, buying process and competitive threats, long before they show up as lost deals.

Chapters

 • (00:00) Introduction to April Dunford 
 • (01:53) The story behind Obviously Awesome 
 • (05:33) Positioning as a cross-functional decision 
 • (07:23) Why everyone is repositioning right now 
 • (09:32) Intercom, Fin and the AI-native rebuild 
 • (11:53) Building a point of view of the future 
 • (16:52) Is the vision genuine or self-serving 
 • (18:00) How to develop your point of view 
 • (22:13) Stack Overflow, Salesforce and staying silent 
 • (23:45) Hyping the future without stalling sales 
 • (27:01) When positioning needs to change 
 • (28:42) Running a regular positioning check-in 
 • (30:29) Customer advisory boards and voice of customer 
 • (34:47) Predicting change after covid and AI 
 • (37:20) Wrap-up

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Our Hosts
Lily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She’s currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. 

Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury’s. He participated in Silicon Valley Product Group’s Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He’s the author of What Do We Do Now? A Product Manager’s Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon’s music stores in the US & UK.

How to position your product for a future nobody can predict - April Dunford (Author of Obviously Awesome)

Julia Barham leads a CX acquisition team at Progressive Insurance and is the author of The Product Management Playbook, published by Rosenfeld Media in July 2026. She wrote it to close what she sees as a coaching gap in the profession: a decade of product transformations has produced far more people with the title than people who have been taught end-to-end craft. In this episode she makes the case for treating ambiguity as a condition of the job rather than a problem to be solved, and walks through the things that quietly break when a product starts to scale.

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Key takeaways

 1. Frameworks come and go, but the questions endure. Julia structured her book around why something matters, who it is for, what needs building and when, because no methodology eliminates ambiguity, it only reduces it.
 2. Organisational ambiguity is the least discussed of the four ambiguities PMs face, and the one that separates individual contributors from leaders. Waiting for the perfect operating model, funding model or team shape is a way of not moving.
 3. If you have to be in every room to answer every question, you are scaling chaos. Durable artefacts, bug severity rubrics and self-service dashboards let the team make calls without you.
 4. Synthesis is where shared context gets built, and offloading it to an AI tool quietly removes the thing that made it valuable. Do it together, monthly, with the customer, platform and business data in the same room.
 5. Chasing growth before product market fit turns your economics upside down. Products commonly take two years to find fit, sometimes five, and retention is the strongest signal that you have it.
 6. Julia spent nine months fixing latency on an inherited platform because of shortcuts taken at launch. The cost was measured in millions of lost revenue, not just engineering time.
 7. Attaching a monetary value to technical debt is what turns a product manager from a stick in the mud into a steward of the business. Treat your product like a P&L whether you own one or not.
 8. A product at scale needs a portfolio, not a backlog: optimisation, strategic bets, capability work, and honest capacity set aside for run-the-business support.
 9. AI belongs in the toolkit, not in the chair. If you cannot call BS on the output, you do not know enough to be doing the job.

Chapters

 • (00:00) Don't scale chaos
 • (01:01) Introducing Julia Barham
 • (03:01) The coaching gap that prompted the book
 • (03:57) Why the book is built around questions, not frameworks
 • (06:06) Has product management ever been deterministic?
 • (07:47) The four ambiguities every product manager faces
 • (10:00) Does organisational ambiguity change with company size?
 • (12:57) The 21 plays and how to use them
 • (15:35) Getting your reps in across the product lifecycle
 • (17:07) What breaks when products and teams scale
 • (17:59) Mistake one: needing to be in every room
 • (20:30) Building shared context across distributed teams
 • (23:51) The ways of working exercise
 • (24:19) Mistake two: chasing growth before product market fit
 • (25:56) How to measure product market fit
 • (27:16) Mistake three: scaling expensive problems
 • (29:42) Putting a price on technical debt
 • (31:54) When taking on debt is the right call
 • (34:22) Naming the mode your product is in
 • (35:09) Mistake four: running your product as a portfolio
 • (37:39) The one problem Julia would make disappear
 • (39:25) What AI changes, and what it does not
 • (42:26) Wrap-up

Referenced

 • The Product Management Playbook, Julia Barham, Rosenfeld Media: 
https://rosenfeldmedia.com/books/product-management-playbook/ • Use discount code MTP20 for 20% off at Rosenfeld Media
 • Sample chapter: 
https://rosenfeldmedia.com/sample-chapter-the-product-management-playbook/ • Dan Olsen and the product market fit pyramid: 
https://dan-olsen.com • Testing Business Ideas, David Bland
 • Progressive Insurance: 
https://www.progressive.com • Pioneers, settlers and town planners, Simon Wardley: 
https://blog.gardeviance.org/2015/03/on-pioneers-settlers-town-planners-and.html
We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Our Hosts
Lily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She’s currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. 

Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury’s. He participated in Silicon Valley Product Group’s Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He’s the author of What Do We Do Now? A Product Manager’s Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon’s music stores in the US & UK.

Four mistakes scaling teams make - Julia Barham (Author and Product Executive)

Tiama Hanson-Drury is CPTO at Opus 2, the legal technology company behind the systems that run some of the world's largest and most high-stakes litigation. She started her career in sales, moved into product in 2010 and has spent the last 16 years split roughly evenly between individual contributor and leadership roles. Her verdict on AI in product organisations is neither evangelism nor scepticism: the tooling has removed software as a bottleneck, but the markers of quality that mattered before AI have not changed, and teams that forget them end up shipping slop and burning out. In this episode, we discuss:

 1. Why a sales background is better preparation for product than an engineering one, and how to lead engineers without pretending to be an expert
 2. How the promise of doing more with AI is producing overload and burnout, and what leaders owe their teams in response
 3. Why high AI adoption scores mean nothing if pull request sizes are ballooning and someone else has to review the output
 4. The three things Tiama looks for in her teams now: outcome focus over craft, curiosity, and a culture of sharing failure as readily as success
 5. Why the right move is not to hand three of your seven steps to AI, but to start again from the outcome you want
 6. How Opus 2 went from shipping every six to 12 weeks to shipping daily, and why that made documentation and planning more important, not less
 7. The case for betting on humans in the loop when your customers explicitly prefer it
 8. Why Opus 2 is still hiring juniors, and how to build commercial judgment when the groundwork can be skipped
 9. The one situation where Tiama tells people to let AI write the first draft rather than the second

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Chapters

 • (01:31) From sales to product
 • (03:24) Why the move is less obvious than it sounds
 • (04:34) Leading engineering without an engineering background
 • (06:28) How outsider questions sharpen engineering teams
 • (07:36) What AI has changed for a CPTO
 • (08:16) Overload, burnout and the pressure to token max
 • (10:32) Adoption scores versus quality signals
 • (11:39) What AI adoption actually looks like inside law firms
 • (12:42) Outcomes over output
 • (14:07) How Opus 2 built its AI strategy
 • (16:07) Removing friction from an AI rollout
 • (16:53) Partnering with AI instead of splitting up the steps
 • (18:08) A message from Mike Belsito
 • (19:40) Three things AI asks of a team
 • (21:47) More agency, and why planning matters more
 • (23:51) Scaling a team on conflicting evidence
 • (26:09) Betting on humans in the loop
 • (27:36) Why Opus 2 keeps hiring juniors
 • (29:44) Building judgment when the work moves faster
 • (32:36) Sharing your own AI operating system
 • (33:22) AI slop, CVs and the hiring algorithm
 • (36:17) Top tips for a product career in the age of AI
 • (38:36) Wrap-up

Referenced

 • Opus 2: 
https://www.opus2.com • Opus 2 announces addition of Tiama Hanson-Drury as chief product and technology officer: 
https://www.opus2.com/news/opus-2-announces-cpto-tiama-hanson-drury/ • Minna Technologies, where Tiama was previously chief product officer: 
https://minnatechnologies.com • DX, the developer intelligence platform used to track squad performance: 
https://getdx.com • DORA metrics: 
https://dora.dev • Vote for Mike Belsito's South by Southwest 2027 session: 
https://tinyurl.com/belsitosxsw
Where to find Tiama Hanson-Drury

 • LinkedIn: 
https://www.linkedin.com/in/tiamahansondrury
We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Our Hosts
Lily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She’s currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. 

Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury’s. He participated in Silicon Valley Product Group’s Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He’s the author of What Do We Do Now? A Product Manager’s Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon’s music stores in the US & UK.

How to lead a product team through AI adoption - Tiama Hanson-Drury (CPTO, Opus 2)

Blaine Billingsley is a Member of Technical Design Staff at OpenAI whose path into the field ran through music composition, spare-change website work at college, and a decade across Gmail, Airbnb, YouTube and Slack. At OpenAI he was hired to work on Presence, then redirected to solve a more immediate problem: making ChatGPT genuinely useful as a daily tool for designers. Working with a single engineer, he built the ChatGPT product design plugin — a bridge between the raw power of Codex and the day-to-day workflow of product teams. In this conversation with Randy Silver, he talks about what design actually means when your interface is a text box, why volume beats perfection in an age of infinite iteration, and why the fundamentals of good product thinking are more durable than the tools used to apply them.

Key takeaways

— The designer's job at an AI company has shifted from pixels to outputs. Deciding what "good" looks like, building the criteria to evaluate it, and heuristically assessing results is now a core part of the role — one that didn't exist in the same form at Gmail or Slack.
— LLMs don't replace structured creativity techniques; they scale them. The crazy eights exercise squeezes eight ideas from a room of people in eight minutes. A well-directed ChatGPT session can return 80 in the same window, alone, while you're at lunch.
— Volume beats perfection. The best way to make a pot isn't to try to make the best pot — it's to make a thousand pots. That logic now applies directly to prototyping: generate at scale, stay unattached, and find the nugget in the noise.
— Evals are closer to synthetic user research than quality assurance. The hardest part isn't building the rubric — it's correctly anticipating what people will actually try to do. Show it to one more person and your assumptions will immediately break.
— The second 80% problem hasn't gone away. Getting to a working prototype is dramatically faster; getting that prototype to production is still gruelling — and becomes harder still when platform direction shifts mid-sprint.
— Small teams with AI assistance need to protect the rituals that keep them aligned. When two people can each produce a week's worth of work in an afternoon, parallel drift becomes the real collaboration risk.
— Role boundaries are dissolving, but specialisations still matter. The question is less "what is your title" and more "what does the band need right now, and can you play that part?"
— Experience brings judgment; freshness brings juice. The best work often comes from junior designers unconstrained by years of accumulated assumptions — and both things need to be in the room.

Chapters 

 • (00:00) Introduction
 • (01:14) Blaine's background: from music composition to product design 
 • (02:32) What design means at OpenAI 
 • (04:21) The ChatGPT product design plugin 
 • (06:12) Deciding what to build: the early exploration 
 • (10:05) Structured creativity and LLM-powered ideation 
 • (13:37) Volume over perfection: the thousand pots approach 
 • (16:13) Designing as a two-person team 
 • (20:29) What is the job now? 
 • (23:33) Evals as synthetic user research 
 • (27:08) Testing at scale when you can't know your users 
 • (30:15) How they actually did the research 
 • (33:01) The second 80%: from prototype to production 
 • (35:06) Staying aligned without roadmaps 
 • (38:19) Demo: the product design plugin 
 • (44:52) When a prototype isn't ready to ship 
 • (48:26) Design sprints, reimagined 
 • (49:27) Advice for joining an AI-first product team 
 • (52:17) The jazz analogy: experience, freshness and your role in the band 

Featured Links

 • ChatGPT for Work: https://openai.com/chatgpt 
 • Codex: https://openai.com/codex 
 • Figma: https://figma.com 
 • FigJam: https://www.figma.com/figjam 
 • Linear: https://linear.app

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Our Hosts
Lily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She’s currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. 

Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury’s. He participated in Silicon Valley Product Group’s Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He’s the author of What Do We Do Now? A Product Manager’s Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon’s music stores in the US & UK.

What OpenAI taught me to unlearn — Blaine Billingsley (OpenAI, Slack, YouTube, Airbnb)

Dr Cat Hicks is a psychological scientist and the founder of Catharsis, a human-centred research consultancy that works with engineering organisations. After self-funding her first open-access study into developer motivation, she was recruited to lead the Developer Success Lab at Pluralsight — a three-year programme that generated large-scale empirical research across hundreds of companies and more than 11,000 developers. Her book, The Psychology of Software Teams, published in July 2026, brings that evidence to bear on the question her industry keeps asking: why do smart people in smart organisations so often struggle to work well together? We talk about the hidden costs of treating developers as interchangeable units, what large-scale cycle time data reveals about individual performance, and how product managers can build the conditions for teams to actually thrive.

Key takeaways

 1. The "brains and jars" model — treating developers as interchangeable, isolated computing units — does not just feel demeaning; it actively undermines the collaborative, social work that makes software teams effective, and is linked to burnout, self-censorship, and a breakdown of trust.
 2. Cycle time data from 216 companies and over 11,000 developers shows that individual performance fluctuates dramatically week to week — it is not a stable personal trait — which means slow periods are usually an environmental problem, not a personal one.
 3. Over-production pressure (the constant pull towards short-term delivery) has measurable cascading effects: developers stop mentoring, stop surfacing problems to managers, and stop investing in long-term code quality. It can be measured and, with committed leadership, changed within weeks.
 4. AI is producing genuine identity threats, not just productivity disruption. Teams that lower the "threat temperature" — framing change as a shared technical challenge and affirming that new skills can always be learnt — unlock significantly more adaptive and curious behaviour.
 5. Metacognitive scaffolding — building structured strategies for thinking about your own thinking, not just raw output — is more trainable than cognitive capacity and is almost entirely absent from how agentic coding environments are currently designed.
 6. Superordinate goals (shared outcomes that transcend individual preferences) allow diverse teams, including those who prefer deep solo work, to collaborate productively without demanding that everyone care about the product in the same way.

Chapters

 • (00:00) Opening 
 • (01:06) Cat's background and the book 
 • (04:40) Defining a software team 
 • (07:02) Building the Developer Success Lab 
 • (10:26) The brains and jars model 
 • (13:14) What the model costs teams 
 • (17:54) Why communicating value is so hard 
 • (19:04) What change looks like in practice 
 • (23:01) Code review anxiety and cycle time research 
 • (27:55) AI's effect on developer identity 
 • (31:57) Agentic coding and cognitive fatigue 
 • (35:46) Threat, play, and psychological safety 
 • (38:19) Working across disciplines 
 • (43:04) What product managers can do 
 • (48:00) Wrap-up

Referenced

The Psychology of Software Teams • by Dr Cat Hicks
The Programmer's Brain • by Felienne Hermans
The Psychology of Computer Programming • by Gerald Weinberg
 • Developer Success Lab (Pluralsight)
DORA projectCatharsis • — Dr Cat Hicks's consultancy
Fight for the Human • — Dr Cat Hicks's newsletter
Dr Cat HicksLearning Opportunities Claude skill • — by Dr Cat Hicks
Deliberate practice and chess improvement study • (44,000 Chess.com players)

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Our Hosts
Lily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She’s currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. 

Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury’s. He participated in Silicon Valley Product Group’s Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He’s the author of What Do We Do Now? A Product Manager’s Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon’s music stores in the US & UK.

What your developers aren't telling you - Cat Hicks (Psychologist)

Faith Forster has spent 15 years in product leadership. She was VP of product at Dex, acquired for approximately $600 million, and went on to serve as CPO at Legal, a payments and compliance platform. She now runs discovery.com, an AI-native platform that helps product leaders and teams make faster, better product decisions by connecting to their tools and synthesising competitor, customer and growth intelligence. She is also the driving force behind the Makers Manifesto — a cross-disciplinary set of values and principles for building great products in the age of AI, developed with 45 contributors from across product, engineering, design, and business leadership.

We discuss:

 1. The manifesto emerged from 96 conversations with product leaders whose grasp of AI ranged from fully automated pipelines to treating it as a faster way to write PRDs — a gap that revealed an industry in urgent need of a shared reference point.
 2. Four values anchor the manifesto: purpose over possibility, value created over effort spent, learning loops over launch plans, and human accountability over full automation.
 3. "Maker" was chosen over "builder" to signal that designers, engineers, salespeople, customer support staff, and founders all share equal ownership of the creation process — regardless of job title.
 4. Feature parity is no longer a defensible moat: when any competitor can replicate a capability within days, durable advantage must come from data, relationships, distribution, and business model.
 5. Product market fit can no longer be treated as a static milestone — in a market where products, competitors, and customer expectations shift simultaneously, fit must become a continuous, living part of decision-making.
 6. "Done" now means adopted, not shipped. AI removes every excuse for clunky, one-size-fits-all experiences, and teams that still equate production deployment with completion are measuring the wrong thing.
 7. Making context explicit — codifying strategy in a form that agents and humans can both act on daily — is the principle teams consistently identify as their most urgent, immediate priority.

Chapters

 • 00:00 Introduction 
 • 01:12 Faith's background 
 • 02:28 Origins of the Makers Manifesto 
 • 06:18 Makers Manifesto vs the Agile Manifesto 
 • 07:23 Why "maker" not "builder" 
 • 11:42 Four values and 16 principles 
 • 15:01 Purpose over possibility 
 • 19:10 Learning loops over launch plans 
 • 22:36 Who gets to be a maker 
 • 28:55 Durable advantage in the AI era 
 • 33:22 Staying close to customers 
 • 36:04 What's next for the manifesto 
 • 43:59 Wrap-up

Referenced

 • Makers Manifesto — 
https://makersmanifesto.org • discovery.com — Faith's AI-native product decision platform

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Our Hosts
Lily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She’s currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. 

Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury’s. He participated in Silicon Valley Product Group’s Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He’s the author of What Do We Do Now? A Product Manager’s Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon’s music stores in the US & UK.

The new manifesto for product builders - Faith Forster (Chief Product Officer)

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Our Hosts
Lily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She’s currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. 

Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury’s. He participated in Silicon Valley Product Group’s Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He’s the author of What Do We Do Now? A Product Manager’s Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon’s music stores in the US & UK.

5 human signals AI won't replicate - Sarah McDevitt (Hubspot)

What product teams get wrong about trust- Simonetta Batteiger (Product Leadership Coach)

We've all heard about the Jobs to Be Done framework - but do you know how to really make the most of it? We went straight to the source - Bob Moesta, who developed the approach alongside Harvard Business School's Clayton Christensen - to really get into the approach.

In this episode, we cover:

 • How to get started with JTBD - and what to do after you've conducted a bunch of interviews.
 • Case studies, including SAAS, candy bars, and selling houses.
 • When not to use the approach
 • And the mistakes that most people make.

Featured Links: Follow Bob on LinkedIn | The Re-Wired Group | Jobs To Be Done website | Buy the'Never Split The Difference' book by Chris Voss and Tahl Raz | Buy the 'Job Moves' book by Ethan Bernstein, Michael B. Horn and Bob Moesta

We're refreshing The Product Experience and want your input. Take our two-minute survey and help shape where the show goes next! 

Our Hosts
Lily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She’s currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. 

Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury’s. He participated in Silicon Valley Product Group’s Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He’s the author of What Do We Do Now? A Product Manager’s Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon’s music stores in the US & UK.

Getting real with jobs to be done – Bob Moesta (President, CEO, The ReWired Group)

Lyt når som helst, hvor som helst

Other podcasts you might like ...