Case study interview guide
This page is for the person who interviews a customer for a case study: a marketing manager, a partner, or the business itself interviewing its own staff. It gives a structure for a conversation of about an hour, questions that produce facts rather than slogans, and a notes form. Use it with the Case study template and the process on Case studies and content marketing.
Warning
Interview only after the customer has agreed in writing to a case study, and confirm at the start what may be published and whether people may be named. Write down only what was said; never fill gaps with invented figures or quotes.
Contents
Before the interview
- To do: Written consent received (Step 2).
- To do: The public site looked at; features in use noted, with help pages for each.
- To do: Interviewees and their roles agreed; time zone and duration agreed (about 60 minutes).
- To do: Whether you may record the call asked in advance; if not, take notes.
- To do: A fact sheet started (Case study template, fact sheet).
Opening: the consent check
Read or say, and note the answers:
Thank you for your time. Before we start, three points:
1. We will use this conversation to draft a case study about <project>. Nothing is published until you approve
the final text in writing.
2. Do you agree to be named, or would you prefer to be quoted by your role only?
3. May we <record this call | take notes>? Recordings and notes are kept at <place> and deleted after <period>.
You can ask us to change or withdraw the case study at any time by writing to <contact>.The questions
Ask open questions. For any figure, ask "From which system, for which period?" and note it.
The organization and the situation before
- What does your organization do, and who are your customers or users?
- What did your website or application look like before this project?
- What did not work, and what did that cost you in time, money or opportunities?
The choice
- Why did you choose Exponential? Which needs decided it?
- Which other options did you consider? (Record; publish comparisons only if they can be checked, see Comparing Exponential factually.)
- Who built it: your own team or a partner? Why?
The project
- What was built: content types, sites, languages, integrations?
- How long did it take, in which phases?
- What was hard, and how was it solved?
- How did editors learn to use it?
Daily use
- Which features do your editors and staff use every day?
- How is the site hosted and kept up to date? Who does it?
- Has anything gone wrong since launch? How was it handled?
Results
- What has changed since launch? How do you know?
- Which figures can you share, from which system and period? (Only measured figures.)
- What would you not want to go back to?
Advice and next steps
- What would you tell an organization in your position?
- What do you plan next?
- Is there anything we should not mention?
Notes form
INTERVIEW NOTES - <project> Date: <date> Interviewer: <name>
Interviewees: <name or role>, <name or role>
Named in publication: yes / role only Recording: yes / no Notes deleted by: <date>
Q | What was said (close to their words) | Fact? | Source and period | Quote candidate?
---|---------------------------------------------|-------|---------------------------|-----------------
1 | | y / n | | y / n
2 | | y / n | | y / n
...
Follow-up questions: ______________________________________________
Documents promised by the customer: ______________________________After the interview
- Send a thank-you note with the list of documents or figures they promised.
- Transfer facts to the fact sheet, each with its source.
- Write the draft with the Case study template.
- Check every product statement against the help (Feature highlights for customers).
- Send the draft for approval; record changes and the final approval.
- Delete recordings and notes on the agreed date.
- Review the published case study at least yearly and withdraw it on request (Step 8).
Related pages
- Case study template
- Customer references (partners)
- Demo scripts
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.