Product Driven

🔍 Understanding Product Thinking: A Software Engineer's GuideJoin Matt Watson and Nax as they explore why engineers need to embrace product thinking beyond just writing code. Discover how understanding user needs and business goals leads to better technical decisions and more impactful solutions.🎓 Whether you're a seasoned developer or just starting your engineering journey, this discussion offers valuable insights into elevating your impact through product-focused development.🔗 Essential Links (Start Here!):Full Episodes: https://product-driven.captivate.fm/episodesConnect with Matt Watson on LinkedIn: https://www.linkedin.com/in/mattwatsonkc/Subscribe to our Newsletter: https://newsletter.productdriven.com/Powered by Full Scale: https://fullscale.io/Key Discussion Points:Why users care about outcomes, not codeThe importance of product mindset in engineering decisionsPractical steps for developing product-focused thinkingThe role of product thinking in the age of AIChapters:00:00 - Introduction & Why Product Thinking Matters00:32 - Code vs. Product: What Users Really Care About01:31 - Defining Product Thinking for Engineers02:38 - Common Challenges in Developer Mindset03:51 - Tips for Developing Product Ownership05:28 - Overcoming Development Challenges06:46 - Actionable Steps for Engineers08:13 - Product Thinking in the AI Era09:11 - Closing Thought

In this episode of Product Driven, Matt Watson discusses the differences between outsourcing projects and building dedicated teams, particularly in the context of software development. He explores the pros and cons of both approaches, emphasizing the importance of understanding when to use project-based work versus staff augmentation. Matt shares insights from his extensive experience in the tech industry, highlighting the benefits of hiring global talent and the challenges of managing remote teams. He advocates for staff augmentation as a more effective strategy for companies looking to build long-term, dedicated teams that integrate seamlessly into their business processes.TakeawaysOutsourcing can be a cost-effective way to access global talent.Project-based work is suitable for short-term, defined tasks.Staff augmentation allows for building a dedicated team that works directly for you.Quality of talent is crucial in software development.Effective communication skills are essential for remote developers.Having a fractional CTO can enhance project success.Long-term partnerships with development agencies can lead to better outcomes.Understanding the local culture is important when hiring globally.Project-based developers may not always be the best fit for long-term needs.Agencies can provide better resources for employee growth and retention.Find Product Driven Everywhere:https://product-driven.captivate.fm/episodesThis episode is sponsored by Full Scale:https://fullscale.io/Sign up for the Product Driven newsletter:https://newsletter.productdriven.com/Chapters00:00 Outsourcing vs. Dedicated Teams08:07 Understanding Staff Augmentation18:05 Benefits of Working with a Development Agency

In this episode, Matt Watson and Tommy Forstrom discuss the dynamics between engineering and product teams, exploring the friction that often exists due to misaligned incentives and communication gaps. They emphasize the importance of collaboration and understanding between these teams to create a cohesive product development environment. The conversation also delves into the roles of CTOs and CPOs, highlighting the need for product-minded leadership in tech companies. Ultimately, they stress the necessity of fostering a culture where developers are engaged in the product process, leading to better outcomes for both the team and the customers.TakeawaysMisaligned incentives often create friction between engineering and product teams.Developers should be involved in the product planning process.Customer focus is essential for both engineering and product teams.Leadership alignment is crucial for reducing tension between teams.A single executive overseeing product and engineering can improve collaboration.Healthy tension is often a euphemism for deeper issues within teams.Developers need to understand the business context of their work.The role of CTO should evolve to include product leadership.CPOs and CTOs can coexist but should have clear responsibilities.Creating a cohesive team culture starts from the top.Sound Bites"It's not a linear journey.""We have to set the tone from the top down.""We need owners, we need people to own things."Chapters00:00 Engineering Teams vs. Product Teams21:47 The Role of CTO vs. CPO30:12 Building a Cohesive Team Culture

