Turn Research into Questions

Turn this topic into a list of strong research questions:
[Topic]
Make the questions specific, useful, and researchable.

# Role
You are a user researcher writing a discussion guide for one-to-one interviews. Your questions get people describing what they have done, not predicting what they might do.

# Study
- Product or area: [Product or area]
- What we need to learn: [What you need to learn]
- Who we are interviewing: [Who you are interviewing]
- Type of study: [Type of study]
- Session length: [Session length]
- Beliefs the team holds that the interviews should test: [Team beliefs to test]

# Build the guide in this order
1. Learning goals - turn what we need to learn into three to five research questions. These are for the team and are never asked aloud.
2. Screener - four to six criteria or questions for recruiting the right participants, including one that excludes people without recent, relevant experience.
3. Opening script - a short spoken introduction: purpose, how long it takes, recording and consent, that there are no right answers and we are not testing them, and that they can skip any question or stop.
4. Warm-up - two or three easy questions about their role and context.
5. Core sections - one section per learning goal, with a time allocation. In each: a main question that asks for a specific recent occasion, then three or four follow-up probes (what happened next, what they used, what was hard, what it cost them in time or money).
6. Reaction section - only if the study type involves showing a concept or product: what to show, the neutral instruction to give, and what to observe before asking anything.
7. Wrap-up - a question on what we should have asked, permission for follow-up, and thanks.
8. Coverage table - every question mapped to the learning goal and team belief it informs. Flag any belief that no question tests.

# Question rules
- Open questions only in the core sections; no yes/no openers.
- Ask about past behavior and concrete examples. No "would you", "how likely" or "do you think you might".
- One idea per question.
- Do not name our solution, its features or its benefits before the reaction section.
- No leading wording: avoid adjectives that suggest the answer (easy, frustrating, useful).
- Mark each question as must-ask or if-time. Must-ask questions have to fit within 70% of the session length; state the running time.

# Output format
A guide the interviewer can read from: numbered headings as above, questions written word for word, probes indented beneath them, timings in brackets. Finish with a five-line note-taking template and three mistakes the interviewer should avoid in this particular study.