Personal agents make product craft matter again

@sriramk sees "a come back of product management" in how personal agents are designed. Instinct, Dot, Muse, and Grok bot each involve real product work to connect the UX with the model underneath and with the services it can reach @sriramk. He says he "rarely care[s] about the underlying model" but cares a lot about small touches, like Muse's activity notification or Instinct's thumbs-up emoji to acknowledge a message. He contrasts this with the "upgrade to latest model" path the industry is otherwise on @sriramk. Lenny Rachitsky shared it with the comment "PM ascendant" @lennysan.

The strategy question is what happens to companies these agents route around. In "The Amazon Trap," @mvernal (an initial investor in Instinct and on its board) @mvernal argues that Amazon spent 15 years training shoppers to start on Amazon instead of Google, and its $80B ad business is the reward @mvernal. Now it is reacting badly to Instinct and Muse and leaning on an "Alexa for Shopping" tab @mvernal. His case: horizontal agents win because they hold all of a user's context. That leaves Amazon choosing between giving up ad revenue and annoying its customers, while Walmart and Shopify can take share by supporting agents @mvernal. His proposed way through is a "Prime+" tier at about $299 a year with agentic purchasing only available there. It would give loyal customers a way in and replace lost ad revenue without betting the company @mvernal. Scott Belsky agreed: "you can't fight customer preferences for horizontal agents, you must innovate to meet them" @scottbelsky.

Broad versus specialized agents

An a16z conversation pushed back on the all-in-one model. One speaker connects his agent to everything so it can join context across chat history, GitHub, Salesforce, and his calendar a16z. The counterpoint: the more work you hand a general agent, the more understanding you give up, and "agents don't have any responsibility" a16z. That speaker expects vertically focused sub-agents with quality checks, possibly coordinated by a chief-of-staff agent a16z. Replit spent nearly a year making its product deployable in customers' own clouds because of data-leak worries. Speakers agreed that making agents useful at work is still largely unsolved a16z. OpenRouter added that it is surprised how little benchmarking enterprises do, and it expects internal AI teams to build more evals a16z.

On the build side, Teresa Torres found that when an agent edits a tree, comparing the input and output trees can produce several valid change sets, and only one shows what actually happened. Her fix is to give the agent rules for meaningful moves and log every move as it builds @ttorres.

Keep the judgment yourself

Aakash Gupta disagrees with the complaint that Claude Code dulls you. If 90% of your job is pressing enter, "the model is making your decisions" Aakash Gupta. He cites an MIT Media Lab EEG study: people who wrote on their own first and then brought in the model showed the highest engagement Aakash Gupta. His real workload is deciding which of a dozen prototypes "deserves to exist" and saying no, because "when building is free, shipping everything buries the three things that matter" Aakash Gupta.

A practitioner post shows the same shift landing on teams. A PM leading two PMs and three designers says that after adopting GitHub and Claude, designers were expected to deliver close to production-ready pages, covering every error state, breakpoint, and accessibility case, without training for it. Meanwhile engineering keeps setting and changing direction r/ProductMgmt.

Leadership and growth

• The Standard-Setter. John Cutler argues that pushing people harder produces evidence "that people can respond to pressure," not evidence of impact. Many people respond better to clarity, trust, autonomy, and good feedback The Beautiful Mess. The style looks good to executives, while the costs (exhaustion, churn) land on the team The Beautiful Mess.
• Upskilling for today. Shreyas Doshi says mid-career PMs wrongly see upskilling only as preparation for the next job. Building stronger leadership skills would free up time in their current role, which breaks the "too busy to upskill" loop @shreyas.
• Flat teams. Belsky praised "talent dense, aligned, flat, and empowered teams" @scottbelsky. The example he quoted was Nikita Bier dropping his assigned work to fight spam. Bier himself notes the model is "very hard to make … work in a larger company" @nikitabier.
• Occasional expertise. Hiten Shah: you don't review pricing or plan a launch every day, but competitors keep moving. AI changes what it costs to keep that expertise current @hnshah.