Webinar library
Discover and register for live sessions with product managers using AI.
Upcoming webinars
From Raw Calls to a Clickable MVP in One Afternoon
Every AI-for-PM listicle this year says the same thing: drop your interview transcripts into an LLM and get themes in minutes. That part is true, and it's also where most PMs stop. The interesting work happens between "themes" and "a v1 someone can click": - Fixing transcripts that misattribute who said what - Finding where two stakeholders want opposite things - Writing a cut list with reasons - Choosing the one piece worth prototyping In this session I'll walk through the full pipeline I used on a real two-persona discovery project, rebuilt here as a fictional case. You leave with every prompt. **What you will walk away with** - **A 7-step prompt chain** that takes two raw interview transcripts to a scoped v1 and a prototype brief, ready to reuse on your next discovery round - **A way to pick what to prototype:** rank the pieces of your v1 by risk instead of picking the most fun screen - **The "stated vs. revealed" lens:** spot where the personas collide, and the signals a generic AI summary drops **Who it is for** PMs who already use Claude or ChatGPT on research data and have vibe-coded at least once, but haven't chained discovery, scoping and prototyping into one repeatable pipeline.
Run Claude Code Like a Team
Most people use Claude Code like a chat: ask, get code, correct it, repeat. It works for small things and falls apart on anything real. Context gets lost between sessions, Claude invents its own defaults, and two agents edit the same file. In this session I'll show a different way of working: treat Claude Code like a small team. You write the operating manual, Claude plans before it codes, bugs live in a tracker, and sprints run several agents in parallel without collisions. The method was tested on a real project: a web remake of Championship Manager 2, the 1995 football management classic. One person acting as product owner, 12 days, 12 production releases, 26 written plans, 47 tracked bugs (46 fixed) and 966 automated tests. **What we will cover** - **CLAUDE.md as your operating manual:** the six things worth writing down, and how every repeated correction becomes a rule - **Define "correct" before Claude builds:** name your source of truth (spec, design, legacy app) and make Claude cite it - **Project memory:** three files (bugs, plans, sprint log) that let any new session pick up where the last one stopped - **The sprint loop:** plan → overlap check → parallel lanes in git worktrees → one controller merges → honest log - **Users in the loop:** in-app feedback becomes a tracked bug, a fix and a release, often on the same day - **Guardrails:** a person approves anything irreversible, and the logs say plainly what hasn't been verified Then we'll see it live in the project itself. **What you will walk away with** Six habits you can apply to any codebase on Monday morning, plus a CLAUDE.md structure you can copy. **Who it is for** PMs and builders who already use Claude Code (or Cursor) and want to move from one-off prompting to a repeatable process that ships real software.
Never miss a session
Past sessions & recordings
How to nail your next job with Claude Skills
Next-Level Vibe Coding
Vibe coding 101
Claude Co-Work - How to get started
AI Products - Learning about skills, agents commands and more
Ai Product Hub - The basics
What attendees say
“Got More deeper understanding on how the system works with live examples and great explanations”
Yaron
AI Products - Learning about skills, agents commands and more
“The lecture was very interesting and provided both a clear explanation of the topic and practical examples of its application. Ofer delivered the material in a clear, structured, and easy to follow way.”
Raz
AI Products - Learning about skills, agents commands and more