产品管理已经死了：下一站是带着智能体干活的「三栖」

Claire opens the Lenny & Friends Summit with a deliberately blunt thesis: product management is dead, or will be soon, and the useful question is what product leaders should do instead. She frames the talk as a bet on the future rather than a hot take, and asks the audience to hold on to that claim through the evidence that follows. The point is not to eliminate the craft but to force a pivot: the work that defined the role is being compressed, so the role has to be rebuilt around what remains scarce.

Claire argues AI will transform product, design and engineering faster than people expect — faster than the usual 'yeah, yeah, yeah' reaction allows. After two decades in product, she says the rate of change over the last 18 to 24 months has made things she never thought she would see in her lifetime feel almost boring. Her job, as she describes it, is to not be surprised: build product strategy for what customers will need in three, five and ten years, and build the team that can push toward that future.

Claire tells a self-deprecating story about 'baby Claire CPO' being asked for a product strategy and going through a long, familiar ritual. She talked to customers, sales, finance and engineering, took notes, thought hard, wrote the strategy in a document tool, took it back to the team, absorbed feedback, thought again, and produced another draft. After many weeks and many conference rooms, she ended up with a roughly ten-page document with a link to all the drafts at the top.

The next time she built a product strategy, the process looked completely different. She dropped her kids at school, put ChatGPT voice on her phone and prattled through everything she knew, then asked it for the product strategy. It produced the same ten-page document, which she then sharpened on her laptop; she calls this a perfect metaphor for how product work is changing.

Claire walks through the broader before-and-after: strategy writing that took weeks now starts with a voice memo and an editing pass; requirements and feedback docs that took days become a 15-minute scaffold that is 80% good and a 45-minute sharpening pass. Wireframes on paper or Balsamiq become fully functional prototypes shared with teams and customers in minutes. Spreadsheet-based customer feedback and prioritization become no-code automated insights, and hand-made slides become AI-generated slides.

Claire concludes that product work now takes less time, less thought and maybe fewer PMs. That could make the job more fun, but only if product people do what she says they are good at: pivot. The alternative is to defend a shrinking set of tasks that AI already does adequately.

She lays out three requirements for an AI-powered PM: automate yourself to speed up delivery, add new skills and do more, and multiply your impact by teaching the team. Her first instruction is to become an AI-powered product team now, not after a reorg or a tooling budget cycle. She even generated her own to-do list with ChatGPT, then turned it into an anti-to-do list.

The anti-to-do list is deliberately concrete: do not draft documents alone, do not manually gather or give passive feedback, do not write updates by hand, and do not hand-produce agenda summaries and action items. Do not manually prioritize feature requests, monitor goals and OKRs, track competitors, prep interviews, consolidate candidate feedback, tell customer stories, make slides pretty, or repeatedly explain product functionality. These are the chores that turn product managers into support knowledge bases instead of people doing higher-leverage work.

Claire's operating trick is to catch herself in the moment: every time she does one of those tasks and wishes she did not have to, she spends four to seven minutes trying to manifest a way not to do it next time. About 80% of the time, she says, she gets it done and ships the automation. She quotes a teammate: do not ask how to get to 100%; ask how to get to 75% faster than starting from zero.

Claire points to Cody, who leads product innovation and incubation at LaunchDarkly, as the shape of the new hire. Cody came from development, engineering and marketing rather than classic product management, and learned to be an 'edge prototyper' who builds product in code. When Claire offered him ChatGPT-based product management help, he said sure and stepped into a product leadership role with a very different skill base.

Cody got blocked because design had four other priorities, and instead of waiting or crying about it, he learned to design. He started using v0 to build beautiful designs and prototypes, not just wireframes, as part of the requirements package he handed to the team. By the end of the story he was even starting to write PRDs for frontend code; Claire says these are exactly the kinds of people who will come for product jobs.

The final piece is multiplication: none of this matters if only one person, 'a Cody', changes. LaunchDarkly runs a 'Building with AI' channel where people share daily automations, ask for help and post what they build. Claire posts constantly because a product leader has to normalize using the tools and make people less bashful about experimenting; funding the tools matters, but cultural permission comes first.

