בית
למידה
קורסים
וובינרים
עוד
PM × AI
בוחר לך את הצפייה הבאה
למידה
קורסים
שירותים
וובינרים
EN
עב
צור קשר
ניווט
למידה
כל התוכן
רוב התוכן כתוב באנגלית.
← חזרה למפה
כל התוכן
חיפוש
הכול
מאמרים
סרטונים
סקילז
נושאים
AI Basics
AI for PMs
Career
Claude
Claude Co-work
Claude Co-Work
Claude Code
Claude Skills
Discovery to MVP
Git
Idea to MVP
Job Hunter
Prioritization
Product Builder
Product Discovery
Product Management
Product Sense
Roadmap
Skills
Vibe Coding
Webinar
Webinar recording
9 תוצאות
החדשים
א–ת
סקיל
discovery-to-mvp
Takes the PM through the discovery pipeline one step at a time, from raw customer interview transcripts to a scoped v1, a prototype brief, a built prototype and an honest critique, showing the results of each step and stopping for the PM's decision before the next.
סקיל
interview-guide
Writes a discovery interview guide before customer or stakeholder calls — learning goals, the riskiest assumption behind each, and event-anchored questions per persona, plus recording setup that makes later synthesis reliable.
סקיל
transcript-reconcile
Cleans and merges one or two auto-generated transcripts of the same call into a single trustworthy transcript with correct speaker attribution, glossary fixes, numbered turn IDs and a log of every judgment call. Use before any interview synthesis, when transcripts come from Zoom, Meet, Otter, Granola or similar, when speaker labels look wrong, when two transcripts of one call disagree, or when a transcript needs translating.
סקיל
persona-extract
Pulls one persona's evidence out of a merged interview transcript — pains with verbatim quotes and severity, workarounds, numbers, prompted vs unprompted signals, stated vs revealed gaps, what must not change, and conspicuous silences — every line tied to a turn ID. Use after transcripts are cleaned, when someone asks what a customer or stakeholder "really said", or before comparing personas.
סקיל
persona-collide
Compares two or more persona extracts to find where people want opposite things, tell different stories about the same event, or both assume someone else owns a step — including a workflow map with an owner for every step and a list of what nobody mentioned.
סקיל
problem-framing
Turns discovery evidence into a solution-free problem statement under 80 words, compares it with how the original brief framed the problem, offers rejected alternative framings with reasons, and defines what "solved" would look like per persona. Use after synthesizing interviews and before scoping, or when someone asks "what problem are we actually solving" or suspects the brief asked for the wrong thing.
סקיל
mvp-scope-cutlist
Scopes a v1 from a framed problem and discovery evidence — what v1 does, what it explicitly doesn't, a cut list where every cut has a reason, a cost and a revisit trigger, and an adoption plan for getting busy users off their current channel. Invites and handles the PM's pushback.
סקיל
prototype-brief
Ranks a v1's assumptions by risk and testability, picks the single riskiest one a prototype can test, and writes a build-ready prototype brief — one flow, realistic mock data drawn from the interviews, what's real vs faked, success criteria, a user test script and a paste-ready build prompt. Use after scoping and before building, or when someone asks "what should we prototype first".
סקיל
prototype-build-critique
Builds the single-flow prototype described in a prototype brief and then critiques the proposal and prototype as a skeptical head of product — is the "why" clear for the customer and the business, does the prototype test the assumption, which sentences sound AI-written, and what to cut.