notebook, office, business, work, computer
Photo by kuanish-sar on Pixabay

Audience research

Part of Audience research for productivity software, from recruitment frame to interviews without selling

Customer interviews: eight neutral questions on real productivity workflows

Use eight neutral interview questions to examine real productivity workflows, buying authority, adoption barriers and evidence needs in English firms.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Editorial Desk.

Start with one completed task, not a pitch for new software. In the illustration here, work leaves its main system, is captured on a paper note, returns through duplicate entry, then receives a final check. That sequence gives the interview a starting point, but it does not prove that anything is wrong.

These prompts are for interviews with actual or likely business software users in England. The eight prompts focus on behaviour, constraints and responsibility for change. They are not satisfaction ratings, pricing questions or usability tasks. Keep the conversation attached to one occasion, rather than an ideal process or a prediction.

The latest task gives the scenario its shape

The participant's latest completed occasion sets the boundaries: the task begins in the main system, takes a paper-note detour, returns through duplicate entry and ends at a final check. Until an interview confirms each event, treat this route as an illustration rather than established research evidence.

Ask for the account in the participant's own terms, then clarify the order and any unclear detail. The aim is to reconstruct a workflow from trigger to finish, not to steer someone towards a preferred tool or label a step as wasteful before its purpose is understood.

The questions are worded so that they do not assume the illustrated route. Use the illustration only to prepare, and never to prompt the participant. Questions 4, 5 and 6 may produce answers such as "no, it all stayed in one system", and that answer is as useful as any other.

  1. What happened on the most recent occasion you completed this task?
  2. What information did you have at the start, and where did it come from?
  3. Who handled the work between its start and its completion?
  4. At any point, did the work move between tools, people or media? If so, when, and what happened next?
  5. How was any information handled outside the main system recorded afterwards, if at all?
  6. What check, if any, was made before the task was treated as complete?
  7. What changed during the latest occasion when the usual route differed?
  8. Who would need to agree to a different route, and what evidence would they need?

Reconstruct the hand-off one event at a time

Follow the task through its detour before deciding what the paper note means. In this worked sequence, each stage is a question for the interview, not an additional fact about the participant or their workplace.

  1. Situation:establish the completed task and where its account begins.
  2. Check:ask whether the work left the main system and, if the participant says it did, how that step worked and how the information returned.
  3. Finding:record a note, duplicate entry or final check only if the participant confirms those events.
  4. Action:leave the reason for the detour open and ask what evidence would support a different route.

Ask why the note is used before describing it as a hidden software cost, a speed measure or a response to a client requirement. A verbal explanation or blank example can be sufficient when a real record would expose confidential details. Do not request customer or employee data merely to make the route easier to visualise.

Who Touched the Work

  1. Operator starts the task
  2. Reviewer checks the output
  3. Approver signs off
  4. Recipient receives the work
  5. Hand-off by message, spreadsheet or meeting

The supported finding remains narrow: the account includes a paper note, duplicate entry and a final check. It does not show why the note is there or whether the route works well. Record the event first; if a participant describes a benefit, ask how they know rather than turning recollection into measurement.

Keep the finding smaller than the explanation

The sequence confirms only what the participant describes. A detour may serve a requirement that is not visible in the route alone, so its presence does not establish that the main system is defective or that replacing it would improve the task.

Separate direct observation, participant recollection and researcher interpretation in the notes. A claim that the process saves time or prevents errors is not a measured result unless the interview establishes how it was assessed. Compare contrasting cases before making wider claims, using a consistent review protocol.

Keep unusual cases separate from the normal route. Ask what changed the last time the normal route differed, but treat an urgent request, staff absence, failed integration or unusual customer condition only as a prompt unless the participant says it happened. The interview should distinguish the described occasion from examples offered to help someone remember.

Choose a follow-up that can be tested

The next move is to document the known sequence and leave its cause unresolved. Before proposing a change, identify who has responsibility and what evidence they would need; interest in a new route does not establish authority over the budget (a budget template lists the cost lines), security review, contract, implementation time or final acceptance.

For the illustrated route, record who could approve a different process and what proof a trial would require, such as an export test, security information or evidence that the old process could continue during transition. Put unanswered points in an assumption register, not in a sales forecast.

Planning should state the research objectives, how notes or recordings will be handled, how informed consent will be collected and how much analysis time is allowed. The GOV.UK Service Manual's user research guidance supplies a reference. For another sample, consult official participant-recruitment guidance rather than treating this illustration as representative.

Notes may contain personal information. Explain collection and use, provide privacy information, minimise what is recorded (data minimisation under UK GDPR Article 5), restrict access with clear access controls and set deletion arrangements. State the lawful basis and supplier arrangements in the research plan, and obtain qualified advice about the organisation's circumstances. For further context, consult ICO guidance on data protection impact assessments.

Carry the scenario's rules into later interviews

The practical rules are to stay with a recent event, trace each hand-off, ask what a detour is for, distinguish interest from authority and finish by recording evidence needed for change. Reuse the discussion topics across sessions, while following relevant details when they emerge.

If colleagues share the task, consider interviewing them together so hand-offs can be examined rather than separately reconstructed. A participant may suggest other roles for a later round, but that does not establish that those people will buy or approve a change. Keep any proposed trial tied to the evidence the participant actually describes.

One interview cannot establish that the same route or requirements apply to everyone. After each session, keep events, recollections and interpretations distinct; do not invent quotations, turn one explanation into a measured result, or report a frequency the recruitment and method cannot support.

More in Audience research