The Growth Podcast

Today’s episode
There is a term Andrej Karpathy coined last year: vibe coding.
We have the same for product management: Vibe PMing.
You describe the problem. The agent pulls the data. Analyzes the chart. Synthesizes the feedback. Drafts the spec. Files the ticket.
That is not theory. That is what I walked through in today’s episode with a principal PM at Amplitude who builds MCP and agent products for a living. He showed it live, on screen, in real time.
If you tune in, you’ll learn the full end-to-end workflow:
----
If you want access to my AI tool stack - Dovetail, Arize, Linear, Descript, Reforge Build, DeepSky, Relay.app, Magic Patterns, Speechify, and Mobbin - grab Aakash’s bundle.
----
Check out the conversation on Apple, Spotify and YouTube.
Brought to you by:
* Amplitude: The market-leader in product analytics
* Pendo: The #1 software experience management platform
* Testkube: Leading test orchestration platform
* Product Faculty: Get $550 off the AI PM Certification with code AAKASH550C7
* Bolt: Ship AI-powered products 10x faster
----
Key Takeaways:1. Claude Code + MCP is the most powerful AIPM workflow today - Connect your analytics tool via MCP, load your product context into a repo, and let the agent do analysis that used to take hours in minutes.2. Deep chart analysis now takes 90 seconds instead of 3 hours - Drop a chart URL into Claude Code, trigger the analyse chart skill, and the agent navigates your data taxonomy, finds anomalies, and hypothesises why metrics changed.3. Automate your entire weekly business review - Point Claude Code at your dashboards Monday morning. Get 3-5 top insights and the one urgent issue to tackle — no manual dashboard scanning ever again.4. Customer feedback synthesis across all channels in one pass - Zendesk, Gong, Salesforce, Slack, app stores all unified. Claude Code navigates the MCP, clusters themes, and surfaces what customers love and hate that week.5. PRDs write themselves from insights - Take the analysis output, point it at your PRD template in Cursor or Claude Code, and get a first draft spec in under 2 minutes. Iterate with command L or command K.6. Skills are the most important Claude Code feature - A skill is just a named prompt with heuristics and tool instructions. It loads only when relevant, preventing context bloat and giving the agent a repeatable workflow.7. The biggest MCP mistake is connecting too many servers - Every tool description burns context. Load only what's relevant to the workflow. Remove or hide tools that aren't being used for a given task.8. MCP is not for complex orchestration — it's for data access - Set the right expectation. MCP connects AI to external systems easily. It's the first step, not the whole pipeline.9. Granola has no MCP, so build a script instead - Frank used Claude Code to write a local script that dumps Granola meeting notes into his product repo. Now he can pull all meeting context with a single at-command.10. The future of PMing is vibe PMing - Chart analysis, dashboard reporting, feedback synthesis, spec writing, and prototyping — all agent-driven. PMs who adopt this workflow now will have a massive advantage in 2-3 years.
----
Related content
Newsletters:
* How to use Claude Code like a pro
* Steal 6 of my Claude skills
* Context engineering
* The AI stack for PMs
* Practical AI agents for PMs
Podcasts:
* How to build an AI-native PM operating system with Mike Bal
* AI evals explained simply with Ankit Shukla
* Advanced guide to AI prototyping with Sachin Rekhi
PS. Please subscribe on YouTube and follow on Apple & Spotify. It helps!


This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.news.aakashg.com/subscribe

