Key Takeaways
- Marty Cagan admitted at the Lenny and Friends Summit that structuring his book Inspired around people, process, and product was a major mistake.
- Teams build complex frameworks and sprint rituals because people go to extreme lengths to avoid actual thinking.
- Elon Musk was right when he observed that corporate teams use process as a substitute for first-principles thinking and judgment.
- Automating product workflows with AI agents repeats the agile trap: speeding up output without clarifying strategic problem framing or business viability.
The Regret Behind Inspired
Marty Cagan spent twenty years advising software companies on product discovery. In a keynote address at the Lenny and Friends Summit, he looked back at two decades of guidance and offered an unsparing critique of his own work.
His biggest regret was structuring his classic book, Inspired, around people, process, and product.
By giving process equal billing, Cagan accidentally gave permission for product managers to obsess over mechanics. “I did not appreciate the lengths that people would go to in order to avoid thinking,” Cagan said. “What does it show up as? It shows up as a craving for process, frameworks, and predictability. I structured Inspired as people, process, and product. Big mistake.”
When managers feel insecure about their strategic clarity, they run toward playbooks. They invent sprint ceremonies, backlog grooming templates, and rigid Jira workflows. The process feels productive because tickets move across a board. But running a ceremony is not the same as solving a hard customer problem.
Why Elon Musk Was Right About Process
Cagan pointed directly to an observation from Elon Musk: “In many companies, process is used as a substitute for thinking.”
When a team replaces individual judgment with rigid steps, it protects mediocre decision-makers. If a feature flops after following the playbook, nobody gets blamed because the team followed protocol. The post-mortem checks every box, yet the product still fails in the market.
That safety net destroys real product work. Building software that matters requires sitting with ambiguity, talking to customers until you understand why their business is struggling, and making difficult trade-offs that no checklist can resolve. Process provides an illusion of control, but customers pay for solved problems, not agile compliance.
The AI Automation Trap
Now, product teams are transferring that same craving for safety into AI tools and agent workflows.
Instead of learning how to frame a difficult business model problem, teams rush to build agents that automate product requirement documents, user story generation, or roadmap scheduling. Cagan rejected this trend: “I am not interested in the latest process. I am not interested in the latest framework. I don't really care what you created an agent to automate. I don't care because that's not actually the job of product.”
He added a warning about modern tools: “I am worried that large language models will be used as an alternative to thinking, but the truth is that's already happened with process.”
When code generation becomes fast and cheap, churning out software features is trivial. The bottleneck in a software company was never the speed of writing tickets or generating documents. The bottleneck is knowing which problem actually matters to the customer and why previous attempts failed. An automated model cannot make that strategic choice for you.
What to Do With This
Audit your team rituals this week and cancel any recurring meeting whose primary output is status tracking or ticket maintenance. Before you prompt an AI tool to write your next product document, sit with a blank page for thirty minutes and write down the single customer risk you still do not understand.