entrevista-usuario

Guides story-based user interviews with bias mitigation and JTBD analysis.

Updated May 31, 2026
One-click install
npx skills add https://github.com/ithaloazevedo/pm-loadout --skill entrevista-usuario-ithaloazevedo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: entrevista-usuario
Source: https://github.com/ithaloazevedo/pm-loadout/tree/main/.agents/skills/entrevista-usuario
Command: npx skills add https://github.com/ithaloazevedo/pm-loadout --skill entrevista-usuario-ithaloazevedo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often run user interviews that produce shallow, biased, or hypothetical answers instead of real behavioral evidence. This Skill structures interviews around past-tense customer stories so you uncover genuine needs, pain points, and Jobs-to-be-Done. ## Core Features & Use Cases - Story-Based Question Design: Enforces past-tense, behavior-focused questions while banning hypothetical, leading, or opinion-based prompts. - JTBD and Bias Lens: Captures functional, emotional, and social job dimensions and flags interpretation biases before and after each interview. - Post-Interview Snapshots: Produces structured summaries with key quotes, opportunities, surprises, and extracted scenarios containing persona, means, motive, and simulation. - Use Case: Before a discovery sprint, run five customer interviews using this guide to populate an opportunity solution tree with verbatim quotes and validated user needs instead of assumptions. ## Quick Start Use the entrevista-usuario skill to help me design and run a story-based user interview about how customers currently handle expense reporting.

Frequently Asked Questions about entrevista-usuario

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a user interview for product discovery?▼

Ask story-based, past-tense questions like "Tell me about the last time you tried to accomplish X" instead of hypotheticals. Listen for emotional and social dimensions, wait 3-5 seconds after responses, and close by asking what you did not ask about.

What questions should I avoid in user interviews?▼

Avoid hypothetical questions ("Would you use..."), opinion questions ("Do you think X is good?"), leading questions, abstract rating scales, and feature requests. These produce unreliable answers because people describe intended rather than actual behavior.

How do I apply Jobs-to-be-Done in customer interviews?▼

Listen for hiring and firing language, then probe the functional, emotional, and social dimensions of each story. Ask what users felt and what others thought, since JTBD spans more than the functional task.

How do I reduce bias when interpreting interview results?▼

Run a bias check before designing questions, watch for the say-do gap by asking the same question multiple ways, and record biases to watch for in each post-interview snapshot. Cross-check stated behavior against actual past events.

What should I document after a user interview?▼

Capture 3-5 verbatim quotes, identified opportunities, surprises, JTBD dimensions observed, and interpretation biases. Extract scenarios only when persona, means, motive, and simulation elements are all present in a story.