Today’s Episode
Designing with AI isn’t about prompting.
Most PMs think they understand AI design because they can write a good prompt. They’re wrong.
Real AI design is about understanding the entire workflow, the system, the constraints, and the behaviors.
Xinran Ma runs Design with AI, one of the top newsletters on AI design. He’s been studying AI design tools for three years. And he hasn’t shared most of this information publicly before.
In today’s episode, we’re going live. We’re building real prototypes. We’re showing you the exact workflows that top 1% designers use.
By the end of this episode, you’ll know the entire workflow from PRD to prototype to product.
----
Check out the conversation on Apple, Spotify and YouTube.
Brought to you by:
* NayaOne: Airgapped cloud-agnostic sandbox
* Pendo: The #1 software experience management platform
* Maven: The cohort-based course platform powering the future of learning
* Bolt: Ship AI-powered products 10x faster
* Gamma: Turn customer feedback into product decisions with AI
----
If you want access to my AI tool stack - Dovetail, Arize, Linear, Descript, Reforge Build, DeepSky, Relay.app, Magic Patterns, Speechify, and Mobbin - grab Aakash’s bundle.
----
Key takeaways:
Key Takeaways:1. AI design covers five areas not just prompts - Prompting, ideation, design/prototyping, workflows, and staying conscious. Most people think better prompts equal better design. That's just 20% of the skill.2. Use Google AI Studio for quick design variations - Upload 2-3 visual references. Describe what you want. Generate three different design directions in 5 minutes. What used to take 3-4 hours now takes 15 minutes.3. Lovable builds functional prototypes in seconds - Describe the experience you want to build. Lovable generates a working prototype in 60 seconds. Not mockups—actual clickable experiences you can test with users.4. Match tools to specific use cases - Custom GPT for effective prompts. Lovable for high-quality prototypes. Magic Patterns for design variations. Google AI Studio for free exploration. Cursor for full-stack experiences. Claude Code as all-purpose best.5. Good design passes four layers not just visual - Visual representation, problem-solving, design principles, and implementation feasibility. Most people stop at layer one. Great design works at all four layers.6. Context matters more than prompt length - Don't say "design a button." Say "design a primary CTA button for B2B SaaS onboarding where users connect calendar. Professional brand." Specificity drives quality.7. Visual references anchor AI output - Upload 2-4 screenshots showing the aesthetic you want. These show AI what "modern and minimal" means to you. The quality difference is massive versus text-only prompts.8. Iteration speed determines final quality - The magic isn't in the first output. It's in the 10th iteration after you've refined and tweaked. Review, identify issues, tell AI how to fix, repeat.9. Always validate with real users - AI tools make generating designs easy. Only users tell you if those designs actually help. Show prototypes to 3-5 users. Watch them try to use it.10. Workflows changed from linear to parallel - Before AI: sequential steps taking weeks. After AI: describe, generate, iterate freely. This is how top 1% designers work now.
----
Where to Find Xinran
* LinkedIn
* Newsletter
* Maven course
Related Content
Newsletters:
* AI Prototyping Tutorial
* AI Prototype to Production
* How to Build AI Products
* Prompt Engineering
* Product Requirements Documents
Podcasts:
* Advanced Guide to AI Prototyping with Sachin Rekhi
* AI Prototyping for PMs
* How to Become an AI PM
* Everything You Need to Know About AI
----
PS. Please subscribe on YouTube and follow on Apple & Spotify. It helps!
If you want to advertise, email productgrowthppp at gmail.


This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.news.aakashg.com/subscribe

Check out the conversation on Apple, Spotify and YouTube.
Brought to you by - Reforge:
Get 1 month free of Reforge Build (the AI prototyping tool built for PMs) with code BUILD
Today’s Episode
Ankit Shukla is BACK after his gangbusters episode, that is my #2 most popular of all time. This time he's diving deep on one of the most important new AI skills for PMs: Evals.
Whether you're working on AI features now or not, this is a skill you want to have an intuitive understanding of. So, I'm building on my library of eval episodes with today's drop.
I've never heard someone explain evals from first principles as intuitively as Ankit has with this one. Hope you enjoy as much as I did!
If you want access to my AI tool stack - Dovetail, Arize, Linear, Descript, Reforge Build, DeepSky, Relay.app, Magic Patterns, Speechify, and Mobbin - grab Aakash’s bundle.
Where to find Ankit Shukla
* HelloPM
* Twitter (X)
* LinkedIn
* YouTube
Related Content
Newsletters:
* AI Evals
* AI Testing
* LLM Judges
Podcasts:
* How to Do AI Evals Step-by-Step with Real Production Data
* The PM’s role in AI Evals
* AI Evals Live
PS. Please subscribe on YouTube and follow on Apple & Spotify. It helps!
email productgrowthppp at gmail dot com for sponsorships.


This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.news.aakashg.com/subscribe

