How to build a product-driven engineering team - Matt Watson (Founder, Full Scale)

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.

Featured Links
🔗 Follow Matt Watson on LinkedIn | https://www.linkedin.com/in/mattwatsonkc/
🔗 Full Scale | Software development services | https://fullscale.io/
🔗 Buy the book: Product Driven | https://productdriven.com/

Chapters
0:00 – Why “no feedback” is a warning sign, not success
1:46 – Matt’s journey: from developer to founder
2:58 – Thinking outside the code: how the book Product Driven started
4:50 – Why many engineers don’t think about the customer
5:57 – The rise of product managers and the walling off of engineers
6:56 – Redefining the role of PMs in cross-functional teams
9:01 – Metrics, measurement, and the illusion of progress
10:57 – Ownership as the root of productivity
13:04 – Code monkeys, culture, and killing creativity
14:55 – Communicating context: five minutes that save weeks
17:04 – AI and the changing definition of developer productivity
20:32 – External value vs internal tech debt
22:48 – The Product Driven model: Vision, Focus, Clarity, Shared Ownership, Courage
27:08 – Why courage is the starting point for change
31:09 – The blurred lines of product and engineering
33:03 – What makes a 10x developer?
35:25 – The importance of clarity in the age of AI
36:01 – The four types of engineering leaders
38:22 – How Full Scale hires for curiosity, not just coding skills

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.

This episode is brought to you by Bolt.new
 — the product manager’s secret weapon to prototype and test ideas in hours, not weeks. Build real interactive flows without waiting on design or engineering, reduce guesswork, and keep your product vision intact. Try it now at bolt.new.