We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
OpenAI on simpler products and building for agents
On Lenny's Podcast, Tibo Sottiaux (Head of ChatGPT and Codex) said ChatGPT will merge its chat and "work" toggle. Users liked what work mode could do but sometimes preferred chat because it is faster and more pleasant . Dots has no model picker; users only configure which channels to talk through . He admits he gets "fatigued with the model picker and the reasoning efforts" himself, and wants to get rid of it as quickly as possible . He also called loops and graphs a passing phase. Users shouldn't have to tune their own loops; an always-on agent should learn their goals and feedback instead .
Distribution. Sottiaux called the ecosystem the "sleeper hit." There are 16 sign-in-with-ChatGPT partners, plus plugin extensions and plugin discovery . Popular, heavily used plugins will get a share of revenue . ChatGPT decides which plugins to recommend in conversations based on retention and quality, and weaker plugins stop being recommended . For PMs, that means the ranking rewards keeping users, not winning on keywords.
Agents as users. He expects most internet actions to be taken by agents . When Notion shipped its MCP server, a flood of agent traffic strained its systems and forced it to work out the economics. He says every product faces the choice of whether to offer an agent interface, and delaying it only works for so long . On hiring, he said typing fast matters less now, while taste and understanding users matter more. He described the PM job as deciding what to build, helping build it, and judging whether it's great .
Scott Belsky described the other side of this. Jessica Lessin said about half her Muse use cases stopped working within two days because the browser could no longer complete them; she wondered whether sites had changed policies or added bot detection . Belsky says businesses that depend on the graphical interface (ads, upsells) can either block agents, which means fighting customer preferences, or change their business model to work with "favored agents" and/or build a horizontal agent of their own .
Control comes from permissions, not prompt rules
Aakash Gupta revisits the PocketOS incident. A Cursor agent running Claude Opus 4.6 hit a credential mismatch in staging, found an API token with blanket permissions, and deleted a production volume that also held the backups . His point is that the agent had rules telling it not to do this, and only permissions and review gates actually stop an action. The question for PMs: "What can this agent do without asking, and what stops it from doing the rest?" .
Gupta also proposed an order for learning AI product work. First, treat hallucinations as context failures and prompt for one to two weeks before adding retrieval. Then hand-label about 100 real traces before trusting an LLM judge. Before setting prices, know your P50 and P90 cost per user; he puts AI gross margins at 20–60%, against 70–90% for SaaS . Hiten Shah added two points. Teams blame the model before checking for missing context, weak retrieval, or a bad tool call . And a monitoring agent should tell the difference between "nothing changed" and "I couldn't verify a change" .
A practitioner showed what this looks like day to day. They give coding agents repo questions, feedback theming, and first drafts of requirements docs. They don't trust the agent's reading of the code, because a confident wrong answer looks like a right one. So it goes to engineering as a sharper question, never as a feasibility answer, which "costs most of the speed" . Others described smaller automations: a Jira-to-Confluence triage agent saving 15–30 minutes a day , and drafting briefs, release notes, and weekly updates from tickets and notes .
Practitioner craft
- Record why requirements change. When a requirement changes after refinement, add one line to the issue: what changed, what forced it, who agreed. This breaks down when the decision happens on a call or in a side agreement . One commenter says a missing "why" usually means the change was made on a whim, not on evidence .
- Behavior over compliments. Stronger validation signals include returning unprompted, changing a workflow, or paying . One critic noted these only exist once something is built . A suggested middle path: if three people use a manual version twice, offer the smallest paid continuation with a deadline .
- Customer voice changes minds. Teresa Torres relays Vistaly's practice of putting interview evidence directly on the opportunity solution tree, because teams overvalue their own ideas .
- The first idea isn't the big one. Paul Graham says the biggest idea usually comes later . Believing everything hinges on the first idea makes founders quit too early, or demand that it be huge .
- AI and org design. Hiten Shah argues AI lets companies keep expertise that was never big enough to justify a full role .
Job market
Commenters in r/ProductManagementJobs describe engineer-to-PM switches as harder than ever, with gatekeeping plus a glut of qualified applicants . They point to an internal transfer, built on visibility with director-level PMs, as the more practical route .
- OpenAI plans to merge Chat and Work modes to reduce complexity; Sottiaux also described choosing among models and reasoning options as fatiguing and said he wants to remove that burden.
- Dots is positioned as a persistent agent that understands a user’s goals and preferences, learns from feedback, and can be reached across clients and screens. The initial rollout provides one primary Dot, with multiple task-specific Dots planned so users can assemble a virtual team.
- OpenAI’s ChatGPT ecosystem strategy includes 16 sign-in partners, plugin extensions and discovery, and revenue sharing for popular, high-usage plugins; recommendations are based in part on plugin quality and retention.
- Sottiaux expects most internet actions to be taken by agents, making scale and agent-access economics product concerns: Notion’s MCP brought substantial traffic and system strain, raising the question of whether to build interfaces, agent-accessible capabilities, or both. He also sees delightful experiences for humans using other modalities as underinvested.
- For hiring, Sottiaux emphasized product judgment, user understanding, and knowing what good looks like over fast typing; he framed the PM job as deciding what to build, helping build it, judging the result, and iterating, while noting that roles are blurring.
- In response to a 25-year-old fintech SDE with 3 YOE considering a PM move , commenters describe a difficult market: one says PM demand has been on a similar trend while supply is increasing ; another says age is not the issue but switching is harder amid hiring-manager “purity” gatekeeping and a glut of qualified applicants .
- Commenters present an internal move as the more practical path: first confirm transfers are possible, then build visibility by networking with director-level PMs and joining product meetings; one says a NextLeap course offers no advantage in the open market . The transition may require doing PM work alongside development duties, and compensation varies by company; one commenter says some firms’ PM base pay is near, but not equivalent to, developer pay .
- The interviewee forecast that agents will perform most internet actions, so agent-facing products need to handle large-scale usage and its economics; Notion saw substantial traffic arrive after exposing an MCP, putting strain on its system. He also said investment in delightful experiences for humans remains important.
- OpenAI described opening ChatGPT to extensions and plugin discovery, with revenue sharing for popular, heavily used plugins; recommendations are based on retention and quality, and weak plugins can lose recommendations.
- Dots launched with one configurable primary agent intended to learn user preferences, with additional role-specific agents planned. The broader UX direction is an always-available agent that learns goals and feedback, rather than requiring users to configure task loops.
- Product skills the interviewee said are gaining value include taste, understanding users, choosing what to build, recognizing quality, and iterating; typing speed matters less, and design and engineering roles are blurring.
- A PM who enjoys product strategy and design but dislikes stakeholder coordination says general management and product-strategy roles are rare; commenters caution that leadership still involves stakeholder alignment and execution accountability. One describes the management route as Group PM to possibly director, with CPO roles uncommon.
- Suggested alternatives include consulting, strategy and operations, starting a company, and—after earning well as a PM—angel investing; an MBA was also suggested for pivots into finance or consulting. Adjacent support or operations roles may involve a pay cut, while other pivots may require a persuasive explanation of transferable skills.
- A founder shifted a TCG-card similarity engine from an intended Shopify product-recommendation app to a standalone discovery site after finding the card-to-card exploration loop enjoyable. Community promotion brought 30–40 daily users; 25% returned for at least two sessions separated by 30 minutes and 15% returned on multiple days. When the subreddit banned promotions, traffic fell to zero after two weeks; Reddit and Google ads mostly brought instant bounces.
- Replies suggested treating repeat use as an early demand signal and reducing reliance on one acquisition channel: create descriptive, indexable pages for individual cards and submit the site and sitemap for indexing, while recognizing SEO may take weeks; other suggestions included participating in relevant communities and using the Shopify app as a distribution channel through installing shops.
- A PM’s agent turns Jira email notifications into a per-ticket Confluence to-do list and hides completed items on later runs; the builder reports saving 15–30 minutes daily. A separate Jira planning companion projects Kanban team velocity against a capacity cap to estimate when tickets may finish; the builder says it saves hours weekly and improves planning speed and accuracy.
- PMs are automating routine outputs from meeting notes, artifacts, and tickets, including product briefs, release notes for shipped tickets, user documentation, weekly management updates, and usage summaries.
- One PM built a shared home for HTML artifacts, with folders, comments, and collaboration features, after finding it difficult to collaborate on artifacts generated with Claude.
- Sparrow is an unreleased tool intended to create designs and user stories during meeting conversations in real time and manage them in projects; its builder is seeking early beta feedback.
Lenny Rachitsky’s conversation with OpenAI’s Head of ChatGPT and Codex, @thsottiaux, covers product theses that model pickers may disappear, loops and graphs may be a passing phase, and agents may soon handle most internet actions; it also discusses OpenAI’s approach to AI safety.
Hiten Shah argues that org charts reflect expertise economical to hire but omit useful capabilities too small to justify a dedicated role; AI may let companies maintain expertise before the work warrants a job, a useful lens on how product teams access capabilities beyond their formal headcount.
Audit recurring, important work that nobody clearly owns—especially work that is too small for a full-time role but whose absence is noticeable.
- On April 24, a Cursor agent running Claude Opus 4.6 encountered a staging credential mismatch, found a blanket-permission API token, and deleted PocketOS's production volume, where its backups also lived. Prompt rules alone do not prevent unsafe actions; PMs should define permissions and review gates, and ask what an agent can do without approval and what blocks the rest.
- Growth loops are self-reinforcing alternatives to funnel-only growth, supporting acquisition, engagement, and retention. Uber's loop runs from more riders to more driver supply to shorter pickup times, which attracts more riders. Airbnb's host capacity drives guest bookings and further capacity, supported by SEO, host promotion, reviews, and host and guest invites. HubSpot's customer revenue funds content that attracts more customers, alongside SEO, sales, integrations, content sharing, and email marketing loops.
- A proposed AI-product PM learning sequence: understand that models can produce confident-sounding falsehoods, improve context and prompts for one to two weeks before adding retrieval, then experiment with agents on your own work and build them in an inspectable workflow such as n8n. Before shipping, hand-label about 100 real traces and validate the LLM judge against them; before pricing, know P50 and P90 cost per user, given the stated 20–60% gross margins for AI versus 70–90% for SaaS.
Product teams tend to overvalue their own ideas about what to build; embedding customer interview evidence in the opportunity solution tree can help teams hear customers describe problems and align on which problems are real.
When AI work underperforms, don’t assume the model is at fault before diagnosing the system: missing context, weak retrieval, the wrong method, a bad tool call, or losing the thread can also be causes.
AI monitoring products should distinguish a verified “nothing changed” result from an inability to verify whether anything changed; these are different outcomes and should not be reported interchangeably .
For post-refinement requirement changes, record on the issue what changed, what forced it, and who agreed; a practitioner recommends requiring a one-sentence rationale for every change so the reason stays with the work. Calls, side agreements, and configuration workarounds can bypass the tracker, leaving later owners to reconstruct the decision and potentially re-litigate it.
Humynity is testing an execution network that routes enterprise tasks directly to professionals with relevant production experience, offering an alternative to agency hiring and freelancers’ bidding and pitching; its first beta will use a closed Discord to manually route client tasks.
In a PM resume review, a commenter warned that combining internship and full-time experience on the same timeline can look like a red flag and make the resume read more like an APM profile than a PM one. The junior PM, whose assigned title was Growth PM, asked whether to show clearer timelines and separate experiences .
- After hundreds of outbound messages produced no results for a deep-research SaaS, commenters recommend reassessing the ICP rather than simply increasing outreach: narrow to a vertical and the person whose work is research-heavy, and test whether small consulting firms are the right buyers. Freelance researchers or analysts—and data analysts or scientists in larger organizations—are suggested as alternative users or referral paths.
- Validate value with a prospect’s actual research task, delivered free, rather than a demo; gather feedback and develop pilot users through local industry conversations and warm introductions. To build trust, show sample research outputs with claims linked to their sources instead of relying on a benchmark, and have a clear answer ready on data storage and access for prospective law-firm buyers.
- For outreach, commenters suggest contacting people showing a current problem signal, engaging with their content before messaging, and sharing case studies in the communities and professional groups where target buyers gather; they describe small consulting firms as particularly reliant on referrals and peer proof.
- For product validation, weigh observed commitment over compliments: stronger signals include spending time trying a product, returning unprompted, changing an existing workflow, asking when it will be available, paying, or recommending it.
- Treat these behaviors as evidence about a product people can use, not proof that an unbuilt idea will work; turn early use into a test, such as offering the smallest paid continuation by a deadline after three people use a manual version twice.
A product manager uses coding agents to check whether existing features are configurable, group a week of customer-success feedback for manual review, and draft parts of requirements documents. They treat codebase analysis cautiously: because confident but incorrect answers are hard to spot, they pass findings to engineering as sharper questions rather than feasibility conclusions, accepting a substantial speed tradeoff .
For PM interviews with prospective stakeholders, keep the core answer consistent while shifting emphasis by audience—clarity and feasibility for Dev, process for Product Ops, and impact for Business—and practice answering the same question from each perspective. This advice was given to a candidate who had passed the Product lead round and was preparing to meet those stakeholders.