| This publish first appeared on Aman Khan’s AI Product Playbook publication and is being republished right here with the writer’s permission. |
Let me begin with some honesty. When individuals ask me “Ought to I change into an AI PM?” I inform them they’re asking the incorrect query.
Right here’s what I’ve discovered: Turning into an AI PM isn’t about chasing a classy job title. It’s about growing concrete abilities that make you more practical at constructing merchandise in a world the place AI touches all the pieces.
Each PM is turning into an AI PM, whether or not they notice it or not. Your fee circulate may have fraud detection. Your search bar may have semantic understanding. Your buyer assist may have chatbots.
Consider AI product administration as much less of an OR and as an alternative extra of an AND. For instance: AI x well being tech PM or AI x fintech PM.
The 5 Expertise I Truly Use Each Day
| This publish was tailored from a dialog with Aakash Gupta on The Progress Podcast. You could 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 here are the abilities I exploit consistently—not those that sound good in a weblog publish 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 group spent two weeks creating stunning mocks for an AI agent interface. It regarded good. Then I spent half-hour in Cursor constructing a purposeful prototype, and we instantly found three basic UX issues the mocks hadn’t revealed.
The ability: Utilizing AI-powered coding instruments to construct tough prototypes.
The instrument: Cursor. (It’s VS Code however you possibly can describe what you need in plain English.)
Why it issues: AI habits is unimaginable to know from static mocks.
The right way to begin this week:
- Obtain Cursor.
- Construct one thing stupidly easy. (I began with a private web site touchdown web page.)
- Present it to an engineer and ask what you probably did incorrect.
- Repeat.
You’re not attempting to change into an engineer. You’re attempting to know constraints and prospects.
2. Observability: Debugging the black field
Observability is the way you truly peek beneath the hood and see how your agent is working.
The ability: Utilizing traces to know what your AI truly did.
The instrument: 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” will not be actionable. “The context retrieval returned the incorrect doc” is.
Your first observability train:
- Choose any AI product you employ day by day.
- Attempt to set off an edge case or error.
- Write down what you suppose went incorrect internally.
- This psychological mannequin constructing is 80% of the ability.
3. Evaluations: Your new definition of “finished”
Vibe coding works for those who’re transport prototypes. It doesn’t actually work for those who’re transport manufacturing code.
The ability: Turning subjective high quality into measurable metrics.
The instrument: Begin with spreadsheets, graduate to correct eval frameworks.
Why it issues: You possibly can’t enhance what you possibly can’t measure.
Construct your first eval:
- Choose one high quality dimension (conciseness, friendliness, accuracy).
- Create 20 examples of excellent and unhealthy. Label them “verbose” or “concise.”
- Rating your present system. Set a goal: 85% of responses needs to be “excellent.”
- That quantity is now your new North Star. Iterate till you hit it.
4. Technical instinct: Figuring out your choices

Immediate engineering (1 day): Add model voice pointers to the system immediate.
Few-shot examples (3 days): Embrace examples of on-brand responses.
RAG with fashion information (1 week): Pull from our precise model documentation.
Advantageous-tuning (1 month): Prepare a mannequin on our assist transcripts.
Every has completely different prices, timelines, and trade-offs. My job is understanding which to advocate.
Constructing instinct with out constructing fashions:
- Once you see an AI characteristic you want, write down 3 ways they could have constructed it.
- Ask an AI engineer for those who’re proper.
- Flawed guesses educate you greater than proper ones.
5. The brand new PM-engineer partnership
The largest shift? How I work with engineers.
Outdated approach: I write necessities. They construct it. We take a look at it. Ship.
New approach: 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 had been “useful” or not. We disagreed on lots of them. This taught me that I want to begin collaborating on evals with my AI engineers.
Begin collaborating in a different way:
- Subsequent characteristic: Ask to hitch 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: Software setup
- Set up Cursor.
- Get entry to your organization’s LLM playground.
- Discover the place your AI logs/traces dwell.
- Construct one tiny prototype (took me three hours to construct my first).
Week 2: Commentary
- Hint 5 AI interactions in merchandise you employ.
- Doc what you suppose occurred versus what truly occurred.
- Share findings with an AI engineer for suggestions.
Week 3: Measurement
- Create your first 20-example eval set.
- Rating an current 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 Reality
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 primary questions. That’s precisely the place you want to be.
The PMs who reach AI are those who’re snug being uncomfortable. They’re those who construct unhealthy 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 perfect function, or for AI to “stabilize.” The talents you want are sensible, learnable, and instantly relevant.
Choose one factor from this publish, 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 observe, not years of research.
See you on the opposite facet.