In this conversation, Matt Watson and Greg Head discuss the challenges faced by SaaS founders, the importance of product development, and the realities of VC funding. Greg shares insights from his experience with Practical Founders, emphasizing the need for a strong product and the potential for success without relying on venture capital. The discussion covers the genesis of SaaS companies, the role of technical co-founders, and the significance of product leadership in driving growth and customer retention.TakeawaysPractical Founders help SaaS entrepreneurs build valuable companies without VC funding.Industry experience often serves as an unfair advantage for founders.Product development is not just about coding; it's about understanding customer needs.Many founders struggle with translating their vision into a tangible product.The importance of having a technical co-founder varies among startups.Product leadership is crucial for the success of a SaaS company.Transitioning from zero to revenue involves understanding product-market fit.Quality of the product directly impacts customer retention and referrals.VC funding is not always necessary for growth; many successful companies bootstrap.The landscape for exits has shifted, with private equity becoming a significant player.Find Product Driven Everywhere:https://product-driven.captivate.fm/episodesThis episode is sponsored by Full Scale:https://fullscale.io/Sign up for the Product Driven newsletter:https://newsletter.productdriven.com/Sound Bites"Practical founders create valuable software companies without VC funding.""It's figuring out what is so darn valuable.""You can't outrun churn with VC funding."Chapters00:00 Introduction to Practical Founders and SaaS Challenges03:02 The Genesis of SaaS Companies06:12 Navigating Product Development Challenges09:10 The Role of Technical Co-Founders12:09 The Importance of Product Leadership15:01 Transitioning from Zero to Revenue17:54 The Impact of Product Quality on Growth21:05 Understanding the VC Landscape23:53 When to Consider VC Funding27:12 The Reality of Exits and Success in SaaS29:54 Conclusion and Resources for Founders

In this conversation, Matt Watson discusses the critical roles of the Chief Technology Officer (CTO) and Chief Product Officer (CPO) in startups, emphasizing the importance of product vision in SaaS companies. He argues that the CTO should ideally also take on the responsibilities of the CPO, focusing on product needs rather than just technology. Watson highlights common mistakes startups make, such as neglecting customer feedback and product validation, and advocates for a shift toward hiring executives with a strong product mindset.TakeawaysStartups need to prioritize product vision over technology.The roles of CTO and CPO can overlap in small companies.A strong product mindset is crucial for success in SaaS.Many startups fail to validate their product with customers.The CTO should focus on how technology serves product needs.Hiring a CPO with an engineering background can enhance product development.Product vision should align with the overall company vision.Effective communication of product requirements is essential for developers.Startups should avoid creating a 'feature factory' mentality.Understanding the 'why' behind product development is key.Find Product Driven Everywhere:https://product-driven.captivate.fm/episodesThis episode is sponsored by Full Scale:https://fullscale.io/Sign up for the Product Driven newsletter:https://newsletter.productdriven.com/Sound Bites"I care about the product."Chapters00:00 The Role of CTO vs. CPO in Startups02:45 Product Vision and Its Importance in SaaS05:11 The Shift Towards Chief Product Officers

In this episode of Product Driven, Matt Watson speaks with Jay Eigner, founder and CEO of JDA QA, about the critical role of Quality Assurance (QA) in software development. They discuss how developers can contribute to testing, the importance of collaboration between QA and development teams, and the need for QA to be embedded within product teams. The conversation also covers strategies for prioritizing testing, identifying what to test, and the enduring necessity of manual testing in an increasingly automated landscape.TakeawaysQA is essential for building better products.Developers have unique insights into testing their own code.Collaboration between QA and developers enhances product quality.QA should be involved early in the development process.Understanding user functionality is key to effective testing.Many organizations waste time testing unnecessary features.Manual testing will always have a place in QA.Exploratory testing helps uncover hidden issues.Automation tools assist but cannot replace human insight.Effective communication and curiosity drive better outcomes.Find Product Driven Everywhere:https://product-driven.captivate.fm/episodesThis episode is sponsored by Full Scale:https://fullscale.io/Sign up for the Product Driven newsletter:https://newsletter.productdriven.com/Chapters00:00 Introduction to QA and Product Development02:43 The Role of Developers in Testing05:12 The Importance of QA in the Development Process07:45 Embedding QA in Product Teams12:27 Prioritizing Testing in Software Development15:10 Avoiding Wasted Testing Efforts17:07 The Future of Manual Testing

In this conversation, Matt and Ryann discuss the evolution of the Product Driven initiative at Full Scale, emphasizing the importance of bridging the gap between software development and business needs. They explore the necessity of empowering teams, adapting brand strategies to market demands, and creating unique content that addresses the challenges faced by startups and established companies alike. The discussion highlights the significance of understanding the purpose behind product development and the need for cohesive communication within teams.TakeawaysProduct Driven represents an evolution from just building software to a more holistic approach.There is a significant gap between technical skills and business understanding in tech companies.Empowering developers with knowledge about the product leads to better decision-making.Brand evolution is essential as businesses grow and their audiences change.Identifying opportunities versus distractions is crucial for founders.Creating a unique content strategy can differentiate a brand in a crowded market.Team culture and ownership are vital for retaining top talent.High-quality nurturing content is necessary for engaging customers effectively.Understanding the 'why' behind product development enhances team cohesion.The market demands a shift from startup-focused content to broader product-driven insights.Sound Bites"Every company is a software company now.""We need to teach developers to think outside the code.""Is this a distraction or is it an opportunity?"Chapters00:00 The Evolution of Product Driven03:02 Bridging the Gap: Developers and Business Needs06:00 Empowering Teams for Better Product Development09:14 Brand Evolution: Adapting to Market Needs12:01 Identifying Opportunities vs. Distractions14:59 Creating Unique Content in a Crowded Space

