Write user interview questions about real creative work
Prepare an interview guide about workshop preparation using recent examples, open prompts, neutral follow-ups, and consent, while avoiding speculative feature voting and invented participant stories.
Ask about recent creative work
An interview can help you understand how people approach creative tasks, what constraints they face, and how they currently work around problems. Ask about specific recent experiences before proposing a product. What happened before your last workshop invites a different kind of account from Would you use an app that organized everything for you.
Use topics and neutral follow-ups
Organize the guide around topics and research questions rather than a script that must be read without adaptation. Use open prompts, then follow the participant's account with neutral requests for detail. Explain the purpose, obtain informed consent, and avoid collecting personal information that the research does not need. Separate what the team has observed, what it has inferred, and what it proposes to do next. These categories can sit close together without becoming interchangeable. A compelling account is still an interpretation unless its evidence is available for review. Keep the original context accessible through the approved project process, and avoid collecting more personal detail than the inquiry needs. Clear distinctions make later disagreement easier to resolve without erasing useful uncertainty.
Prepare a workshop-experience guide
Prepare prompts about finding a workshop, deciding whether it was suitable, gathering materials, and arriving. Add follow-ups such as What did you do next and How did you find that information. Write a note identifying which question each prompt supports. Use a practice interview to detect leading wording before meeting research participants. Walk through one ordinary case and one case that challenges the assumptions. Keep the underlying question consistent so the contrast is interpretable. Note what changes in the artifact and what remains fixed. A rehearsal can reveal preparation gaps and contradictions, but it does not replace the actual research or service evaluation the project needs. Write that boundary beside the example so its apparent completeness cannot be mistaken for evidence.
Follow concrete accounts without steering them
If someone gives a general opinion, ask whether they can recall a concrete occasion rather than treating the opinion as observed behavior. If you describe a proposed feature enthusiastically, you may encourage agreement. If an account seems contradictory, ask for clarification without arguing. The participant's circumstances may differ from the team's assumptions. If the output has no clear next use, revisit its purpose before expanding it. An attractive document that nobody can act on may be missing a decision, an owner, or a review condition. Add the minimum information that closes that gap. Avoid filling the remaining space with general recommendations; make the next step concrete enough that a colleague can carry it forward and report what remains unresolved.
Separate accounts from prevalence claims
Review the guide for leading language, unnecessary sensitivity, and coverage of the research purpose. After actual sessions, separate what was said from your interpretation and avoid presenting a quote as proof of prevalence. Interviews provide contextual accounts that need careful analysis. A useful guide supports attentive inquiry while leaving room for experiences the team did not anticipate.
Worked decision
Ask Tell me about preparing for your last workshop, then follow the account with What did you do next rather than proposing a feature.
References & further reading
Examples and exercises in this guide are original teaching scenarios.
