Design a non-leading user interview guide

Autor: AILesson9 min de configuraçãoTestado com:ChatGPTRevisado em: 2026-08-28

Resposta rápida

Build a neutral conversation that elicits recent behavior, context, trade-offs, and evidence rather than feature approval. Forneça: Study questions and decision, Participants and ethics, Session constraints. Resultado esperado: A timed interview guide with consent, screening, recent-instance questions, probes, concept boundaries, and observation notes.

1

Adicione seu contexto

Seu texto permanece neste navegador. O AILesson Prompts não o envia para um modelo ou servidor.

2

Seu prompt

Campos não preenchidos permanecem visíveis como marcadores de posição, para que você ainda possa copiar e editar o prompt

Design a neutral user interview guide aligned to the supplied research questions.

Research questions, decision, evidence, hypotheses, unknowns, and concepts:
[study]

Participants, exclusions, recruitment, consent, incentive, privacy, sensitive topics, accessibility, language, and withdrawal:
[participants]

Duration, mode, moderator, observers, recording, artifacts, concept order, tasks, analysis fields, and requirements:
[session]

Allocate time for welcome, informed consent, context, one or more recent concrete instances, current workflow and artifacts, breakdown and workarounds, consequences, variation and counterexamples, concept or task evaluation if approved, and closing. Start with behavior before opinions or future predictions. Use one idea per open question and neutral probes such as “what happened next?” Avoid mentioning the desired answer, asking why in a blaming way, presuming a problem, using praise that signals correctness, or asking whether participants like a solution. When showing concepts, explain their provisional status, counterbalance order where possible, ask participants to interpret and complete realistic tasks, and separate comprehension, usability, value, trust, and preference. Do not collect unnecessary sensitive data. Include permission points, skip and withdrawal paths, moderator cautions, observer rules, exact artifacts to capture, and post-session factual notes versus interpretation. Audit every question for leading premises and direct connection to a research question.
Experimente no Playground
Privado por padrãoA montagem do prompt acontece localmente no seu navegador. Evite colocar informações confidenciais em qualquer serviço de IA, a menos que sua organização permita.

Da entrada ao resultado

Um exemplo prático

Veja como um contexto concreto transforma esta receita em um resultado útil

Entrada real

Study questions and decision
Decision: whether to explore email reminders, in-product ownership cues, or neither for Ready handoffs over 48 hours. Questions: what situations create long Ready states; how roles notice and act; what information enables action; costs and benefits of each concept. Evidence suggests unclear accepters, forgotten status, deliberate waiting, and notification fatigue. Two low-fidelity concepts approved after privacy review.
Participants and ethics
12 UK/Germany active users: requesters, owners, and accepters, half from workspaces with long Ready events and half comparison. Recruitment with existing research consent. No managers interviewing direct reports. GBP 60 equivalent incentive. Avoid collecting customer content; artifacts must be fictional or participant-redacted. Support screen readers, keyboard navigation, English or German. Participants may skip, stop, or withdraw recording consent.
Session constraints
60-minute remote moderated session, one researcher and silent note-taker. Recording optional. Use one recent instance plus two clickable prototypes; alternate A/B order. Capture timestamps, exact phrases under short-quote consent, task actions, errors, and confidence. Stakeholders observe only through separate muted room and cannot message moderator.

Exemplo de saída

0-5 min — Welcome and consent. Explain study purpose without naming a preferred concept; confirm recording separately, short-quote use, fictional/redacted artifacts, accessibility setup, incentive, and right to skip/stop. Observers remain unnamed by role only if approved consent wording says so; otherwise disclose them.

5-10 — Context: “What part do you usually play when work moves from ready to accepted?” “What tools or signals are involved?” Do not ask whether handoffs are frustrating.

10-28 — Recent instance: “Think of the most recent handoff that stayed ready longer than you expected—or, if none, one that moved as expected. Walk me through it from the moment it became ready.” Probes: “What happened next?” “Who knew?” “What did you see?” “What did you do?” “What prevented or enabled that action?” “Was the waiting intentional?” Ask for a redacted artifact only after permission. Capture counterexamples.

28-35 — Variation: “When does this process work differently?” “Tell me about a case where no reminder was needed.” “What information would have changed your next action, if any?”

35-52 — Concepts, order alternated. State: “These are incomplete ideas, not committed features.” Task for each: “Imagine the fictional handoff has been Ready for 52 hours. Show what you think is happening and what you would do next.” Follow with interpretation, actionability, missing information, unwanted consequence, trust, and accessibility questions. Ask preference only after both tasks and require reasoning; do not ask “Would this helpful reminder solve the problem?”

52-57 — Comparison: “In which situations, if any, should neither concept act?” “What would make either option harmful or ignorable?” 57-60 — Recap, correction, questions, withdrawal reminder.

Post-session notes separate participant statements/actions from researcher interpretations and link each to research question. Log concept order, response mode, recording status, task completion, errors, and counterexamples.

Por que isso funciona

  1. 1

    Recent-instance reconstruction yields inspectable behavior rather than polished general opinion.

  2. 2

    Concept tasks separate what people understand and can do from what they say they like.

Verifique o resultado

  • Does every question avoid a preferred premise and map to a research question?

  • Does the guide prioritize recent behavior and counterexamples over prediction?

  • Are consent, privacy, accessibility, withdrawal, observer, and concept-order controls explicit?

Use com confiança

Perguntas frequentes

Respostas práticas sobre quando usar esta receita, o que fornecer e onde a revisão humana ainda é importante

What should I prepare before using “Design a non-leading user interview guide”?

For “Design a non-leading user interview guide,” prepare Study questions and decision, Participants and ethics, and Session constraints. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Design a non-leading user interview guide” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A timed interview guide with consent, screening, recent-instance questions, probes, concept boundaries, and observation notes—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Design a non-leading user interview guide”?

The published test record for “Design a non-leading user interview guide” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Mais maneiras de explorar

Onde esta receita se encaixa

Mantenha o trabalho em andamento