Key Questions
- What is a good way to approach product management at a startup?
- Should the founder continue to lead the product or give responsibility to a product manager?
- What does a product manager do?
- What are the key functions within product management?
- When is it helpful to formalize product management and build a product team?
- Should engineering lead product management?
Start Here
Leigh Braswell: Product Management at a Startup 101
(17 min read.) Leigh discusses the evolution from early-stage product development to hiring PMs, common mistakes, and scaling product teams. Braswell emphasizes the importance of clear communication, customer focus, and adaptable processes. She shares insights from her experience at Scale and working with portfolio companies, offering practical advice for building successful product-driven cultures.
Kyle Poyar: The Pre-PMF Guide to Product Management
(8 min read.) Poyar’s article outlines six key principles for early-stage startups to accelerate their path to product-market fit (PMF). He emphasizes unlearning traditional practices, starting with a well-defined MVP, prioritizing tasks effectively, moving quickly, setting achievable milestones, and consistently collecting learnings. Traditional product management approaches often slow down startups; instead, founders should focus on rapid delivery, direct problem-solving, and adapting based on real-time feedback. According to Poyar, by following these principles, startups can increase their chances of achieving PMF faster, as demonstrated by the success of companies like June, Notion, and Uber.
Learn More
Marty Cagan: Product vs Feature Teams
(8 min read.) Marty offers his take on two types of product teams, discussing the differences between what he calls empowered product teams (whose purpose is to solve problems in ways customers love yet work for the business) and feature teams (whose purpose is to serve the business). He states that while they look very similar on the surface, they differ dramatically in the way they operate, the level of empowerment and accountability, and the responsibilities of the product manager. Cagan also offers a practical list of questions that can help a team member determine which type of team they are on.
Marty Cagan: Empowered – Achieving Extraordinary Results With Ordinary People
(48 min video.) Marty explains how companies can build empowered product teams and what differentiates the best from the rest. He goes over the reasons why most companies lack a true product mindset, the role of leadership in fostering a product culture and inspiring people, the importance of consistently innovating on behalf of customers (as Amazon, Apple, and Google do), the basis of trust, and the main responsibilities of management (staffing, coaching, and setting objectives). The key point Marty makes is that putting people in the right environment enables them to do amazing things.
Roman Pichler: Scaling the Product Owner Role
(4 min read.) Roman argues that scaling the product owner role involves adapting strategies based on a product’s life cycle. For young products, a single product owner is preferred for efficient decision-making. As the product grows, responsibilities can be divided among feature and component owners. Unbundling features into separate products or creating variants can also distribute workload. Another approach is splitting strategic and tactical roles, although this should be used carefully to maintain integration. Roman concludes that these strategies help manage complex products effectively while avoiding decision-making by committee and ensuring consistent product development.
Marty Cagan: Product Management Theater
(125 min video.) Marty discusses the common pitfalls in product management where activities give the appearance of progress but don’t actually contribute to meaningful outcomes. He criticizes practices like excessive focus on processes, documentation, and superficial engagement with customer feedback, which he terms as “theater.” He advocates for a more genuine approach to product management, emphasizing the importance of truly understanding and addressing customer needs, iterating on product ideas based on real feedback, and fostering a culture of continuous learning and improvement.
Ben Horowitz: Good Group Project Manager / Dead Group Project Manager
(9 min read.) Horowitz highlights the critical role of the Group Product Manager (GPM) in a software company. He emphasizes that a GPM’s success is vital, as it can make or break a company. He outlines key principles distinguishing successful GPMs from unsuccessful ones, stressing the importance of taking full responsibility, managing effectively, prioritizing rigorously, and maintaining clarity in communication. He advises GPMs to remain hands-on, ensure strategic alignment, and be paranoid about potential risks. The ability to navigate organizational dynamics and engage effectively with executives is also crucial for a GPM’s success.
Casey Winters: Product Visionary vs. Product Leader
(3 min read.) Casey explains the difference between two types of product roles: product visionary and product leader. Product visionaries are the creative minds who come up with innovative products, often founders or CEOs. Product leaders, on the other hand, are responsible for executing the vision set by the visionary, driving performance, and scaling the company. He emphasizes that most companies need product leaders rather than visionaries, as founders typically have the vision and need leaders to operationalize it. Aspiring product managers should understand the distinction between these roles and determine which path aligns with their goals.
Shreyas Doshi: Why Products Don’t Succeed: The 7 Biases of Product Teams
(3 min read.) Shreyas identifies seven common biases that product teams often fall victim to, leading to products that lack impact. These biases include focusing on quick execution over long-term strategy, prioritizing building without fully understanding the problem, overvaluing past work, overestimating the importance of a problem when discussing it with customers, relying on familiar frameworks even when they are not optimal, focusing on strategies that align with company leadership’s beliefs, and ignoring potential risks. To combat these biases, He suggests recognizing them, naming them explicitly within teams, and fostering a culture of awareness. The ultimate responsibility lies with product leaders to identify and address these biases throughout their organizations.