# Interview Script > Crea un guion de entrevista de clientes estructurado con preguntas JTBD, apertura, exploración central y cierre. Sigue los principios de The Mom Test: sin preguntas dirigidas, sin pitch. Fuente: https://skillsagentes.com/skills/phuryn/pm-skills/interview-script Markdown: https://skillsagentes.com/skills/phuryn/pm-skills/interview-script.md Repositorio: https://github.com/phuryn/pm-skills Autor: phuryn Licencia: MIT Actualizado: hace 5 meses Coste de contexto: 79 tok instalada, 1.2k tok al activarse, 1.2k tok con todos los archivos del bundle Bundle: 1 archivo, 5 KB Permisos que pide: ninguno declarado ## Instalación Un skill son archivos markdown: los mismos archivos valen para cualquier agente y lo único que cambia es el directorio de destino, es decir la bandera `--agent`. Añade `-g` para instalarlo en todos los proyectos de la máquina. ```bash # Claude Code npx -y skills add phuryn/pm-skills --skill interview-script --agent claude-code # Cursor npx -y skills add phuryn/pm-skills --skill interview-script --agent cursor # Codex npx -y skills add phuryn/pm-skills --skill interview-script --agent codex # Gemini CLI npx -y skills add phuryn/pm-skills --skill interview-script --agent gemini # Windsurf npx -y skills add phuryn/pm-skills --skill interview-script --agent windsurf # Cline npx -y skills add phuryn/pm-skills --skill interview-script --agent cline ``` ## Qué hace - Genera un guion de entrevista con apertura, calentamiento, exploración JTBD central y cierre - Incluye preguntas de sondeo y técnicas para profundizar en un hilo interesante - Aplica las reglas de The Mom Test: sin preguntas dirigidas, sin pitch, enfocado en el pasado, escuchar más que hablar - Incluye una plantilla de toma de notas por participante (jobs clave, dolor principal, hallazgo sorpresa, etc.) ## Cuándo usarla - Prepararse para entrevistas de usuarios - Crear guías de entrevista - Planear investigación de discovery ## Qué la activa - "Crea un guion de entrevista de clientes para validar esta hipótesis" - "Arma una plantilla de entrevista siguiendo The Mom Test" - "Dame preguntas de sondeo para mi próxima entrevista de discovery" ## Archivos - SKILL.md — 5 KB ## SKILL.md Reproducido tal cual desde phuryn/pm-skills bajo MIT. Esta sección es el documento original y está en inglés. ## Customer Interview Script Create a structured interview script that surfaces real insights, not just opinions. Follows "The Mom Test" principles — ask about their life, not your idea. ### Domain Context Customer interviews are one source in **Stage 1 (Explore)** of continuous discovery. Other sources: stakeholder interviews, usage analytics, data analytics, surveys, market trends, SEO/SEM analysis. The PM needs direct access to users, stakeholders, engineers, and designers — "without proxies." The **Product Trio** (PM + Designer + Engineer — Teresa Torres) should work together on discovery, not just the PM alone. ### Context You are preparing a customer interview script for research on **$ARGUMENTS**. If the user provides files (personas, hypothesis lists, product briefs, or previous interview notes), read them first. ### Instructions 1. **Clarify research objectives**: - What specific questions does the team need answered? - What decisions will this research inform? - What assumptions need validation? 2. **Create the interview script** with these sections: ### Opening (2-3 min) - Introduce yourself and the purpose (learning, not selling) - Set expectations: "There are no right or wrong answers. We're here to learn from your experience." - Ask permission to record (if applicable) - Confirm time available ### Warm-Up: Context & Background (5 min) - "Tell me about your role and what a typical day/week looks like." - "How long have you been doing [activity related to the product area]?" - Goal: Build rapport and understand their context ### Core Exploration: Jobs to Be Done (15-20 min) **Current situation and behavior** (past tense, specific instances): - "Walk me through the last time you [did the thing we're exploring]. What happened?" - "What tools or methods did you use?" - "How long did it take? Who else was involved?" **Pain points and frustrations** (observe, don't lead): - "What was the hardest part about that?" - "If you could wave a magic wand, what would change?" - "What have you tried to solve this? What happened?" **Desired outcomes** (their words, not yours): - "What does 'good' look like for you in this area?" - "How would you know if this was working well?" **Willingness to pay / priority** (skin in the game): - "How much time/money do you currently spend on this?" - "Have you looked for a better solution? What did you find?" - "What would you give up to have this solved?" ### Probing Techniques Use these when you hit an interesting thread: - **"Tell me more about that"** — opens up any topic - **"Why?"** (asked gently, 2-3 times) — gets to root causes - **"Can you give me a specific example?"** — moves from opinions to facts - **"What happened next?"** — follows the story - **"How did that make you feel?"** — captures emotional intensity ### The Mom Test Rules - Ask about **their life**, not your idea - Ask about **the past**, not the future ("Would you use X?" is useless) - **Talk less, listen more** — aim for 80/20 split - **Never pitch** during the interview - Look for **strong emotions** — they signal real pain or delight - **Compliments are noise** — "That sounds cool!" tells you nothing ### Wrap-Up (3-5 min) - "Is there anything I didn't ask that you think is important?" - "Who else should I talk to about this?" - Thank them for their time - Share next steps (if any) 3. **Customize the script**: Adapt questions to the specific product area, persona, and research objectives. Add or remove sections based on the interview length available. 4. **Include a note-taking template**: ``` Participant: [Name / ID] Date: [Date] Key Jobs: [What they're trying to accomplish] Current Solution: [What they use today] Biggest Pain: [Their #1 frustration] Desired Outcome: [What success looks like] Willingness to Pay: [How much they invest / would invest] Surprise Finding: [Something unexpected] Follow-up: [Next steps] ``` Save as markdown. Include both the script and the note-taking template. --- ### Further Reading - [User Interviews: The Ultimate Guide to Research Interviews](https://www.productcompass.pm/p/interviewing-customers-the-ultimate) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course) ## Dónde encaja - Categoría: [Investigación](https://skillsagentes.com/categorias/investigacion.md) — Investigación estructurada, búsqueda de fuentes y síntesis. - Creador: [phuryn](https://skillsagentes.com/creators/phuryn.md) — 0 skills en el directorio - [Todas las skills](https://skillsagentes.com/skills.md) - [Ranking de instalaciones](https://skillsagentes.com/ranking.md) ## Otras skills del mismo repositorio - [Shipping Artifacts](https://skillsagentes.com/skills/phuryn/pm-skills/shipping-artifacts.md): Conjunto de documentación que hace revisable una app construida con IA antes de lanzarla: arquitectura, flujos de usuario/permisos, permisos, variables/secretos y cobertura de tests, más docs condicionales. - [Intended Vs Implemented](https://skillsagentes.com/skills/phuryn/pm-skills/intended-vs-implemented.md): Método para encontrar la brecha entre lo que un sistema debería hacer y lo que el código realmente hace, el tipo de bug que los escáneres genéricos no ven por falta de un modelo de intención. - [Strategy Red Team](https://skillsagentes.com/skills/phuryn/pm-skills/strategy-red-team.md): Hace de red-team de un PRD, roadmap o estrategia: ataca sus supuestos críticos antes de que lo haga la realidad. Defiende y ataca cada afirmación, prioriza por impacto x probabilidad x coste y da el test más barato. - [Swot Analysis](https://skillsagentes.com/skills/phuryn/pm-skills/swot-analysis.md): Realiza un análisis DAFO detallado (fortalezas, debilidades, oportunidades y amenazas) con recomendaciones accionables. - [Value Proposition](https://skillsagentes.com/skills/phuryn/pm-skills/value-proposition.md): Diseña una propuesta de valor detallada con una plantilla JTBD de 6 partes (Who, Why, What before, How, What after, Alternatives) para crear o articular por qué elegir tu producto. --- Skills Agentes · [Índice de páginas en markdown](https://skillsagentes.com/sitemap.md) · [Inicio](https://skillsagentes.com/index.md)