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 click copies it and shows you exactly how to drop it into Contextli.
Next, open Contextli, go to the Contexts page, click Import, choose From JSON, paste, then Import Context. It is ready to use.
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.
Questions people ask
Questions product managers ask about User Interview Script
What is the best way for a product manager to capture interview notes without missing what the candidate is saying?
Stay fully present during the interview, then speak a structured debrief immediately afterward. The User Interview Script context converts your spoken observations into an interview note covering the competencies assessed, key quotes, and your recommendation. You take better notes because you listened better.
What should an interview note include?
It should include the date, the candidate name and role, the competencies or areas assessed, the key observations and quotes, your overall impression, and your recommendation with reasoning. The User Interview Script context structures your spoken debrief to cover these areas consistently across all candidates.
How do I take interview notes quickly between back-to-back interviews?
Dictate a 60 to 90 second spoken debrief into Contextli using the User Interview Script context right after each interview. The context produces a structured interview note in under two minutes. Because the format is consistent, you can compare candidates directly at the end of the day.
How do I share interview notes with a hiring panel after an interview?
Copy the structured interview note that Contextli produces and paste it into your ATS, a shared document, or the hiring channel. Because the output is consistently formatted, panel members can read and compare notes across candidates without reformatting.
How do I add this context to Contextli?
Copy the context on this page, then open Contextli and go to the Contexts page. Click Import, choose From JSON, paste it into the Import from Clipboard window, and click Import Context. It is ready to use in under 30 seconds. If you do not have Contextli yet, you can download it for free first.
Is my voice recording private? Does Contextli send it anywhere?
Your voice recording and the transcription are stored on your device only. Contextli processes your audio locally and does not send your recordings or transcription text to any server. The structured output it produces is text you control, and you decide where it goes.
Can I change what the output looks like?
Yes. Every context in Contextli is a starting point you can edit. Open the context in the app, change the instructions to adjust the structure, tone, or fields, and save. The next time you use it, the output reflects your changes. You are not locked into the default format.
Do I need to install an app to use this context?
Yes. Contextli is a free app. Download it, then copy this context and paste it into the Import from Clipboard window on the Contexts page. The whole process takes about 30 seconds.