Aakash GuptaComplete Course: Claude for PMs (Cowork + Code + Dispatch)
At a glance
WHAT IT’S REALLY ABOUT
How PMs use Claude Cowork, Code, Dispatch for 10x workflows
- The speakers argue traditional web chat is now a poor default because it cannot persist work across devices, smoothly switch modalities (files → code → artifacts), or maintain long-running, resumable workflows.
- Cowork is positioned as the “real work” surface for PMs—handling files, multi-step plans, parallel sub-agent execution, connectors (MCP), and generating polished artifacts like slide decks and infographics.
- Claude Code is presented as essential for PMs because product work increasingly touches codebases and complex file hierarchies, and Code offers IDE/terminal-native affordances (repo browsing, hooks, codebase tooling) that Cowork lacks.
- They describe building a “second brain for agents” using a lightweight CLAUDE.md plus domain-indexed knowledge files, where the system continually converts examples into rules/hypotheses and updates them via feedback loops.
- Dispatch and Web Sessions enable remote, asynchronous work—running multiple background tasks from mobile/desktop—while browser automation should favor token-efficient tooling (e.g., Vercel Agent Browser) over screenshot-heavy Chrome MCP.
IDEAS WORTH REMEMBERING
5 ideasTreat chat as a last-mile scratchpad, not your main workspace.
Chat is fine for quick one-offs (e.g., grammar checks), but it breaks when you need continuity across devices, long-running tasks, or switching from discussion to files/code artifacts without reloading context.
Use Cowork when the work touches real files or requires multi-step execution.
Cowork can plan and execute sequential steps (e.g., deduping and sorting invoices by month) and produce tangible outputs (PPTX, PDFs, HTML infographics) directly in a project/folder context.
Adopt skills as reusable “procedures,” and rely on progressive disclosure.
Skills load via short descriptions and only expand into detailed instructions when relevant, letting you maintain many capabilities without bloating every prompt; use slash commands when you need deterministic activation.
Iterate skills like you iterate evals: find failure modes, then rewrite the procedure.
Instead of memorizing better prompts, capture feedback after real usage and have Claude refactor the skill from first principles so the same mistake doesn’t recur—this is framed as one of the highest-ROI activities.
PMs can’t avoid Claude Code because engineers and codebases are part of the job.
Cowork is not optimized for navigating large hierarchies or repositories; Code provides explorer-style browsing, codebase-aware tooling, and terminal command execution needed for debugging, instrumentation, and building systems.
WORDS WORTH SAVING
5 quotesThere's no good reason to talk to Claude just over a normal web chat anymore
— Aakash Gupta
Most people stay in chat forever. That's like using Photoshop only to crop photos.
— Pawel Huryn
Product managers must understand technology. They must get comfortable with, uh, tools that previously were designed for engineers traditionally, so like the terminal.
— Pawel Huryn
You cannot be a product manager who only interviews customers and creates items in the product backlog.
— Pawel Huryn
There's no excuse to walk into a meeting with a bad presentation anymore. You basically get a McKinsey-level output in a minute or two
— Aakash Gupta
High quality AI-generated summary created from speaker-labeled transcript.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome