Write a neutral, event-based interview guide
Produce a short guide that asks about real events and keeps the preferred solution out of the answer.
- Preparation
- A guide-writing and peer-review session
- Steps
- 6
- Difficulty
- Moderate
- Task
- Remove cues from interview questions
Requires: Write the research question and the assumption most likely to bias the interviewer. Choose a shared review document without participant data.
Uses: Google Sheets
Back to the Task: Remove cues from interview questionsBefore you start
Prepare
- Write the research question and the assumption most likely to bias the interviewer.
- Choose a shared review document without participant data.
Steps
Work through the method
Use the listed inputs and tools. Check the evidence when you need to verify a step.
Anchor the interview in a recent event
Open with a request to describe the last time the participant faced the target situation.
Step details and sources
Why it matters: A concrete event gives the conversation context you can examine.
- Input
- The research question.
- Output
- An opening event question.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner recommends reconstructing a recent workflow from start to finish before evaluating solutions.
First Round Review: EARLY EXPLORATION; workflow script beginning “walk me through the last research project you did”The examples come mainly from software product research.The Forces of Progress framework defines push, pull, anxiety, and habit around a concrete struggling moment and switch.
Jobs to be Done: The Forces of Progress; The Struggling MomentThe framework does not establish any candidate’s forces by itself.
Cover context and behaviour
Ask what triggered the event, what the participant did, which tools were involved, and what happened next.
Step details and sources
Why it matters: Behaviour and context show the current workflow without requiring a proposed solution.
- Input
- The opening event question.
- Output
- A chronological core question set.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner recommends reconstructing a recent workflow from start to finish before evaluating solutions.
First Round Review: EARLY EXPLORATION; workflow script beginning “walk me through the last research project you did”The examples come mainly from software product research.
Remove leading words
Replace yes-or-no wording, praise, criticism, and solution names with open factual questions.
Step details and sources
Why it matters: Leading wording can cue the answer the interviewer expects.
- Input
- The first guide draft.
- Output
- A neutral guide draft.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner advises replacing leading solution questions with neutral questions about behaviour and context.
First Round Review: Collect better data by checking your biasThe source is an edited practitioner interview.
Use one short question at a time
Split questions that ask several things at once. Let the participant answer before asking a follow-up question.
Step details and sources
Why it matters: Short questions make the answer easier to attribute to one prompt.
- Input
- The neutral guide draft.
- Output
- A guide with one idea in each core question.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner advises replacing leading solution questions with neutral questions about behaviour and context.
First Round Review: Collect better data by checking your biasThe source is an edited practitioner interview.
Prepare neutral probes
Add probes for sequence, consequence, workaround, and missing detail without suggesting an answer.
Step details and sources
Why it matters: Prepared probes support comparable interviews while preserving unexpected evidence.
- Input
- The core guide.
- Output
- A separate probe list.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner recommends reconstructing a recent workflow from start to finish before evaluating solutions.
First Round Review: EARLY EXPLORATION; workflow script beginning “walk me through the last research project you did”The examples come mainly from software product research.
Run a bias review
Ask a reviewer to mark every question that reveals the desired product, judgement, or answer.
Step details and sources
Why it matters: The founder’s preferred solution needs an explicit check before the first session.
- Input
- The complete guide and stated assumption.
- Output
- A reviewed guide and a record of removed cues.
Tools in this stepGoogle SheetsEvidence for this step
A practitioner advises replacing leading solution questions with neutral questions about behaviour and context.
First Round Review: Collect better data by checking your biasThe source is an edited practitioner interview.
Success checks
Check the result
- The guide starts from a recent event.
- No core question names or praises the preferred solution.
- The same core guide can be used across the round.
Failure modes
What could go wrong
- Rewrite questions that ask whether the participant would use an imagined feature.
- Record a new spontaneous probe before reusing it in later sessions.
- Treat the guide as a bias check, without claiming that it removes all bias.
Tools
Choose tools
Google Sheets
A shared spreadsheet for source-linked research, decisions, and operating records that people can inspect and correct.
Check fit, limits and pricingSources
Check the sources
Check what each source supports and where the advice has limits.
- First Round Review: How to Know if Your Idea's the Right OneEdited practitioner interview · Publication date unavailable
- First Round Review: A UX Research Crash Course for FoundersEdited practitioner interview · Publication date unavailable
- Jobs to be Done: The Forces of ProgressTraining-provider framework · Publication date unavailable
- Google Workspace: Share files from Google DriveOfficial help documentation · Publication date unavailable