Podcast

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

August 26, 2026/4 min read

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.

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