Discovery vs. Delivery
Cagan argues that product teams face two simultaneous goals: learning fast through discovery about what customers need, and delivering robust, scalable, production-quality software they can release with confidence…
Founder of Silicon Valley Product Group (SVPG) and author of Inspired, Empowered and Transformed.
Cagan argues that product teams face two simultaneous goals: learning fast through discovery about what customers need, and delivering robust, scalable, production-quality software they can release with confidence…
Marty Cagan answers the most common questions readers raised after his article proposing an alternative to conventional product roadmaps. He argues that engineers should help decide what to build, that outcome-based…
Cagan argues that feature-list roadmaps often tell teams what to build without explaining the underlying problem, producing waste. He proposes replacing them with shared context: a product vision describing the…
Marty Cagan, a longtime admirer of Apple, argues that the first Apple Watch after Steve Jobs is a disappointing product that falls short of Apple's usual standards of value. He criticizes its dependence on the phone…
Marty Cagan argues that leadership and management are distinct, both essential competencies that many people wrongly conflate. He draws on an excerpt from Marty Abbott and Michael Fisher's The Art of Scalability to…
Marty Cagan argues that the common company process of taking executive or stakeholder ideas, building business cases, prioritizing feature roadmaps, and handing requirements down a line from product to design to…
Marty Cagan examines how product organizations tackle large, multi-team initiatives, such as a usability redesign or a localization push into a new market, that cannot be owned by a single team. He argues that the core…
Cagan extends his series on product team autonomy by examining how code ownership interacts with it. When companies split a codebase among product teams, one team's changes often touch code another team owns, creating…
Cagan argues that team autonomy and leadership control are reconciled when leaders supply two inputs: a clear product vision and specific, prioritized business objectives for each team. Teams should then have freedom…
Marty Cagan argues that while empowered, cross-functional product teams have become the norm and boost motivation and ownership, teams often feel constrained by shared foundations. He frames the core tension as a…
Marty Cagan argues that product teams can find major opportunities by letting customers use their products for purposes the company never planned or officially supports. He describes this as a third path beyond…
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 responds to readers stuck in IT-mindset organizations who ask whether they can change their company or must leave for a startup. He argues that established companies can still produce disruptive innovation…
Marty Cagan argues that established companies often lose their capacity for continuous innovation, and that a deeper root cause than the usual focus on scale and execution is an "IT mindset" applied to product work. He…
Marty Cagan argues that UX designers often work in isolation, going off for days or weeks to produce a polished 'grand reveal,' a pattern he calls the 'internal agency model.' This breaks down because requirements and…
Marty Cagan addresses a recurring question from company leaders: should product managers carry P&L responsibility? He traces the idea to consumer packaged goods, where a product manager owned costs, marketing, forecasts…
Marty Cagan argues that the project management role, in its many forms, is often poorly performed and sometimes seen as a liability, and that its damaged brand may need a fresh start. He attributes the problems to…
Marty Cagan contrasts strong product teams with weak ones, drawing on years of working with both top technology companies and struggling ones. He argues the differences are not minor but span leadership behavior, team…
Marty Cagan argues that milestone swarming, where most or all of a dedicated product team (or a virtual team drawn from several teams for an initiative) focuses together on one significant business milestone, can speed…
Marty Cagan argues that many product teams grind through backlog stories without understanding the customer pain or business impact behind them, and that this is worsened by Kanban-style continuous delivery…
Marty Cagan argues that product teams often fixate on a single kind of analytics, usually web analytics, and miss the larger picture. He lays out four flavors that matter for product work: user analytics on how real…
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 analytics has become a core competency for product leaders, driven by larger data volumes, better tools, and a growing belief that data can speed up learning. He identifies five uses of analytics…
Marty Cagan argues that a startup's central goal is reaching Product-Market Fit, the point where a product has proven demand and justifies investing in sales, marketing and scale. He standardizes on Marc Andreessen's…
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 teams should design for specific personas rather than vague generic users. Using eBay seller tools as an example, he sketches three detailed fictional people with different backgrounds…
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 product teams should stop framing their work as gathering and documenting requirements, since most so-called requirements are really constraints. He proposes defining products along two…
Marty Cagan argues that the biggest risk facing most startups and new products is not market risk or business-model risk but solution risk: whether the team can find an approach customers actually choose to buy and use…
Cagan argues that strong products are the foundation of a healthy business: weak products inflate acquisition costs, lengthen sales cycles, pressure prices and burden customer service. The most powerful antidote is a…