Write a Jobs-to-be-Done interview script that surfaces the real switching trigger without leading the witness

Write a Jobs-to-be-Done interview script for talking to people who recently switched to (or away from) the product below. The point of a JTBD interview is to find the real trigger moment and struggle that led to the switch — not to confirm assumptions I already have, so every question needs to be checked for leading language before it goes in the script.

PRODUCT AND SWITCH DIRECTION
Interviewing customers who switched away from a spreadsheet-based system to our inventory-management app.

MY CURRENT ASSUMPTION ABOUT WHY THEY SWITCHED
We assume they switched because spreadsheets couldn't handle multi-location stock syncing.

INTERVIEW LENGTH
30 minutes.

STRUCTURE THE SCRIPT IN THIS ORDER
1. A timeline reconstruction opener that asks the person to walk through the actual sequence of events leading up to the switch, starting well before the switch itself — a JTBD interview should establish what was happening in their life or workflow before they even started looking for an alternative, not open with "why did you switch," which invites a tidy retrospective justification rather than the messier real sequence.
2. Struggle-moment questions that probe for the specific moment something became actively painful enough to prompt looking for alternatives — ask what they were doing right before that moment, not what they generally disliked about the old tool in the abstract.
3. A forces-of-progress set covering what pushed them away from the old solution, what pulled them toward the new one, what anxieties they had about switching, and what habits of the old tool they had to overcome — these are four genuinely different forces and deserve separate questions, not one blended "why did you switch" question.
4. A check against my stated assumption — include one question late in the script, phrased neutrally, that would surface disconfirming evidence if my assumption is wrong, rather than a question that could only confirm it.

RULES AGAINST LEADING LANGUAGE
For every question, check whether it presupposes an answer ("wasn't it frustrating when...") or offers the interviewee a category to agree with ("was it mainly the price, or the features?") rather than asking them to generate the category themselves. Rewrite any question that fails this check before including it.

WHAT NOT TO DO
Do not include generic satisfaction-survey questions (rate your experience 1-10) — JTBD interviews are about reconstructing a causal story, not scoring sentiment. Fit the total question count to the stated interview length; do not write more questions than could actually fit.

OUTPUT FORMAT
The script in the four sections above, each question numbered, with a one-line note under any question that was rewritten explaining what leading language was removed.