Silicon Valley Product Group's latest essay, "Great Products, Bad Companies," opens with a blunt reversal of the firm's long-held position: great products power great companies, but they no longer guarantee them.

Why is SVPG walking back the "great product" doctrine?

The post, published on svpg.com, opens by restating SVPG's founding argument that product excellence drives company success. The author walks it back in the second paragraph. "I have long argued that great products are what powers great companies," the post begins. "And while I still believe that great products are necessary for great companies, it's become quite clear over the years that great products are not sufficient."

That pivot — necessary but not sufficient — is the spine of the piece. The truncated preview ends mid-sentence: "I have seen too many examples where great products can..." The full post on svpg.com lays out the rest of the argument and the failure modes the author has watched repeat across companies.

What conditions make the "great product" thesis fail?

The framing of the opening paragraphs implies a specific set of conditions the essay is built to explore: companies shipping beloved, well-designed products that still underperform on the dimensions that actually matter to the business — revenue durability, customer retention, operating discipline, and capital efficiency.

For practicing product managers, the argument lands on a tension most senior PMs recognize immediately. A team can ship a product that customers love, that wins design awards, that hits every engineering OKR — and still watch the parent company fail because of pricing, distribution model, or organizational design made outside the product team's reach.

The essay draws a line between product success (customers choose and use it) and company success (the business compounds). The author argues the two have decoupled in enough cases to break the original equation.

What does the post imply for Monday morning?

The structure — restating a thesis, then qualifying it with observed counterexamples — points to three practical adjustments for product teams.

• Pull the boundary of accountability wider. If great products aren't sufficient on their own, the product team needs a seat at the table for pricing, GTM motion, and operating cadence — not only for discovery and delivery.
• Define "great" against company outcomes, not just customer outcomes. Customer love without revenue durability isn't a great product; it's a tolerated one.
• Treat product-market fit as a starting condition, not a strategy. PMs should pressure-test whether the fit they have compounds, or whether the company is consuming capital faster than the product creates value.

Why does SVPG's voice matter here?

SVPG is the consultancy behind the product-management book series Inspired, Empowered, and Transformed — titles that have shaped how product teams structure discovery, delivery, and operating models over many years. A piece walking back the firm's founding line carries weight precisely because it speaks from inside the playbook the essay is now revising.

That makes the post a directional signal, not a rant. The argument comes from the same body of product thought that popularized the empowered-team model. When that school says the model needs an update, product organizations should at least read it carefully.

Where does this leave product practice?

The essay lands at a moment when several high-profile product-led companies have stumbled despite widely admired products — a pattern that has sharpened the question of what product teams actually own. SVPG's revised thesis pushes that conversation forward: product managers should expect the bar to rise from shipping well-loved software to co-owning the conditions under which that software compounds into a durable company. The trade-off the essay surfaces is real: scope expands, accountability widens, and the line between product work and company work stops being a clean handoff.