A useful customer interview starts with the decision the customer faced. Ask what they were trying to accomplish, what alternatives they considered, and what changed during the work. Let them describe the result in their own words before choosing a headline or asking for a particular number. The resulting story can explain a buying decision and a working process even when the available outcome is qualitative.
Prepare questions around the customer’s decision
Before the call, agree on the topic, participants, intended audience, and review process. Ask which person can explain the original problem and who can check any operational or financial figures. A product user may know how a workflow changed, while a manager may hold the reporting definitions. Invite both perspectives when they matter to the story.
Prepare open questions that allow the customer to describe an unexpected result:
- What prompted your team to reconsider the previous process?
- Who was involved in the decision, and which constraints mattered?
- What did the earlier workflow look like, and how did you know where it needed attention?
- What did you implement first, and what adjustments did you make afterward?
- What changed for the people doing the work? What stayed difficult?
- Which records could help us check the dates, measures, or examples you mention?
If someone says a task became faster, ask which task was measured and over what period. A reliable measurement may be unavailable.
Capture a baseline that can be checked
A baseline describes the earlier situation in terms the customer recognizes. It can be a documented measure, a workflow description, or a combination of both. Record who supplied it and whether the description refers to the whole organization or a particular team. If the customer provides a figure, ask how it was collected and which work was included.
Write the comparison period beside the later result. Check whether the people, definition, and unit are consistent. A monthly count from one department may answer a different question from a weekly count across the company. Keep both records if they are relevant, and ask the customer to reconcile them before writing a comparison.
Ask about other changes made during the same period. A new internal approval process, extra staff, or a changed customer mix may affect how the team interprets its experience. The customer can describe what they observed while the article preserves uncertainty about the contribution of each change.
Follow a fictional interview through review
Imagine a fictional software customer, Northline Studio, which uses a SaaS platform to coordinate client approvals. An interviewer arrives expecting a story about a shorter approval cycle. The operations lead instead explains that the initial problem was uncertainty about which version of a document was awaiting review.
The lead says the team introduced a shared approval queue in April. Around the same time, it also changed its internal review schedule. A manager recalls that approvals seemed quicker, but the team’s old spreadsheet does not consistently record when each request started. The new platform records a different start event. The two figures cannot support a clean before-and-after comparison without further work.
The interviewer asks for a concrete example. The lead describes a typical handoff in which a project manager now checks the queue and asks the named reviewer to respond. The customer confirms that this made outstanding requests easier for the team to locate, although some approvals still require discussion outside the platform. The editor labels the scenario as an illustration of the team’s workflow and avoids presenting it as a measured time saving.
For review, the editor sends the lead a passage describing the earlier problem, the April rollout, the new queue, and the unresolved measurement issue. The manager confirms the dates and clarifies which team used the process. The resulting draft explains the decision and the observed workflow change without attributing an unmeasured speed improvement to the platform.
Preserve attribution through editing
Keep an interview note beside each material statement. Identify whether it came from a participant, an internal customer record, or the writer’s explanation. When paraphrasing, retain the speaker’s conditions and degree of certainty. A participant’s impression can be valuable when it is presented as their experience.
Check quotes against the recording or notes and send them with surrounding context for review. Update source notes when the customer corrects a detail, and resolve differences between sources.
Give the customer a precise approval request
Send the draft passages that name the customer or describe its work. Ask reviewers to check names, roles, dates, product details, numbers, and context. Identify where a quote will appear and what edits need another review. Keep a record of the approved wording and the supporting material under the terms agreed with the customer.
Treat permission to publish a quote or use a logo as a separate question from factual review. An operations lead may confirm a workflow while another contact handles brand permissions. Note the right contact and the status of each request before the story is published.
Frequently asked questions
What if the customer has no numerical result? Ask for a concrete description of the decision, rollout, and observed workflow. A qualitative account can be useful when it identifies who observed the change and avoids an unsupported numerical claim.
Can we compare figures collected in different ways? First document the units, dates, populations, and collection methods. Ask the customer whether a comparable view can be produced. If it cannot, describe the figures separately with their conditions.
Should we remove a difficulty the customer mentions? Discuss its relevance and accuracy during review. A continuing limitation can help readers understand the implementation and the customer’s decision, provided the customer agrees to the wording and context.
Who approves the final case study? Agree the reviewers and their responsibilities with the customer. Product and operations contacts can check facts, while an authorized contact can address publication, quotes, and brand use.