In this episode of the Product Driven podcast, host Matt Watson is joined by Nax, the VP of Engineering at Full Scale, to discuss one of the most significant challenges developers face—focusing too much on code and not enough on the product. The conversation highlights key insights on bridging the gap between product development and engineering to create better outcomes for developers and users.Key Takeaways:Ask the Right QuestionsDevelopers must move beyond just coding and start asking broader questions. Understanding why something is being built, rather than just what, helps reduce surprises and deliver a better product. Nax emphasizes the importance of validating assumptions early on to avoid unnecessary rework.Talk to Users and CustomersDevelopers need to have more empathy for users. Watching users interact with a product or reviewing support tickets can help engineers understand pain points. This connection improves the quality of the software and makes the development process more user-centric.Get Involved in Product PlanningEarly involvement in product planning helps developers grasp the bigger picture. Instead of just following the requirements, developers should understand the goals and expectations to build more scalable and user-friendly products.Take OwnershipOwnership means seeing projects through to the end, not just finishing the coding aspect. Developers should take pride in monitoring, testing, and ensuring their code works in production, which leads to a better overall product experience.Focus on the Product, Not Just the CodeIt’s crucial for developers to think from a product usability standpoint, rather than focusing solely on technical aspects. Nax shares examples where focusing only on the code resulted in less user-friendly products.Simpler Code is BetterWhile complexity can sometimes seem like the mark of a skilled developer, simpler code leads to fewer bugs, easier maintenance, and happier teams. Matt and Nax emphasize the importance of keeping things simple unless complexity is required for performance or security reasons.Additional Resources:Watch Matt’s previous episode with Chris Atkinson on the importance of teaching developers the big picture here: https://youtu.be/Fi2WRkQTFdgQuotes:Nax: "Simpler code means fewer bugs, easier updates, and happier engineers."Matt Watson: "It’s not done until it’s in production and the user loves it."Stay tuned for more insightful discussions on aligning product development with engineering. Thanks for listening!

In this conversation, Matt Watson discusses the concept of 'founder mode,' a state of being that many entrepreneurs experience, characterized by a hands-on approach and rapid decision-making. He shares his personal experiences and challenges faced while operating in this mode, including difficulties in delegation, micromanagement, and the need for structured processes. Watson emphasizes the importance of balancing founder mode with effective team dynamics to avoid burnout and ensure company growth.TakeawaysFounder mode is essential for early-stage startups.Extreme ownership is crucial for founders.Delegation is a significant challenge for many founders.Micromanagement can frustrate team members.Structured processes are often overlooked by founders.Feedback from the team is vital for growth.Burnout is a risk if founders don't delegate.Having a COO can help balance founder mode.Companies can move faster with a founder mindset.Understanding weaknesses in founder mode is key to success.Chapters00:00 Understanding Founder Mode03:11 The Challenges of Founder Mode06:00 Balancing Founder Mode with Team Dynamics

In this conversation, Matt Watson and Chris Atkinson, CTO of eHawk discuss the importance of bridging the gap between engineering and business understanding in software development. They explore how engineers often focus too much on coding and not enough on the bigger picture, which includes understanding user needs and the business context. Chris shares practical strategies for training engineers to think more like product managers, emphasizing the need for empathy towards users and the impact of leadership in fostering this mindset. The discussion highlights the value of innovation sprints and direct engagement with users to enhance product development and improve team dynamics.TakeawaysEngineers often struggle with understanding the big picture.Bridging the gap between business and technical sides is crucial.Training engineers on product value enhances their creativity.Empathy for users is essential for effective software development.Innovation sprints encourage engineers to think about customer needs.Recording client conversations helps engineers understand user pain points.Involving engineers in support conversations improves their perspective.Leadership plays a key role in fostering a user-centric mindset.Understanding the 'why' behind coding tasks increases job satisfaction.Empathy leads to better questions and higher quality software.Sound Bites"Engineers struggle with the big picture.""Everyone in my organization is in product.""It's all about the why."Chapters00:00 Bridging the Gap: Engineering and Business Understanding05:37 Training Engineers for the Big Picture09:22 Empathy in Engineering: Understanding User Needs13:03 The Impact of Training on Productivity and Creativity17:17 Leadership's Role in Fostering Empathy and Understanding