Audience research
Part of Researching marketplace sellers around one decision without turning research into sales
Six rules for neutral marketplace software interviews with verified sellers
Run neutral marketplace software interviews with verified roles, recent events, informed permission, accessible sessions and bounded analysis.
A neutral interview can clarify how a verified England seller handled a particular event, but cannot show how often the issue occurs, establish a budget or prove wider demand. The useful comparison is between practices that invite assumption and practices that ground each answer in a recent event, clear permission and traceable evidence.
Recruitment is limited to a verified England seller operation and authorised staff, decision-makers or adult customers who pass a recent-event screener. Cold sales calls, supplier demonstrations, invented respondents, unsafe live transactions, review solicitation and inference from public profiles stay outside scope. The practices are non-ranked and follow preparation, fieldwork and analysis.
Research date is 6 September 2026. The editorial team received no recruitment fee, referral payment or private findings from any party discussed. UK professional standards and government methods are used only within their stated scope; they do not widen the England seller-recruitment boundary or make interviews representative.
Pair 1: Confirm the person's part in the event
| Weak version | Better version |
|---|---|
| Accept a job title, seller profile or familiar marketplace name as enough proof. That leaves unclear whether the person had authority to speak for the legal seller or actually handled the work under discussion. | Check the legal seller and marketplace account against a recent listing, stock, order, return or refund event. Ask what the participant personally did and which record supports that account. HMRC digital-platform seller guidance offers a narrow reporting definition, not proof of authority. Exclude anyone whose role cannot be confirmed. A recent seller workflow can help keep the event in focus. |
Pair 2: Put consent information first
| Weak version | Better version |
|---|---|
| Ask for agreement before explaining what the session involves, who will see the material or what happens to a recording. Treating participation as permission for later marketing or marketplace contact also crosses the boundary described here. | Before seeking agreement, explain the purpose, activities, observers, recording, uses, recipients, retention, incentive and withdrawal route in an accessible format. The GOV.UK consent guidance says participants should understand these points and be able to stop. Research permission does not authorise marketing or marketplace contact. Keep participant data controls aligned with the information given. |
Pair 3: Start from a recent episode
| Weak version | Better version |
|---|---|
| Lead with whether a hypothetical tool would be useful. That asks for a prediction before the interviewer knows what the seller currently does, which records they use or where the actual difficulty occurs. | Ask about the last qualifying event and trace its trigger, records, hand-offs, exception and finish. GOV.UK interview guidance recommends stories and real examples rather than generalities. Hold back questions about hypothetical tools until the current work is understood. Compare the account with research accounts without treating one interview as evidence of market-wide demand. |
Pair 4: Keep questions open and neutral
| Weak version | Better version |
|---|---|
| Ask a question that presumes the seller's system failed or that automation is wanted. Leading wording can shape the answer and make it harder to distinguish the participant's account from the interviewer's assumption. | Use open prompts such as "What happened next?" or "Which record did you open?" The UK Statistics Authority's qualitative-research ethics guidance explains how leading questions can affect responses and credibility. Keep a versioned guide so interviewers cover the same topics, and use UK rules and ethics as a boundary, not a sales script. |
Pair 5: Make the session workable for the participant
| Weak version | Better version |
|---|---|
| Assume that one format, time or communication method will suit every invitee. Do not infer a disability or diagnosis from a device, role or response, or make the participant adapt without asking what they need. | Ask invitees what format, timing, communication support or assistive technology they need. Government guidance on research sessions with disabled people advises planning around the participant's own setup and communicating directly with them. Offer information in an accessible format, and use accessibility task planning to keep the session centred on their stated needs. |
Pair 6: Keep evidence distinct from interpretation
| Weak version | Better version |
|---|---|
| Turn a researcher's summary into an apparent participant quotation, or report only accounts that fit the expected explanation. That blurs what was said, what records support it and what remains unknown. | Store notes, approved quotations, documentary evidence, researcher interpretation and unknowns in separate fields. The MRS Code of Conduct, binding on MRS members and Company Partners, addresses participant interests and transparent reporting; it is not legal advice. Verify quotations where identification or meaning could be material, preserve contrary cases, and follow a quality checklist. |
After sessions, report invitations, eligible participants, completions, field dates, instrument version and missing roles. Retain counts of refusals and early endings without speculating about the reasons.
Stop if permission cannot be matched to the data, live customer details appear unexpectedly, or a participant is being asked to judge outside their competence. These interviews explain workflows, not England-wide frequency, budget or demand. Recruitment concerns also exclude cold sales calls, supplier demonstrations, unsafe live transactions, review solicitation and inference from public profiles: recruitment concerns.
