Who this is for
PMs, designers, and researchers who want interview questions that surface real behavior, not leading questions that confirm assumptions.
The moment this saves you
I run user interviews and accidentally ask leading questions like don't you think this is useful, so users just agree with me, and I walk away with false validation instead of real insight.
See it work
Messy spoken thought in. A clean, structured artifact out.
Building an interview script to understand how people currently manage their team's tasks before we build our feature. What I want to learn, how they actually do it today, what's painful, and whether they'd even change. I do not want to pitch our solution, I want to understand their world. I'm worried I'll lead them. Topics, walk me through the last time they assigned work to their team, what tools they use and why, the most frustrating part of their current process, and what they've tried before. I specifically want to hear about real recent instances, not hypotheticals. Avoid asking would you use a tool that does X.
User interview script, June 5, 2026
Goal: Understand how they manage team tasks today, no pitching.
Warm-up
- Tell me about your role and your team.
Behavior (real, recent instances)
- Walk me through the last time you assigned work to your team. What happened?
- What tools did you use, and why those?
- What was the most frustrating part of that?
History
- What have you tried before to solve this? Why did you stop?
Avoid: hypotheticals and "would you use a tool that..." questions.
The workflow
Record a voice note
Hit the hotkey and talk, no formatting, no typing.
Tag it with this context
Contextli shapes your words into the structured output above.
Find it later
Everything's searchable and organised by context.
Pull it into Claude or ChatGPT
Bring your contexts straight into your AI tools with the Contextli MCP.
Your raw recording and transcription stay on your device, so you can always go back to the original.
The prompt behind this context
I'm going to talk through what I want to learn from a user interview. Turn it into a non-leading interview script: a bold "User interview script, [today's date]" heading, an italic goal line, then questions grouped under bold sections (Warm-up, Behavior, History, etc.). Phrase every question to surface REAL past behavior and specific recent instances, never leading or hypothetical ("would you use..."). Base questions only on the topics I mention. End with an italic "Avoid:" line listing the traps I flagged. Don't invent topics. Output only the script.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Use this context
One tap adds it to your clipboard. Open Contextli and paste to add it.
Next, open Contextli, Contexts, Import, paste.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Your raw recording and transcription stay on your device, so you can always go back to the original.
Related contexts
User Research Observation
Right after a user interview, your memory starts smoothing the awkward truths into what you hoped to hear. Speak it now, what they actually said and did, where they got stuck. You get a clean observation note that keeps the real signal, not your wishful version of it.
Interview Question Prep
You're interviewing a guest or expert and you don't want generic questions. Say what you're curious about and what you want the audience to learn. You get a sharp, ordered question list, so the conversation goes somewhere instead of staying on the surface.
Product Demo Feedback
You watch a user try your product and see exactly where it breaks down, then the meeting moves on and the insight gets diluted. Speak what you observed right after. You keep the raw signal, the confusion, the workaround, the delight, so the team fixes the real thing.