What does it take to build truly product-driven engineering teams? In this episode, Matt Watson — founder and CEO of Full Scale and author of Product Driven — joins Lily and Randy to challenge the longstanding silos between product and engineering. Drawing on 25+ years of experience and four tech ventures, Matt makes the case for why developers need more than just code to care about: they need context, ownership, and clarity.
From redefining "done" to the evolving role of AI in software teams, this conversation dives into how product leaders can foster a culture where engineers aren't just implementers, but co-creators of customer value.
Chapters
Key Takeaways
"Ship and forget" is a failure mode. Lack of feedback means missed learning — not success.
Redefine 'done'. It's not when the code is committed; it's when the customer experiences value.
Clarity beats ceremony. Agile rituals mean little without shared context and purpose.
10x is about friction, not genius. The most productive engineers aren't just skilled — they're empowered, trusted, and aligned.
Product-driven teams require courage. From engineers speaking up, to PMs giving up control, psychological safety fuels innovation.
Engineers need to know the why. Without understanding customer impact, even brilliant code becomes meaningless.
AI raises the bar on thinking. Execution is easier — now value creation is what separates teams.
Featured Links
Key Quote
"The only reason any of you have a job is we create a product for our customers. That's why we're here."
