Fifteen years after INSPIRED taught a generation of product managers to treat viability as a footnote to feasibility, its author reversed course at the Lenny & Friends Summit, listing ten positions he no longer holds.

The talk, titled "Strong Opinions, Loosely Held," distills learning accumulated after 25 years in product at leading platform and developer-tool companies. "I treat my content as my product, and literally every week I am doing product discovery on my content," the author said. The constraint he set: only count lessons since INSPIRED shipped in 2008.

Why revisit the principles now?

He framed the revisions as a response to AI, not a repudiation of his prior work. He distinguished between frameworks and processes, and by the underlying principles that survive constant change. The real test, he argued, is whether content written 20 or 10 years ago still holds up. AI's economics, he said, make that re-examination unavoidable.

What's missing from the four product risks?

In INSPIRED's first edition, the product risks were value, usability, and feasibility, with viability buried underneath. The second edition, published 10 years later, lifted viability into its own category, but the author acknowledged that "literally hundreds of thousands of product people heard from me this very one-sided view of the product role."

His explanation: nearly all his early career was spent on developer tools and platforms, where weak business skills rarely cause harm and a product-inclined engineering lead can substitute for a product manager. Going forward, he argued, the real superpower is a deep understanding of viability from a systems-thinking perspective. On AI products, viability risks around cost, monetization, liability, and ethics are now table stakes.

Where do teams over-invest their discovery time?

The author splits product discovery into problem discovery and solution discovery, but conceded he underestimated how strongly product people would gravitate toward the problem side, acting as gatekeepers for whether the problem is "worth solving." He called the question of whether something is the most important problem "a fruitless and unanswerable question." All you can know is whether it's a real problem.

The pattern, in his telling: teams obsess over problem validation, then arrive at the solution phase with too little runway. "When a product fails, it's almost always because the solution the team came up with just wasn't good enough."

What's the right "why?" question?

He has long argued for missionaries over mercenaries, but said the more important why is this: why do people use, or stop using, your product? He reported trying new products constantly and being "always amazed by how few of the companies reach out" after he churned. That data, he argued, is among the deepest learning available to a product team and rarely captured.

Why did "CEO of the product" backfire?

The framing pushed product managers toward certainty rather than humility, toward asserting an answer they did not have. He defined humility as "knowing what you can't know, and admitting what you don't know," and tied the absence of it directly to failed products.

Where does predictability hurt most?

Roadmaps and PRDs, the two dominant artifacts in product, function as enablers for believing you know more than you do. Predictability has its place, he said, "but not at the expense of outcomes or trust." He tied the craving for predictability directly to the output addiction that erodes product teams.

What did INSPIRED under-cover?

Three areas the author now flags as major gaps:

• Politics, which includes stakeholder management, executive briefings, and organizational alignment. He calls it a consequence of limited resources, competing objectives, and personal ambitions.
• Product leadership, since empowered teams require better management, not less. The gap was partially addressed in EMPOWERED, but he said the consequences of the original omission persist.
• Corporate governance. He now coaches product leaders to work proactively with the CEO so governance structures can protect the product strategy. He pointed readers to Eric Ries's Incorruptible as a direct treatment.

What did he get wrong about competition?

"For commercial products competing in the open market, product is a full-contact blood sport," the author said, conceding his prior framing sounded too academic. With AI compressing build cycles, competitors move faster than ever, and teams trained on a genteel version of discovery arrive unprepared.

Where is product practice heading?

The author closed bullish on the future of the product discipline. He argued that two persistent objections have weakened: that companies are addicted to output and predictability, and that the product model is too hard to develop. AI tools have made it "dramatically easier to build-to-learn" and reduced the cost of delivery enough to increase, not decrease, the relevance of strategy and discovery.

The work of the next year, for product managers, will be less about adopting fresh frameworks and more about how seriously their teams take the underlying thinking.