Claire's most strongly held belief is that AI will collapse the talent stack, turning separate product, design and engineering jobs into one broader role. She acknowledges this is scary and a big change, but argues it does not have to break the team if leaders plan for it. The collapse is not a thought experiment for her; it is the organizing premise for how she wants to hire and structure product teams.

She runs an arm-raising exercise to show how rare cross-functional behavior still is: many people have written a document this week, fewer have done design, some have written code, and only about five have deployed code to production. She contrasts that with the classic product triad — product, engineering and design, sometimes with data added — surrounded by supporting resources. That triad, she says, has been the platonic ideal of a product team for a long time.

The problem with the triad is that separate functions turn product development into a handoff mechanism: product hands requirements to design, design hands work to engineering, and product stays hands-off from what actually gets built. Claire says the replacement is a generalist specialist — deep in product, design or engineering, but expected to participate across the building process. LaunchDarkly's operating principle is 'there are no lanes': if something needs doing and you have the skill, you do it, even if that means product doing design, design pushing React code, or engineering writing a PRD.

Claire predicts an AI-powered 'triple threat': one person who can do engineering, design and product as the lead of a team that also includes AI tools, agents and platforms. This person may spike in engineering, classic product management or design, but will need to know how to do it all. In that world, the triad goes away as the default organizing structure.

The logic is speed: small teams generally move faster than big teams, and Claire pushes further by arguing that individuals can move faster than small teams. The exercise is to imagine how fast opinionated product leadership in a small team can move things forward when given the right tools. That is why she believes the role may expand into more commercial and marketing orientation, more data tooling, and maybe everything else.

Claire acknowledges that this future scares people, including people who like their lanes and their craft identities. She quotes a friend: the only people who need to be worried are the people acting like they do not need to be worried. If leaders accept the thesis that things will change dramatically, they can prepare themselves and their teams in advance instead of becoming obsolete.

She contrasts two attitudes: 'AI will never do this thing' is naive, while 'AI can help me do anything' is inspiring. The second attitude is what gets her excited about what can be built, put into the market and created with the new tools. That optimism is not a denial of the disruption; it is a choice about how to respond to it.

Claire turns the warning on product leaders: AI is coming for you too, despite the comfortable assumption that only PMs are exposed. She expects leaders to manage whatever this new AI-augmented team becomes, which is unlike the teams most of them have run. For B2B and enterprise leaders, that means more commercial skills and more technical skills; she describes herself as a CPTO because the functions are already coming together.

Leaders will be expected to manage people who code, and to think differently about budgeting. Claire says they will need to budget for headcount versus budgeting for agents and tools, and that this changes how they think about investment in R&D. The operating model is not just a tooling decision; it changes the shape of the org and the cost base.

She calls the result 'artisanally crafted team topologies': the team is built for the thing that needs to get done, rather than forcing every project into the same triad template. Leaders should organize around motivated individuals; if someone comes in with a globe-shaped set of skills, build a team around that, and if someone spikes on product where that skill is needed, build the team around them. Team design becomes a creative act, not a fixed prescription.

Claire warns that experience and strategy — the minivan story — are becoming commodities. She cites a Lenny's Newsletter article on how close AI is to replacing product managers, where an AI-generated vision was preferred on quality even when people knew it was AI. The implication is that hard thinking is less special than product people assume, and they need to skill up and build a moat.

The moat she points to is running, building and scaling AI-powered teams, and she says it will happen fast enough that leaders need to start now. She tells a story about sitting next to a CEO from a non-tech-forward company who had built a digital twin and would not let anyone in the company ask him questions until they had asked the digital twin first. That made Claire realize that even she was behind.

Her TL;DR is a call to reanimate product management: become an AI-powered product team now, expect AI to collapse the talent stack, care for culture and organization, and plan accordingly. Product leaders should join her in imagining the three-to-five-year future and manifesting it in their teams. Her final advice is to find AI-powered triple threats, give them power and give them budget.