Write Interview Questions Without Assuming Answers

Ask questions that allow the source to establish what happened before asking them to explain a result. A proposed change is not an implemented change, and an implemented change is not proof of success. Keep those distinctions inside the guide, where they affect the next question.

This tutorial ends with the actual proposed interview instrument. Mira and the reading circle are invented teaching material. No person has been contacted, no interview occurred and no answer or agreement is supplied.

Read the Whole Background Packet

B1

In this fictional planning note, Mira proposes moving the reading-circle notice from the paper board to the monthly handout.

B2

The note gives no reason for the proposal and does not say the move happened. It supplies no attendance figures, participant preference, comparison, access assessment or result.

B3

The reporting purpose is to understand Mira's proposed change, establish its status and ask what evidence, if any, informs the choice. The exercise supplies a proposed organizer interview as a reporting method, not an actual contact route, accepted interview or reply.

The packet supports referring to Mira’s proposal and asking its current status. It does not support asking why an improvement happened, attributing a motive or assuming everyone prefers the handout. A detailed question can remain open to an answer of “not implemented” or “not compared.”

Find the Answers Hidden in the Questions

Why did your successful move to the handout increase attendance?

Unsupported premises:

• The move happened.

• It was successful.

• Attendance increased.

• The move caused that increase.

Repair: Ask the proposal's current status first, then ask about any actual evidence without asserting a result or cause.

When did you realize everyone disliked the paper board?

Unsupported premises:

• Everyone disliked the paper board.

• Mira came to that realization.

Repair: Ask what prompted the proposal and whether any participant views were actually collected.

How much easier is the handout for every reader to use?

Unsupported premises:

• The handout is easier.

• Every reader shares that result.

• A measured or reported comparison exists.

Repair: Ask whether the two approaches have been compared and what that comparison can establish.

A softer tone alone would not fix these premises. “Could you explain your successful move?” still asserts success. Repair the question’s starting assumption, then make any follow-up depend on what the source actually establishes.

Use the Complete Proposed Guide

Opening

This is a proposed guide for a fictional interview, not a record of an interview. The planning note says you propose moving the reading-circle notice from the paper board to the monthly handout. Is that an accurate description of your proposal, and what is its current status?

Q1: What change are you proposing, and which parts are still undecided?

Conditional follow-up — If Mira confirms an implementation: What was actually changed, when, and what record can establish those details?

Keep this boundary: Do not call the move completed if only the proposal is confirmed.

Q2: What prompted the proposal?

Conditional follow-up — If Mira mentions participant feedback: What feedback was collected, from whom, and what wording or record may be checked? Were other views recorded?

Keep this boundary: Do not turn an explanation into everyone's preference or invent a motive if none is given.

Q3: Have you compared the board and handout for this purpose?

Conditional follow-up — If Mira describes an actual comparison: What did you compare, how was it examined, and what did it show or leave unknown?

Keep this boundary: If no comparison exists, report that limit rather than asking how much better the handout performed.

Q4: What questions about finding or using the notice remain unresolved?

Conditional follow-up — If Mira describes an actual access concern or assessment: What is the specific concern or finding, what supports it, and whose situation does it cover?

Keep this boundary: Do not infer an accessibility result or a result for every reader from a proposal.

Closing

What should I clarify or check before describing this proposal? Are there records you can identify for any factual statements, and what questions do you prefer not to answer? Any actual agreement about recording, attribution or use would need to be established in the real reporting task; this guide supplies none.

Keep Questions Separate From Evidence

The guide asks for status, reasons, comparisons and unresolved questions. It does not contain findings. If a source later supplies an answer, record that actual answer and the evidence it identifies; do not replace it with a more convenient response implied by the original question.

Conditional follow-ups belong after the condition is met. Without a comparison, the guide cannot ask how much better the handout was. Without participant feedback, it cannot attribute a universal preference. The planned interview also supplies no consent or access arrangement by itself.

If the Plan’s Attribution Is Missing

Only an unattributed note saying handout idea is supplied.

The changed packet does not establish that Mira proposed this change. Do not address Mira as if authorship and plan are already confirmed.

Establish the proposal and its source first; use an opening such as What notice-distribution change, if any, are you proposing? only in an actually authorized reporting task.

Keep the reader’s question in your article brief, develop the surrounding blog post, and use the blogger’s topic guide when choosing what the article should answer.

For your own guide, keep the actual background beside every proposed question. Mark what each question assumes, remove assumptions the packet cannot support, and state the conditions that would make a follow-up appropriate. The finished guide should make room for an unexpected answer rather than write that answer in advance.