We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
How the Codex team ran with two PMs
In Product Compass, Rohan Varma, Cursor's first PM and until recently Product Lead for Codex at OpenAI, describes that team: about two PMs, two designers and 30–40 engineers across roughly 15–20 product areas . They wrote few traditional specs. Sometimes a spec was about ten bullets. Varma set strategic guardrails and engineers made the micro-decisions. Most projects had one or two engineers, because "human-to-human collaboration becomes a big bottleneck" . A brief should set out the problem, outcome, constraints and scope. It should also say what the builder can decide alone and what evidence would change direction. Planning ran four to eight weeks at a time, not six months .
The guide also offers two habits for AI PMs:
- Start with the bottleneck. In his support example, agents struggle to find the right policy, not to write replies. That points to a copilot that drafts cited answers for agents to approve, not a fully autonomous chatbot .
- Diagnose before you re-prompt. A wrong answer can come from retrieval, from missing context or from generation. Each needs a different fix .
The constraint is now judgment
Aakash Gupta opens with a line from Madhu Guru, who led product for Gemini: "I've never felt this behind as a product person." Gupta's argument: engineering capacity used to be the excuse, but a PM can now spin up execution in an afternoon. The hard part is separating signal from noise, deciding what to build and scoping ruthlessly. That team constraint was "a useful governor that prevented bad ideas from shipping" . In a separate note, Gupta says he tested four graph designs against single-shot prompts on 40 PM tasks. The biggest margins came on tasks like PRDs, eval suites and roadmap prioritization. Every winning design worked by checking facts, not by improving judgment, so his advice is to "wire a graph when the failure mode is a wrong fact" .
Practitioners split on whether AI has improved the job
An r/ProductManagement thread asked whether PMs still enjoy their jobs. The useful answers fit Gupta's argument:
- The upside. A PM without analyst support says data analysis went from three days to an hour . Another spotted segment-level conversion patterns in a BI chart and had Claude code a four-arm onboarding test that was live by ten. The segment-specific variant was ahead by that afternoon .
- The cost. A PM managing several teams says the cognitive load has moved from writing docs to reviewing AI output. Some developers now skip reading the spec, and management wants "more and faster" .
- The exposure. One commenter argues that documentation was never the job. Now that it's 10x faster, PMs who avoid decisions are "exposed" . Another says experience depends on the setup: empowered PMs may be having their best time, while those in feature factories have it worst .
What "AI-native" can mean
Run the Business says most heads of product have been handed an "AI-native" mandate in 2026. It can mean one of three things, or a mix: AI in the product surface, an operating model built around an AI development lifecycle, or a strategy focused on how to win rather than what to ship. Which to pursue "depends" on the company .
Designing for agents
Ravi Mehta looks at Descript, which wanted outside AI agents to edit videos without ever opening its interface. That raised a choice: build a separate machine interface, or make one product that serves both humans and agents . He frames designing for agents as designing "for humans — one step removed" . In a related post, Hiten Shah argues AI video needs evals against a quality bar for story, pacing and brand. His team tested AI editors on real footage and plans to share what worked on Friday .
Briefly
- Validation: In an r/startups thread on vetting ideas, one founder's playbook: ask about the last time the problem happened, not "would you use this?". Do the job by hand for five to ten people. Treat a deposit as worth more than a hundred signups, and competitors as evidence of demand .
- Sharing work: In a podcast with Petra Wille, Teresa Torres urges PMs to share specific work they are personally doing, even null results such as "we tried 20 things… no efficiency gains" .
- Daffy separates funding charitable giving from choosing recipients: users can set money aside when convenient and recommend charities later, addressing the discomfort of making both decisions during a solicitation. The product applies behavioral-finance techniques used in retirement plans and supports recurring donations to make giving an intentional financial goal; Nash says members give more consistently and often give more to organizations they already support.
- Daffy combines charity information with peer context: members can view basic publicly filed information and optionally share notes about why they give; Nash says these notes can help people discover organizations and build trust.
- Daffy offers auto-rebalanced ETF portfolios, more than 600 ETFs, eligible individual stocks, and native crypto, with investment choices that can reflect whether funds are intended for near-term or long-term giving.
- At SurveyMonkey, Verna moved into growth product as a PM with engineers after reaching a ceiling in analytics, then expanded into growth marketing and analytics. She initially questioned whether growth belonged in a dedicated team, arguing that growth is the whole company’s responsibility—a useful organizational tension for product leaders to weigh.
- At Lovable, she spends a couple of hours each week exploring the product because its team keeps adding features and she still has more to learn about its capabilities; she sees hands-on exploration as a way to find how technology can increase impact at work or in something built independently.
- For her own advisory business, Verna used ungated expertise on social media and in a newsletter as a freemium top-of-funnel to attract potential clients. She says frameworks are easy to share, while implementing them inside a company is the harder work where her services add value.
- Start with the user’s bottleneck, not an AI solution: in the support example, agents lost time finding correct policies, so the proposed copilot retrieves policies, drafts cited answers, and lets agents verify, edit, and approve them. The suggested goal—halving policy-answering time without compromising accuracy—is illustrative and should be validated with users.
- Diagnose AI failures before changing prompts: an incorrect answer may stem from retrieval, missing context, or generation, and each requires a different fix. Evaluate answerable, unanswerable, conflicting-policy, and high-risk cases; inspect failure categories, regressions, and fresh examples because a higher aggregate pass rate alone does not establish readiness.
- Bound agent autonomy: use permissions, spending limits, and human approval for consequential actions; predictable tasks may be faster, cheaper, and more reliable as fixed workflows, with architecture revisited as evidence changes. At rollout, measure the whole task—including latency, tool failures, human review, and cost per successful resolution—not just model-response cost.
- Rohan described Codex as having roughly two PMs, two designers, and 30–40 engineers across approximately 15–20 product areas; the team used few traditional specs, relied on strategic guardrails for autonomous decisions, and planned in four-to-eight-week increments rather than six months.
- Verna applies a growth-funnel model to her advisory business: ungated social and newsletter content serve as freemium acquisition for relevant prospects, while advising and interim engagements act as trials that can lead to full-time work. She argues that publishing frameworks is easy; the hard, human-intensive work is operationalizing them within a company's details.
- For expertise-based distribution, she recommends starting on social for faster feedback, sharing specific examples and patterns rather than generic advice, and iterating until finding an audience and voice before adding a newsletter; she launched hers about two years into her social journey.
- She recommends setting aside regular time to explore AI tools and product capabilities: she spends a couple of hours weekly experimenting, including with Lovable, because its product team continues to add features.
For product managers advocating a proposal, a potentially useful reframe is to treat promotion as sharing the work’s ideas rather than elevating oneself: in a book-launch discussion, the guest distinguishes the book’s ideas from himself, and the host frames sharing useful work as service to others. The suggested practice is to question the limiting belief, consider whether its opposite could be true, then write down and revisit the alternative when hesitation returns.
Teresa Torres recommends sharing specific work you are personally doing rather than generic advice: describe the practice and messy learning, even if the story is unfinished, for someone one step behind you. A result without efficiency gains can still be useful to share—for example, trying 20 things that changed the work but did not improve efficiency. She suggests a low-stakes five-day habit: post the day's most interesting event and say what you faced, did, and hope happens; most posts get ignored, so the risk is low.
For product execution, prioritize controllable actions and rehearse obstacles rather than fixating on desired outcomes: the speaker contrasts an uncontrollable bestseller result with a controllable hour of daily writing, and recommends mentally rehearsing likely difficulties and responses (“mental contrasting”). He reports that students who visualized getting an A studied less and earned worse grades than students who did not, suggesting that outcome visualization alone can undermine action.
- AI is making market and competitor research, vendor and feature POCs, legal work, documentation, and handoffs easier; one PM without analyst support says a data-analysis task shrank from three days to one hour. A PM managing multiple development teams reports the tradeoff: more AI-generated material to review, faster output expectations, and developers sometimes missing specs or acceptance criteria under the increased pace; they are trying not to measure success solely by speed.
- A recurring concern is that AI makes process-heavy PM work less central: as documentation speeds up, PM value shifts toward making timely product decisions and choosing priorities, rather than mainly producing decks, requirements, and process artifacts. One commenter says the experience depends on the role: empowered PMs with real product goals may thrive, while micromanaged feature-factory roles may be especially difficult.
- One PM used BI data suggesting different user segments converted better with different features to create a control and three treatment variants for onboarding using Claude; the segment-specific treatment was winning that afternoon, with productionization and further paywall testing planned if the signal held.
Lenny’s Product Pass added OpenRouter (one API and bill for hundreds of AI models), PloyAI (AI growth-marketing agents), Sentry (alerts when shipped software breaks), TextExpander, and LangSmith (tools to inspect and improve AI agents)—options relevant to AI development, growth, and product reliability workflows. The pass is advertised as a free year of access to 35 products worth $41,428 for Insider subscribers at $400/year, or 22 products worth $37,062 for Annual subscribers at $200/year; codes are first-come, first-served, and popular products may sell out.
Beam says it reached #1 Product of the Day on Product Hunt last month . The team used Beam screenshots and recordings to test AI video tools and planned to show the first renders and what needed fixing .
- OpenRouter and LangSmith were added to Lenny’s Product Pass. OpenRouter provides one API and bill for hundreds of AI models, with model selection or routing, quick model swaps, per-key spend limits, and automatic failover—useful for managing model choice, cost, and reliability in AI products.
- LangSmith supports building, testing, deploying, and improving agents through observability and evaluations; the newsletter says product managers are increasingly using it to manage agent quality and performance. Examples include Rippling using traces and layered evaluations to catch regressions, and Clay reconciling 99.5% of inference spend across providers.
Lenny’s Newsletter Product Pass added OpenRouter for one API and bill across hundreds of AI models, PloyAI for AI-driven growth marketing, Sentry for detecting product failures, TextExpander for reusable prompts and phrases, and LangSmith for observing and improving AI agents. The bundle lists 35 products worth $41,428 for Insider subscribers at $400/year, or 22 products worth $37,062 for Annual subscribers at $200/year; codes are limited and popular products may sell out.
AI video editors need evaluations against a quality bar for story, pacing, and brand so content factories improve with each edit, Hiten Shah argues. His team tested AI editors on real footage and reviewed first cuts for both failures and successes; he said it would share what worked Friday.
Warp Sciences says it is building robots to perform real scientific experiments and accelerate discovery, and is hiring full-time and intern roles in robotics hardware, robot learning, and robot operations .
Jensen Huang said that after his departure from NVIDIA, he would return as CEO if the board decided it was in the best interests of the company and its stakeholders; he also said he would cooperate with the board’s independent investigation into serious personal mistakes that created problems for the board.
a16z Speedrun opened its Insiders program to executives and operators, building on 150+ C-suite founding members; it aims to give company buyers early access to startups and provide founders with feedback from people who may buy their products. Members can watch weekly startup demos, get warm introductions to founders, and join early pilots as design partners who help shape products; participation is free.
For product launches and GTM, build an audience between launches with useful, recurring content from people the market wants to hear from, rather than relying on a campaign when an announcement is imminent; that way, people can stay connected after a launch and be more familiar with the company by the next one. The article argues this matters as search and AI-generated answers can reduce visits to company websites, while feeds increasingly help people discover individual voices.
Descript’s Underlord AI editor can turn an hour-long webinar into five short videos; the company also wanted other AI agents to edit videos without opening its interface, raising a product-design choice between building a separate machine interface and making the existing product work for both agents and humans. The post frames agent UX as designing for humans one step removed.
- For a new design studio, validate a focused offer before buying a broad equipment stack: a commenter warns that the bicycle market is saturated and suggests testing work for 3–6 months through a local fab lab or rented facility, then adding tools; another recommends starting with one strong manufacturing process and expanding as client needs become clear.
- Make equipment decisions as build-versus-buy tradeoffs: one studio operator says a desktop CNC is hard to justify over outsourced services unless machining volume or faster turnaround is valuable, and advises accounting for skill requirements, opportunity cost, and workflow peripherals—not just machine price.
- Funding conditions can change the sequencing: this requester’s grant requires a detailed wishlist and business plan, excludes consumables, and favors high-end, technology-oriented machines, limiting the usual option to buy equipment only after client demand is demonstrated.
An “AI-native” product organization can mean three distinct things: AI-infused product features, product rituals and ceremonies aligned to an AI SDLC, or business bets focused on how to win rather than what to ship. The right approach depends on the company and its circumstances, so the mandate should not automatically be treated as a request to add AI to the product surface.
r/ProductManagement comment by u/HustlinInTheHall
Product Managers: Are you still enjoying your jobs with AI changing the industry?
Hey everyone,
For those currently working in Product Management, how has AI changed your day-to-day experience?
Has it made your job easier, or has it increased expectations? Do you feel more pressure from leadership to deliver faster, take on more initiatives, or accomplish more with the same or fewer resources? Are engineering and design teams feeling similar pressure?
Overall, are you still enjoying the work? How optimistic are you about the future of Product Management over the next 5–10 years?
I think you hit on it that it has made parts of the job easier, but it has also significantly raised expectations.
Like prototyping alone now is completely different than six month ago. The president of my division can spin up a prototype that looks like it’s ready to ship tomorrow, so now I have to explain to him why that’s not yet ready and still needs to go through design review and testing and actually get built. That’s just a totally new pressure that didn’t exist.
At the same time, it is genuinely much faster to build things. We’ve built and shipped more things in the last 8 months at my job than I did in the previous three years. That makes the job harder, but it also makes it more rewarding. It sucks to get through a year of work and look back and realize you only have like two medium-sized wins because the bigger swings were too much work.
At the same time, I have seen a lot of PMs really get exposed because fundamentally the value of having a PM is helping you arrive at the right decisions at the right time. That’s the job. But a lot of PMs get into the role and never make decisions. They prune backlogs, document requirements, talk to customers, make slide decks, put tickets into sprints, report progress up the chain, look at analytics… but aren’t actually on the hook to decide anything. Now with AI, the decisions have to be made faster, and I think a lot of people are finding themselves ill-suited to a role that had become more about managing process and less about managing products and has now flipped.
- AI is making market and competitor research, vendor and feature POCs, legal work, documentation, and handoffs easier; one PM without analyst support says a data-analysis task shrank from three days to one hour. A PM managing multiple development teams reports the tradeoff: more AI-generated material to review, faster output expectations, and developers sometimes missing specs or acceptance criteria under the increased pace; they are trying not to measure success solely by speed.
- A recurring concern is that AI makes process-heavy PM work less central: as documentation speeds up, PM value shifts toward making timely product decisions and choosing priorities, rather than mainly producing decks, requirements, and process artifacts. One commenter says the experience depends on the role: empowered PMs with real product goals may thrive, while micromanaged feature-factory roles may be especially difficult.
- One PM used BI data suggesting different user segments converted better with different features to create a control and three treatment variants for onboarding using Claude; the segment-specific treatment was winning that afternoon, with productionization and further paywall testing planned if the signal held.