Interview recovery and handoff / 访谈纠偏与交接
Choose the objective before the session. Discovery reconstructs recent real behavior; usability testing observes a defined task; sales/support answers adoption questions. They can share a meeting, but label the transition and do not score a persuasive demo as unassisted usability success.
| Trigger | Recovery | Record |
|---|---|---|
| Host explains features at length | Ask “What were you doing the last time this happened?” | User task, current workaround, actual impact |
| User asks product questions throughout | Acknowledge and note the question; offer to answer after the research segment, unless it blocks participation | Unresolved concern, agreed follow-up |
| Host operates the demo | Invite the user to attempt the agreed task; help only when needed, noting the intervention | Action, hesitation, error, assistance and result |
| No real task is defined | Ask about the user's product/workflow and select a representative task together | Why this task represents their needs |
Example rescue: “这个问题我记下了，稍后单独回答。先回到你最近一次处理这件事：当时具体做了什么？” Do not ignore material safety, cost or consent questions to retain control of the interview.
Before a usability test, explain prototype limitations and use a suitable sandbox where possible. Screen sharing and recording are optional and consensual. A research invitation does not authorize production integration, financial transactions or sharing private data. During the task, avoid narrating advantages; ask what the user expects and observe what they do.
Separate: cannot understand (expression/interface); understands but does not need it (value/persona); needs it but cannot adopt (capability, access, input or integration). A demo can test understanding and navigation; claims of time saved or business outcomes need real-use evidence.
Evidence and follow-up
Keep user quotation/timecode, task, observed action, host prompt, blocker, current workaround and proposed solution in separate fields. Handoff clips include start/end time, consent scope, redactions, issue owner, observable acceptance condition and revisit date. A clip index is often more usable than an unexplained full recording.
Re-test the changed task with an appropriate participant, ideally including the person who encountered it. Tell users “fixed” or “scheduled” only after checking the actual state. Record a proposed trial, an agreed trial and a completed action separately. Willingness-to-pay statements and requests for more credits are clues, not payment.
Sampling and evidence strength
Choose participants for the decision: paying, heavy-use, new, churned and non-adopting users answer different questions. Start with a manageable batch and reassess gaps and counterexamples; no fixed interview count or conversion percentage certifies PMF. Do not manufacture feature requests to meet a quota. A participant who does not need a change can supply valuable counterevidence.
Compensation pays for time, not favorable answers; disclose and record it. Do not treat an incentivized interview as invalid by default, or all free-user feedback as useless. Historical purchases and a clearly scoped paid offer are stronger pricing evidence than a hypothetical yes.
Facilitator exercise (constructed, not a customer result)
Bad: “Our integration is easy; let me show all its advantages.” Better: “What are you trying to charge for? Please try configuring that in this test environment.” Acceptance: the researcher identifies whether the person can complete the task, records assistance, and distinguishes an onboarding blocker from an unsupported product promise. No invented conversion result.