conduct-user-interview

Guides live semi-structured user interviews from consent through probing to post-session debrief.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill conduct-user-interview-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conduct-user-interview
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/conduct-user-interview
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill conduct-user-interview-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Live user interviews fail in predictable ways: facilitators lead witnesses, fill silences too early, accept surface answers, and let observers derail rapport. This Skill encodes the full facilitation method so every answer traces to real recalled experience instead of polite speculation. ## Core Features & Use Cases - Full session arc: Pre-session checklist, consent and opening script, rapport warmup, broad-to-narrow funnel, closing, and a mandatory 30-minute debrief with a structured output template. - Probing repertoire: Named techniques (echo, boomerang, Columbo, neutral expand, significance, silence) with a decision tree for choosing the right probe per answer type. - Live mistake recovery: Concrete fixes for leading questions, terse or rambling participants, observer interruptions, and time overruns. - Use Case: You have a discovery interview tomorrow and stakeholders want to sit in. Use this Skill to brief observers on back-channel rules, run the funnel with neutral probes, and produce a debrief with verbatim quotes and coverage gaps. ## Quick Start Help me prepare for and run tomorrow's 45-minute discovery interview with a participant about how they book salon appointments, including an observer briefing and a post-session debrief template.

Frequently Asked Questions about conduct-user-interview

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

FAQPage Schema
How do I run a user interview without leading the participant?

Open questions with how, what, or tell me about, and avoid did/was/is phrasing except for factual confirmation. Use the participant's own words, probe with silence and echo techniques, and never supply your hypothesis or vocabulary mid-answer.

What probing techniques work best in user research interviews?

Six core probes: echo (repeat their key phrase), boomerang (return their question), Columbo (trail off naively), neutral expand (tell me more), significance (why does that matter), and silence (wait 5-10 seconds). Try silence first after every answer.

What is the difference between a user interview and a usability test?

Interviews capture what people say — attitudes, memories, and self-reported behavior. Usability tests capture what people do while attempting tasks on a product. If the question is whether people can use something, moderate a usability session instead of interviewing.

How do I handle stakeholders observing my user interview?

Brief observers before the session: stay silent, mute cameras, and send questions to a back channel. Cap visible observers at one or two, filter and rewrite their questions neutrally, and ask them yourself at the end of the session.

Why shouldn't I ask participants if they would pay for a product?

People cannot predict their own behavior, so prediction questions produce unreliable data. Ask about past behavior instead — when they last did the related activity and what happened — and corroborate claims with behavioral data like logs or observation.

What should I do when a participant gives one-word answers?

Terse answers mean you narrowed the funnel too fast. Climb back up to a broad grand-tour question, re-warm rapport, slow your own pace, and use comfortable silence to invite longer responses.