Escaping the Build Trap

Melissa Perri, a product management consultant, argues that organizations fail to create real value when they measure success by the volume of features shipped rather than by the outcomes those features produce. She calls this condition—measuring success by features shipped rather than by customer outcomes—"the build trap" and structures her argument around four interconnected components needed to escape it: the product manager role, strategy, process, and organizational culture. Throughout the book, she illustrates these concepts with Marquetly, a fictional online education company for marketers whose struggles are composites drawn from her real consulting work.

Marquetly's CEO, Chris, hires Perri to train the company's product managers, most of whom are former marketers with no product experience. Perri identifies deeper problems: Leadership is not aligned on priorities, the company is pursuing too many simultaneous projects with junior staff, and bonuses reward shipping features rather than solving customer problems. When leadership pressures teams to ship faster, they rush out 10 features in a single month. The site breaks, teachers pull their courses, and students ignore the new functionality. Perri diagnoses Marquetly as stuck in the build trap and tells Chris the company must become "product-led," organizing around products and business outcomes instead of feature shipping, by changing its structure, strategy, processes, and policies. She cites Kodak's failure to respond to digital photography disruption and Microsoft's strategic realignment under CEO Satya Nadella as real-world parallels.

Perri grounds her argument in a value exchange: Customers have problems, businesses create products to address them, and value flows back only when those problems are solved. When companies do not understand their customers, they substitute features shipped as a proxy for value. Perri distinguishes between outputs (features, releases, and velocity, or the rate at which teams complete work) and outcomes (the results of solving customer problems), and between projects (discrete work with deadlines), products (vehicles that deliver value repeatedly), and services (value delivered through human labor). She argues that a project-only mentality is damaging because products require ongoing iteration. She then contrasts sales-led, visionary-led, and technology-led organizations, each of which risks the build trap, with product-led companies that align strategy to business outcomes and prioritize work accordingly.

Turning to the product manager role, Perri identifies three archetypes of ineffective product managers. The Mini-CEO dictates solutions and alienates the team, illustrated by Nick at Marquetly, a business school graduate who learns to collaborate only after coaching. The Waiter takes orders without investigating problems, trapping teams in what consultant David Bland calls the "product death cycle," a loop in which teams perpetually ask customers what features are missing, build them, and still find no one using the product. The Former Project Manager focuses on deadlines rather than on why something should be built. To show what effective product management looks like, Perri introduces Meghan, a product manager at a retail bank working to reduce the 60% abandonment rate among first-time mortgage applicants. Meghan discovers that applicants leave because in-person document verification is too hard to schedule, runs a concierge experiment—manually handling document verification for a small group of applicants to test the concept—with emailed documents, and finds completions increase by 90%. Perri outlines the product manager career path from associate through chief product officer (CPO), noting that responsibilities shift from tactical execution to strategic direction, and argues the industry needs standardized career paths to develop scarce senior talent.

On team structure, Perri recommends organizing around value streams, the full set of activities needed to deliver value to customers, rather than around technical components. At Marquetly, a team permanently assigned to a login API, the software interface handling user authentication, creates unnecessary work on an already-optimized component. Perri proposes restructuring under a new CPO, Jen, with VPs overseeing the student experience and teacher platform and product managers aligned to meaningful feature sets.

Perri uses Netflix's evolution from DVDs to streaming as her primary strategy case study. Netflix developed Project Griffin, an internet-connected TV device, but CEO Reed Hastings killed the project days before its 2007 launch because entering hardware conflicted with the company's core vision. Netflix spun off the device as Roku, partnered with Microsoft for Xbox, and achieved its streaming goals. Drawing on Stephen Bungay's The Art of Action, Perri defines strategy as a deployable decision-making framework rather than a detailed plan. She identifies three strategic gaps: the Knowledge Gap (demanding detail instead of communicating intent), the Alignment Gap (prescribing solutions instead of letting teams determine how), and the Effects Gap (adding controls instead of granting freedom to adjust). Perri presents a four-level deployment framework (vision, strategic intent, product initiatives, and options) and introduces the Product Kata, adapted from Toyota's Improvement Kata, as a cycle of understanding direction, analyzing the current state, setting the next goal, and choosing the appropriate process step. At Marquetly, leadership sets two strategic intents: expand into enterprise and double revenue growth from individual users.

The process section follows Marquetly's team as it breaks down its strategic intent. Data analysis reveals that 55% of non-converting visitors want more course variety, and 90% of churned users, those who stopped using the product, left because they exhausted the available content. Investigation uncovers that most teachers have created only one course. Through user research, product manager Christa's team initially attributes the problem to a clunky upload workflow. However, a concierge test in which the team manually uploads content for teachers reveals a deeper issue: Teachers send unedited video with editing instructions, spending upward of 80 hours on production. A survey confirms that 90% of teachers identify video editing as their biggest obstacle. The team runs another concierge experiment, having Marquetly's marketing video editors handle editing for 14 teachers; 12 publish their courses within three weeks. Perri explains additional experimentation types, including Wizard of Oz experiments, which appear finished to users but are manual on the backend, and concept testing, which pitches ideas through prototypes or videos, as Dropbox did to secure funding.

With demand validated, VP of product Karen proposes acquiring a Budapest-based video-editing software company rather than building functionality in-house. After the acquisition, the team integrates the technology, tests prototypes with teachers, and launches a first version. Adoption reaches 60%, below the 75% target, but adopters achieve a 75% publish rate, exceeding the goal. The team iterates until all targets are met.

In the final section, Perri addresses the organizational changes needed to sustain product-led practices. She recounts her 2007 experience on a Cornell University innovation team that identified demand for phone-integrated cameras and photo editing at Kodak, which could not act because its siloed lab and rigid budgeting blocked execution; the company filed for bankruptcy in 2012. Perri recommends outcome-focused communication through structured review cadences and "Living Roadmaps" that convey strategy rather than fixed delivery dates. Rewards must also change: She describes a company whose employees shipped low-quality features every December to earn bonuses, then spent January fixing the code. Budgeting, she argues, should follow a venture-capital model, funding teams incrementally based on validated learning. On safety, Perri cites Netflix's rapid recovery from Qwikster, its aborted 2011 plan to split off the DVD business, as evidence that organizations survive public failures when they return to core strategy. She presents customer centricity as essential, citing Amazon's obsessive focus on customers and John Deere's practice of sending engineers and product managers to a working farm to understand users firsthand.

Marquetly's transformation takes several years. The company replaces annual budgeting with rolling, investment-minded funding, kills many ideas early, and focuses on validated initiatives that drive growth, ultimately achieving its strategic intents and being acquired by a larger educational company. CEO Chris models the change personally, CPO Jen and VP Karen build a senior product team, and product manager Christa rises to VP of product at the acquiring company. Perri closes with six diagnostic questions, including who originates feature ideas, what products have been killed, how recently teams talked to customers, and whether product managers are empowered or merely taking orders.