
Module 1 — Strategy · Lesson 1.2
Customer Research and the Job to Be Done
Learning what people are trying to get done — from what they did, not what they say they would do
What you'll learn
- Describe a customer need as a job: the progress someone is trying to make in a specific circumstance
- Run an interview that asks about specific past events and avoids leading questions
- Recognize the limits of self-reported data and when to pair it with behavioural evidence
- Store research where it is findable and re-usable, not in one person's notes
Most small teams already 'know' their customers. They know them the way you know a city you have only driven through: the main roads, a few landmarks, nothing about why people live there. Research is the discipline of replacing that confident sketch with evidence. It is cheap — the core method is a conversation — and it is the step most often skipped, because it feels slower than shipping a campaign.
The job, not the demographic
Clayton Christensen and colleagues argued in Harvard Business Review in 2016 that firms have never known more about their customers yet innovate hit-or-miss, because they organize their knowledge around customer attributes and product features rather than around what the customer is trying to get done. The Christensen Institute's statement of the theory describes a job as the progress a person or organization is trying to make in a particular circumstance, with functional, social and emotional dimensions — and contrasts it with conventional marketing's focus on demographics or product attributes.
The circumstance is the part that matters most for marketing. 'Finance directors at mid-sized firms' is a demographic. 'A finance director whose board has just asked for monthly cash forecasts and who has three weeks to produce the first one' is a job in a circumstance. The second tells you when the buyer enters the market, what they search for, what they compare you to (often a spreadsheet, a contractor or doing nothing), and what success feels like — which is the raw material for the buying situations described in Lesson 1.1.
Jobs also expose your real competition. The thing a customer fires when they hire you is frequently not a direct competitor at all. Knowing that is the difference between a message that says 'better than Competitor X' and one that says 'the first board pack in a week, without a new hire'.
Interviews that collect behaviour
Nielsen Norman Group's guide to user interviews describes the method plainly: a one-on-one conversation to learn who people are, what their experiences are like, and what they need and value. Its practical advice is the part most teams get wrong. Ask about specific events rather than general processes — 'tell me about the last time you had to produce that report' — because recalling a particular incident nudges memory and produces usable detail. Use open-ended questions. Avoid leading ones; the article warns that the quality of the data depends heavily on the interviewer, and an interviewer who asks many leading questions gets answers that reflect the question.
A serviceable script for a marketing interview has five parts. The trigger: what happened that made you start looking? The alternatives: what else did you consider, including doing nothing? The decision: who else was involved, and what nearly stopped you? The words: how would you describe what we do to a colleague? And the outcome: what is different now? The fourth question is the most valuable for marketing, because it hands you the customer's vocabulary — usually plainer and more specific than yours.
Talk to recent buyers (memory is fresher), to people who chose a competitor or nothing, and to churned customers. There is no magic sample size for this kind of discovery work. Our rule of thumb — a recommendation, not a research finding — is to start with five to eight conversations per segment and stop when the answers stop surprising you, not at a quota.
The limits of what people tell you
Interviews are an attitudinal method: they collect reported behaviour, not observed behaviour. Nielsen Norman Group lists the consequences — memory is flawed, so people do not recall events fully, especially distant ones; participants do not know which details matter; and people describe what they think they did, or should have done. Never ask a prospect to predict their own future behaviour ('would you pay for this?') and treat the answer as a forecast. Ask what they did last time they had the problem, and what it cost them.
Pair interviews with behavioural evidence wherever you can: which pages people actually read before booking a call, which reply in a cadence produced the meeting, what support tickets say in customers' own words. When an interview and the behavioural data disagree, believe the behaviour and go back to ask why.
Making research a team asset
Research that lives in one founder's notebook decays the moment that founder is busy. The fix is a lightweight record: for each interview, the date, the segment, the trigger, the alternatives considered, three verbatim quotes and the job statement you would write from it. After every five interviews, write a one-page synthesis: the jobs you saw most often, the words customers used, and what surprised you.
Two rules keep it honest. Quotes are verbatim, never paraphrased into your own language — the value is precisely that they are not your words. And the synthesis records disagreements and outliers rather than smoothing them away; the one interview that does not fit is often the next segment.
Research of the outside world complements interviews but does not replace them. Reading analyst reports, competitor pages and community threads tells you what is said in public; only conversation tells you what made someone act.
Run and store a research round
- 1
Create an interview template in Knowledge
On /knowledge, create a template with the five script questions and the record fields (date, segment, trigger, alternatives, quotes, job statement). Each interview becomes a doc from that template.
- 2
Schedule the conversations as tasks
On /projects/tasks, create one task per interview with an owner and a due date, and a final task for the synthesis. A research round that is not on the board is a research round that slips.
- 3
Ask the agent to synthesize — then check it
From /ai-agent, ask the agent to search your interview docs and draft the synthesis: recurring jobs, repeated phrases, outliers. Verify every quote it surfaces against the source doc; a synthesis is a draft until a person who sat in the interviews signs off.
- 4
Record decisions the research changed
Back in /knowledge, log a decision entry whenever research changes a message or target, so the next person can see why.
Research health
- Interviews per quarter
- Completed customer or prospect interviews recorded in Knowledge in the last 90 days.
- Healthy signal: Our recommended floor is five per active segment per quarter — a starting point, not a research finding.
- Days since last interview
- Calendar days since the most recent recorded interview.
- Healthy signal: Under 30. Beyond 60, your picture of the customer is ageing.
- Verbatim phrases in live copy
- Count of customer-originated phrases that appear in your current homepage, ads or cadence steps.
- Healthy signal: At least one per major page or sequence; zero means the copy is in your words, not theirs.
Key takeaways
- ·Describe needs as jobs in circumstances; the circumstance tells you when and why buyers enter the market.
- ·Ask about the last specific time, never about hypothetical future behaviour.
- ·Interviews report behaviour; pair them with observed behaviour and believe the behaviour when they conflict.
- ·Store research as a shared record with verbatim quotes, so it outlives the person who did it.
Research tells you what jobs exist and who has them. The next lesson turns that into choices: which segments to serve, which to ignore, and what position to hold in their minds.
Sources
- 1.Know Your Customers' 'Jobs to Be Done'
Clayton M. Christensen, Taddy Hall, Karen Dillon, David S. Duncan · Harvard Business Review, September 2016 · 2016
The argument that firms know more about customers than ever yet innovate hit-or-miss because they focus on attributes and features rather than the job.
- 2.Jobs to Be Done Theory
Christensen Institute · christenseninstitute.org · 2024
Definition of a job as the progress people try to make in a circumstance, with functional, social and emotional dimensions, contrasted with demographic segmentation.
- 3.User Interviews 101
Maria Rosala, Nielsen Norman Group · nngroup.com · 2023
Ask about specific past events, use open-ended questions, avoid leading questions; interviews collect self-reported behaviour with known memory limits.