Building a High-Ownership Engineering Culture with Matt Watson

Key takeaways

High-ownership cultures foster better communication and accountability among engineering teams.
Collaboration between product and engineering enables teams to share ownership of the product vision.
Empathy for customers is crucial for engineers to create valuable products that address real pain points.
Measuring success should focus on customer satisfaction and outcomes rather than just code quantity.
The five foundations of a product-driven mindset are vision, focus, clarity, shared ownership, and courage.

Summary

Creating High-Ownership Engineering Cultures

The podcast opens with a discussion about the common challenge faced by engineering teams in large companies: being in execution mode and not contributing to the product's vision. Matt Watson emphasizes that for engineers to genuinely contribute, they need to feel safe, trusted, and know that their work matters. High-ownership cultures allow engineers to propose ideas, challenge assumptions, and feel a sense of ownership in what they're building, ultimately leading to better results.

Chief Product Officer and Engineering Collaboration

Watson discusses the importance of collaboration between product and engineering teams. He believes that big companies often have a disconnect between these departments, leading to engineers feeling like mere 'order takers'. For successful interaction, product managers must provide clarity around goals but allow engineers to have a say in how to achieve them. This shared ownership creates a stronger commitment and accountability within the teams.

Empathy in Engineering

A critical theme expressed is the need for empathy in engineering work. Watson advocates for engineers to understand the end users of their products. By gaining insights into customer experiences and pain points, engineers can create more valuable solutions. Techniques such as user shadowing and feedback loops are emphasized as methods to foster empathy and a customer-focused mindset.

The Balance of Metrics and Outcomes

Another pressing topic is the difference between code shipped and the value delivered to customers. Many organizations fall into the trap of measuring success through lines of code or speed of deployment rather than actual customer satisfaction and product outcomes. Watson argues that aligning metrics with customer success is essential for determining a product's effectiveness.

Key Foundations for Product-Driven Engineering

Watson introduces the five foundations outlined in his book 'Product Driven': vision, focus, clarity, shared ownership, and courage. He explains that each foundation supports a healthy engineering culture. The most crucial aspect, he concludes, is courage, which is necessary for teams to voice their ideas and push back against less effective processes, enhancing overall productivity and morale.

Show notes

If you’ve ever felt like engineering teams are stuck in execution mode—heads down, building what they’re told—then today’s episode is for you. We're talking about what it really takes to build high ownership engineering cultures where devs aren't simply just shipping code, but they're helping shape the product.

And our guest this week is Matt Watson. He's a long time founder, engineer, and now the CEO of Full Scale, a company that helps startups and scale ups, grow their engineering teams with top talent from the Philippines. Matt's also the author of a book called Product Driven that shows how engineers can build with more clarity, purpose, customer focus and we get into some of the details in that book during this podcast.

So in this episode, we get into everything from the downsides of specialization to the importance of empathy, to why code shipped isn't the same as value delivered. We hope you enjoy it.