Today’s Episode
Discovery might be the most important core PM skill for building great products.
But most PMs are unprepared to do discovery in AI. PMs run surveys incorrectly, conduct interviews poorly, and end up with poor insights.
Today will give you the roadmap to avoid all those mistakes.
Caitlin Sullivan is a user research expert who runs courses teaching PMs how to do AI-powered discovery. And in today’s episode, she shows you exactly how she does it.
We’re talking live demos. Step-by-step workflows. Real survey data. Real interview transcripts.
This is a masterclass in discovery. The kind that moves the needle.
----
Brought to you by:
Maven: Get 15% off Caitlin’s courses with code AAKASHxMAVEN
Pendo: The #1 software experience management platform
Jira Product Discovery: Plan with purpose, ship with confidence
Kameleoon: AI experimentation platform
Amplitude: The market-leader in product analytics
----
Key Takeaways:
1. Replicate the human process - Good AI analysis mirrors how experienced researchers work: comb through data first, then synthesize. Never jump straight to "give me themes."2. Use multi-step prompting - Load context in one prompt, run per-participant analysis in the next, then verify. Cramming everything into one prompt degrades quality.3. Code before you count - For surveys, apply inductive coding labels to every response before asking for patterns. Skipping this step leads to miscategorized, unreliable results.4. Always audit AI's work - Force the model to re-check its own analysis. It catches contradictions, overexaggerated intensity ratings, and miscoded responses regularly.5. Claude wins on nuance, Gemini wins on frequency - Claude gives more thorough, complete analysis by default. Gemini surfaces top-frequency themes faster but misses smaller patterns.6. Define everything explicitly - Quotes, ratings, emotional intensity levels, contradiction types. If you assume the model shares your definitions, you'll get inconsistent results.7. Markdown files beat raw transcripts - Converting transcripts to structured markdown improves accuracy and helps you work around token limits on non-Max plans.8. Parallelize with Claude Code agents - Set up agent markdown files for interview and survey analysis, then run both simultaneously. Cuts total analysis time in half again.
----
Related Content
Newsletters:
How to Do Product Discovery Right
Advanced Techniques: Continuous Discovery
Customer Interviews: Advanced Techniques
Podcasts:
Teresa Torres’ Guide to AI Discovery
Complete Course: AI Product Discovery
Ultimate Guide to Knowing Your Users as a PM
----
PS. Please subscribe on YouTube and follow on Apple & Spotify. It helps!
If you want to advertise, email productgrowthppp at gmail.


This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.news.aakashg.com/subscribe

Today’s Episode
Most PMs are drowning in tools.
You log into JIRA. Then Figma. Then Confluence. Then Notion. Then Google Analytics. Then Slack.
Twenty different tabs. Twenty different logins. Zero flow state.
Mike Bal runs product at David’s Bridal, a company undergoing massive digital transformation.
And he operates from a single interface.
Cursor and Claude Desktop sit at the center. Everything else connects through MCP and custom integrations.
Research? Manus feeds into Claude. Analytics? Clarity exports into Cursor. Design? Figma pulls directly into his projects.
This isn’t a tool stack. It’s an operating system.
Today, Mike shows you exactly how to build it.
----
If you want access to my AI tool stack - Dovetail, Arize, Linear, Descript, Reforge Build, DeepSky, Relay.app, Magic Patterns, Speechify, and Mobbin - grab Aakash’s bundle.
Are you searching for a PM job? Join me + 29 others for an intensive 12-week experience to master getting a PM job. Only 9 seats left.
----
Check out the conversation on Apple, Spotify and YouTube.
Brought to you by Linear: Plan and build products like the best.
----
Key Takeaways:
1. Operating systems beat tool stacks - Stop logging into 20 different UIs. Build one central interface through Cursor and Claude Desktop that connects to everything. The composable mindset adapts to your needs.
2. MCP changes PM workflows forever - Model Context Protocol lets you connect JIRA, Figma, GitHub, Notion, Confluence through natural language. Check ticket status without opening JIRA. Compare designs without manual cross-reference.
3. Design validation takes 30 seconds now - "Find my Confluence doc about Feature X, load this Figma design, compare them and tell me what I missed." Used to take 1-2 hours of manual comparison work.
4. Manus dominates heavy research - Gives you multiple file outputs: sample CSVs, combined datasets, data sources report, quick start guide, markdown summary. All traceable back to sources. ChatGPT just gives responses.
5. Research must stay external until vetted - The "conspiracy theorist LLM" problem is real. If you automatically feed everything into your system, AI anchors to wrong information. Vet research separately, then bring validated context in.
6. PMs can build what required engineers - Mike built a colorization app for e-commerce in one morning. Migrated content to Sanity CMS in a few hours. All from natural language prompts in Cursor.
7. Context switching kills productivity - Every time you open a new tab, you lose flow state. The operating system keeps you in one interface. The AI handles the context switching for you.
8. Corporate IT restrictions become irrelevant - You already have Cursor or Claude Desktop. You already use JIRA, Figma, GitHub. Connect them through a better interface. No new tool approvals needed.
9. Analytics workflows save massive time - Export Clarity data, upload to Cursor, prompt "analyze drop-offs and create visualizations." Takes 10 minutes vs hours of manual Excel work.
10. AI native PMs think in prompts - "What do I need to do? What are the steps? What tools will help?" Treat AI as an extension of yourself, not a separate tool to learn.
----
Where to Find Mike
* LinkedIn
* Youtube
* Website
----
Related Content
Newsletters:
* AI Product Strategy
* How to Build AI Products
* AI Agents for PMs
* Product Requirements Documents
Podcasts:
* AI Prototyping for PMs
* How to Become an AI PM
* Everything You Need to Know About AI
PS. Please subscribe on YouTube and follow on Apple & Spotify. It helps!


This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.news.aakashg.com/subscribe