Wednesday, June 3, 2026

The 5 Abilities I Really Use Each Day as an AI PM (and How You Can Too) – O’Reilly

This submit first appeared on Aman Khan’s AI Product Playbook publication and is being republished right here with the creator’s permission.

Let me begin with some honesty. When individuals ask me “Ought to I turn out to be an AI PM?” I inform them they’re asking the unsuitable query.

Right here’s what I’ve discovered: Turning into an AI PM isn’t about chasing a stylish job title. It’s about creating concrete expertise that make you more practical at constructing merchandise in a world the place AI touches all the pieces.

Each PM is changing into an AI PM, whether or not they understand it or not. Your cost movement can have fraud detection. Your search bar can have semantic understanding. Your buyer assist can have chatbots.

Consider AI product administration as much less of an OR and as a substitute extra of an AND. For instance: AI x well being tech PM or AI x fintech PM.

The 5 Abilities I Really Use Each Day

This submit was tailored from a dialog with Aakash Gupta on The Progress Podcast. You’ll find the episode right here.

After ~9 years of constructing AI merchandise (the final three of which have been an entire ramp-up utilizing LLMs and brokers), listed below are the abilities I take advantage of always—not those that sound good in a weblog submit however the ones I actually used yesterday.

  • AI prototyping
  • Observability, akin to telemetry
  • AI evals: The brand new PRD for AI PMs
  • RAG versus fine-tuning versus immediate engineering
  • Working with AI engineers

1. Prototyping: Why I code each week

Final month, our design staff spent two weeks creating lovely mocks for an AI agent interface. It regarded excellent. Then I spent half-hour in Cursor constructing a practical prototype, and we instantly found three basic UX issues the mocks hadn’t revealed.

The talent: Utilizing AI-powered coding instruments to construct tough prototypes.
The software: Cursor. (It’s VS Code however you possibly can describe what you need in plain English.)
Why it issues: AI conduct is not possible to know from static mocks.

How you can begin this week:

  1. Obtain Cursor.
  2. Construct one thing stupidly easy. (I began with a private web site touchdown web page.)
  3. Present it to an engineer and ask what you probably did unsuitable.
  4. Repeat.

You’re not attempting to turn out to be an engineer. You’re attempting to know constraints and potentialities.

2. Observability: Debugging the black field

Observability is the way you really peek beneath the hood and see how your agent is working.

The talent: Utilizing traces to know what your AI really did.
The software: Any APM that helps LLM tracing. (We use our personal at Arize, however there are a lot of.)
Why it issues: “The AI is damaged” isn’t actionable. “The context retrieval returned the unsuitable doc” is.

Your first observability train:

  1. Choose any AI product you utilize every day.
  2. Attempt to set off an edge case or error.
  3. Write down what you suppose went unsuitable internally.
  4. This psychological mannequin constructing is 80% of the talent.

3. Evaluations: Your new definition of “carried out”

Vibe coding works for those who’re transport prototypes. It doesn’t actually work for those who’re transport manufacturing code.

The talent: Turning subjective high quality into measurable metrics.
The software: Begin with spreadsheets, graduate to correct eval frameworks.
Why it issues: You’ll be able to’t enhance what you possibly can’t measure.

Construct your first eval:

  1. Choose one high quality dimension (conciseness, friendliness, accuracy).
  2. Create 20 examples of excellent and dangerous. Label them “verbose” or “concise.”
  3. Rating your present system. Set a goal: 85% of responses ought to be “excellent.”
  4. That quantity is now your new North Star. Iterate till you hit it.

4. Technical instinct: Understanding your choices

Immediate engineering (1 day): Add model voice tips to the system immediate.

Few-shot examples (3 days): Embody examples of on-brand responses.

RAG with type information (1 week): Pull from our precise model documentation.

Tremendous-tuning (1 month): Prepare a mannequin on our assist transcripts.

Every has completely different prices, timelines, and trade-offs. My job is figuring out which to advocate.

Constructing instinct with out constructing fashions:

  1. Whenever you see an AI characteristic you want, write down 3 ways they may have constructed it.
  2. Ask an AI engineer for those who’re proper.
  3. Mistaken guesses educate you greater than proper ones.

5. The brand new PM-engineer partnership

The largest shift? How I work with engineers.

Outdated manner: I write necessities. They construct it. We take a look at it. Ship.

New manner: We label coaching knowledge collectively. We outline success metrics collectively. We debug failures collectively. We personal outcomes collectively.

Final month, I spent two hours with an engineer labeling whether or not responses have been “useful” or not. We disagreed on a variety of them. This taught me that I want to start out collaborating on evals with my AI engineers.

Begin collaborating in a different way:

  • Subsequent characteristic: Ask to affix a mannequin analysis session.
  • Supply to assist label take a look at knowledge.
  • Share buyer suggestions when it comes to eval metrics.
  • Have a good time eval enhancements such as you used to have fun characteristic launches.

Your 4-Week Transition Plan

Week 1: Device setup

  • Set up Cursor.
  • Get entry to your organization’s LLM playground.
  • Discover the place your AI logs/traces stay.
  • Construct one tiny prototype (took me three hours to construct my first).

Week 2: Remark

  • Hint 5 AI interactions in merchandise you utilize.
  • Doc what you suppose occurred versus what really occurred.
  • Share findings with an AI engineer for suggestions.

Week 3: Measurement

  • Create your first 20-example eval set.
  • Rating an present characteristic.
  • Suggest one enchancment primarily based on the scores.

Week 4: Collaboration

  • Be part of an engineering mannequin evaluate.
  • Volunteer to label 50 examples.
  • Body your subsequent characteristic request as eval standards.

Week 5: Iteration

  • Take your learnings from prototyping and construct them right into a manufacturing proposal.
  • Set the bar with evals.
  • Use your AI Instinct for iteration—Which knobs must you flip?

The Uncomfortable Fact

Right here’s what I want somebody had informed me three years in the past: You’ll really feel like a newbie once more. After years of being the knowledgeable within the room, you’ll be the particular person asking fundamental questions. That’s precisely the place you should be.

The PMs who reach AI are those who’re snug being uncomfortable. They’re those who construct dangerous prototypes, ask “dumb” questions, and deal with each complicated mannequin output as a studying alternative.

Begin this week

Don’t await the right course, the best function, or for AI to “stabilize.” The abilities you want are sensible, learnable, and instantly relevant.

Choose one factor from this submit, decide to doing it this week, after which inform somebody what you discovered. That is the way you’ll start to speed up your individual suggestions loop for AI product administration.

The hole between PMs who speak about AI and PMs who construct with AI is smaller than you suppose. It’s measured in hours of hands-on follow, not years of examine.

See you on the opposite facet.

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles