•
🌲 evergreen
AI + Product Management

AI + Product Management

2026-04 Update — Consumer AI Market Structure

From Menlo Ventures - 2025 The State of Consumer AI:

  • 10x Rule - Why Specialized Consumer AI Tools Lose to Default Assistants — general assistants take 81% of consumer spend; specialized tools only break through at ~10x advantage. Structural advantages (workflow embedding, proprietary data, radically different output) beat feature advantages.
  • High-Frequency High-Friction High-Trust - Consumer AI White Space Pattern — the underserved consumer AI categories all share three traits: high-frequency, high-friction, high-trust. Healthcare research, finance, connection, learning, home tasks, family logistics are the biggest 2026 gaps.
  • Creative Tools in the AI Era - Compression in the Middle, Taste at the Top — creative tools are 45% of specialized-tool spend. Floor is rising (amateurs reach professional-looking output), ceiling is stable (taste stays scarce), middle is compressing fastest.

Summary

  • Keep PRD / PRFAQ and Opportunity / Solution Tree approach with hypotheses Prototype Development Lifecycle
  • Rapidly generate prototypes with workable analytics to validate with stakeholders, end users
  • Build a repo / library — prompts, design systems
  • AI can/will make product management more critical >> Yes, the role will change. But the traits that make a great product manager today will be as important (if not more) in the future: strong customer empathy, strategic thinking, and leadership skills. Will AI kill Product Management?
  • Instead, we’ll see product management take on an even more central role — and we’ll see demand for what only the most senior and skilled PMs and product leaders can deliver today—deep product sense, rigorous strategic thinking, analytical decision-making, and the ability to build, lead, motivate, and align teams.

Organization & Optimization

These ideas are not theory – there are product teams implementing AI with these patterns today. But there are still three main questions I’ve seen:

  1. How does the team stay organized?
  2. How does the team collaborate and reduce rework?
  3. How fast can you run this cycle?
    I’m still working on solutions in this space, but for now I’ll provide a few best practices:
  4. Create a baseline prototype library: Instead of reimplementing the same starting point each time, create a prototype that matches your existing application, then copy it. Add your new feature on top of the copy. Whenever you need to prototype something new, create a new copy of the baseline.
  5. Build design systems: Whether you import directly from Figma or use screenshots, a great asset to build is reusable components. This design system can be leveraged to build prototypes across team members so that everything has the same look and feel.
  6. Think AI first: If you’re building a genAI feature, it’s very challenging to prototype in a static design tool. Leverage AI prototyping to test new ideas with real customers by actually using an LLM in your user testing.

References

Context Engineering Cursor for PMs Product Management Prototype Development Lifecycle Will AI kill Product Management? Exiting the matrix — build products 10x faster Why Every PM Needs Claude Code

2026-09 Update — Evals as Product Work

From AI Evals - A Hands-On Guide for Product Teams (Teresa Torres):

  • Error Analysis Comes Before Eval Design — you cannot choose evals until you have read real output and catalogued what the model actually gets wrong
  • Correctness Is Context Dependent, So Do Not Outsource It — vendor built-in evals ship someone else’s definition of good, and it does not survive a change of user
  • Let the Error Shape Choose the Eval Type — whether detecting an error needs judgment is what picks the method
  • Evals Are a Discovery Habit — evaluation as a feedback loop peer to interviewing and assumption testing, not as QA

  • Spec-Driven Development and AI-Native SDLC - 2026 Analysis — specs as the new PM artifact; SDD reshapes how PMs define requirements
  • PM-Engineer Mind-Meld - 80 Percent Overlap Replaces the Handoff Model — 80% shared context replaces PRD handoffs; from Cat Wu at Anthropic
  • Research Preview Shipping - Reduce Commitment to Compress Feedback — ship ideas in 1-2 weeks with reduced commitment; preview label compresses feedback loops
  • Principles Plus Metrics as PM Replacement - Independent Decision-Making Without Bottlenecks — written principles + weekly metrics enable PM-quality decisions without PM bottleneck
  • Cat Wu - Head of Product Claude Code Cowork at Anthropic — first-person account of AI-native PM at Anthropic
  • AI Product Management Guide - Every — practitioner guide to agent-driven PM: strategy docs via interview, no-ticket workflow, product pulse automated metrics
  • AI PM in 2026 - Skills, Interviews, and the PM OS Question — what the loop actually tests now (product sense carries it, estimation is dead), plus the “Human Delta” framing and a tested verdict on the PM OS genre
  • Evals Are a Discovery Habit — evaluation joins the discovery habit set; the loop that tells you whether a change to an AI product worked
  • Correctness Is Context Dependent, So Do Not Outsource It — defining what good looks like is product work that cannot be bought
  • Error Analysis Comes Before Eval Design — the first move: read the output, log the mistakes, let the error types select the evals

2026-09 Update — Story, Judgment, and Onboarding

From Josh Elman - Product Management Is Still About Telling Stories:

  • The PM Artifact Is a Repeatable User Story — shared product intent must be understandable and transmissible; cheap prototypes do not remove the production design and engineering required for a working product
  • Product Vision Is Purpose, Core Actions, and Cycle — define meaningful use and its natural recurrence before optimizing aggregate activity
  • Onboarding Teaches the Product Story to the Fuzzy Middle — teach concepts to motivated but uncertain users and judge onboarding by retained core-action use

Elman also draws a boundary around cheap execution. AI can invert discovery from spec-and-scope toward build-and-play, but demos remain far from working products. Faster prototypes should increase the evidence available to judgment, not accelerate indiscriminate product commitment.

Connected Notes