Every note in the archive that names Product Discovery: summaries, key takeaways and links to the original essays, episodes and posts. Ask a question below to get a cited answer from just these notes’ authors.
“Note: This is the narrative version of a keynote talk for the Lenny & Friends Summit. Recently I was asked a question that I haven’t been able to get out of my head: “In light of all that has changed, what are the things that you used to argue were true, that you no longer... The post Strong Opinions, Loosely…”
Teresa Torres and Petra Wille examine why hiring processes often fail product teams despite their rigor. They describe how AI-inflated application volumes, longer funnels, and many stakeholders create noise, and how…
Marty Cagan and Bob Baxley argue that in the Generative AI era, strong product managers and product designers become more essential, not less, but only when those roles are defined by their specific, demanding skill…
Marty Cagan lays out the product operating model, in which a product manager sits on a small cross-functional team alongside a designer, a tech lead and engineers, and is accountable for solving customer problems that…
The authors argue that many companies become efficient feature factories: most roadmap features fail to generate a positive return, often estimated at only 10-20%. The root cause is feature teams that serve internal…
Marty Cagan responds to recurring questions about whether SVPG promotes a specific branded process such as 'the INSPIRED process' or 'the EMPOWERED process'. He argues that nearly everything involves some process, and…
Cagan and Moore argue that 'transformation' is often described with labels like Agile or product-led, which fail to capture what actually changes. They propose defining transformation by three concrete shifts: how a…
Marty Cagan argues that the essential nature of technology-powered products is hard to grasp until you've worked on a strong product team, and that most people think they understand it but don't. He highlights a rarely…
Marty Cagan proposes a simple taxonomy for the types of product coaching, since no widely accepted vocabulary exists yet. He distinguishes product-related coaching (delivery, discovery, product leadership, and…
Marty Cagan argues that the MBA pathology, the set of habits instilled by many business programs, continues to produce weak product managers and weak products despite claims that it would self-correct. He stresses he is…
Marty Cagan, who popularized the term product discovery, clarifies a common confusion: learning is valuable, but the real goal of discovery is to gain insights, which are learnings a team can act on. He explains that…
Lea Hickman and Marty Cagan argue that many company transformations to empowered product teams fail because key conditions are missing. They present ten keys, spanning senior leadership support, reframing technology as…
Marty Cagan explains where the term "product discovery" came from and why he chose it. He argues that software has always faced two core problems: figuring out the right product, and then building it right, which he…
Cagan argues that while most team objectives should be aspirational, some situations require high-integrity commitments: deliverables with dates leaders can rely on, driven by trade shows, contracts, tax deadlines…
Marty Cagan revisits Henrik Kniberg's skateboard-versus-car MVP article and argues it describes what engineering-only teams can do, not what true cross-functional product teams should do. He contends that a skilled…
Marty Cagan argues that many teams claiming to be Agile or Lean still operate with a Waterfall mindset, merely adopting the rituals and buzzwords. He identifies three telltale signs: risks deferred to the end…
Marty Cagan argues that a common and avoidable form of waste in product teams is when one member, often a user researcher, learns something important about customers but the rest of the team doesn't absorb it. Findings…
Marty Cagan argues that prototyping is not one thing: teams often narrow the term to whichever prototype type they first encountered, and then misuse it. He lays out four main flavors: feasibility prototypes that answer…
Marty Cagan argues that the largest source of technology waste is not government projects or startups but large non-tech companies such as banks, insurers, airlines and retailers. These firms, often run by CIOs or CFOs…
Marty Cagan argues that product discovery and rapid test-and-learn techniques, which startups use, apply equally to established companies. Startups have no legacy to protect, so they can take big risks cheaply…
Marty Cagan argues that many Agile trainers and coaches who work with software teams lack the experience needed for commercial product companies, and that the poor work he has repeatedly cleaned up after is a persistent…
Marty Cagan argues that product teams relying on long, pre-negotiated roadmaps repeatedly fail to deliver business results because of two unavoidable realities. First, at least half of ideas won't work, whether…
Marty Cagan describes a proposal from Jeff Patton to replace the traditional product roadmap with an "opportunity backlog." The core problem is that roadmap items are often treated as commitments, yet genuine product…
This opening post in a planned series argues that a company can only launch a successful product if it builds something customers actually want, which requires deep knowledge of the customer's need, context, and…
Marty Cagan responds to a debate sparked by Don Norman's essay arguing that big societal innovations are driven by technology first and needs later, which Norman frames against heavy upfront user research. Cagan says…
Marty Cagan reflects on whether product discovery techniques built for software apply to non-technology products. He tested them while writing a book, using customer research, a small group of charter customers…
Cagan argues that product teams need two distinct disciplines: Product Discovery, which uses prototyping and user testing to find new valuable, usable, feasible solutions, and Product Optimization, which improves an…
Marty Cagan examines what business incubators, from independent startup accelerators to corporate labs like HP Labs and Yahoo's Brickhouse, teach about turning product ideas into successful companies or products. He…
Cagan argues that many companies blur business strategy and product strategy, which leaves executives buried in feature-level decisions and product managers without the context or empowerment they need. Business…
Marty Cagan argues that a core failure in product planning is that weak projects, which should be killed during product discovery before reaching engineering, often are not. He identifies seven recurring reasons for…
Marty Cagan argues that product managers who spend their time prioritizing a laundry list of feature requests are working on the wrong problem. A feature-request roadmap pushes unvalidated features into the plan, skips…
Cagan argues that product teams commonly treat requirements and design as a scheduled, sequential phase, which leads to engineers building unvalidated solutions that customers don't want. He reframes this stage as…