Ask what made the purchase necessary
The jobs to be done framework helps when a company knows who its customers are but cannot explain why they bought at that moment. Demographics describe people. A job examines the progress they seek in a particular circumstance. An operations manager may purchase monitoring equipment after an unexplained shutdown, during a capacity expansion or ahead of an audit. Those situations can require different evidence, messages and next steps.
Understand the job in its circumstances
The Christensen Institute describes jobs through the progress people seek and the circumstances in which they seek it.1 That means research should examine the buying situation, not merely ask for preferred product features. The product is one possible means of progress. Existing habits, manual work, another supplier or doing nothing can all be alternatives.
A functional task may have emotional or social consequences. A buyer may need to solve a technical problem and feel confident defending the decision to colleagues. Those concerns need evidence, not theatrical storytelling. Ask what happened, who was involved, what became difficult and why the old approach was no longer acceptable. The circumstances often reveal the communication requirement more clearly than a broad persona description. Our guide to value proposition canvas covers the next question.
Interview decisions rather than opinions
Recent decisions provide concrete material. Speak with customers who switched, prospects who declined and people who continued using an alternative. Reconstruct the timeline. What triggered the first concern? Which options were investigated? What delayed the decision? What finally made one option acceptable? Encourage detail about actual events rather than asking what people might do in a hypothetical future.
An interview should leave room for surprise. If the team assumes speed matters, a leading question about speed can produce agreeable but weak evidence. Ask what took time and what the consequences were. Observe the existing process when possible. A customer may describe a task as simple while a colleague spends hours correcting the handover. Keep consent and research notes appropriate to the setting, and protect confidential information.
Distinguish a job from a product description
“Buy our software” is a desired transaction for the company, not the customer’s job. “Produce an accurate report before the monthly review without reconciling several spreadsheets” gives the team a more useful starting point. It names progress and circumstances without prescribing a particular solution. The wording should remain grounded in research rather than polished into a slogan too early.
The jobs to be done framework can guide the offer, the message and the evidence. If buyers need confidence before committing, the page may require an explanation of validation, implementation and support. If the main difficulty is evaluating suitability, a clear application guide may be more useful than a cinematic brand film. Creative work becomes better when it has a specific job to serve. If that is your next question, read our guide to STP marketing.
Measure the outcome without inventing a JTBD score
There is no universal jobs-to-be-done performance score. Choose measures for the researched task and the business decision. Keep reported importance, experienced difficulty and observed behaviour distinct. A customer calling a problem important does not automatically establish willingness to pay for your proposed solution.
- Task success can measure whether an eligible participant achieves a defined outcome, with assistance rules and testing conditions reported beside the result.
- Time-to-completion can describe burden, but specify the starting and ending event. Faster completion should not excuse inaccurate or unsuitable outcomes.
- Research can examine the frequency and severity of a difficulty. A small interview sample identifies questions rather than establishing market-wide prevalence.
- Adoption can show whether suitable customers actually use the offer. Define meaningful use and the cohort instead of equating registration with success.
- A relevant commercial commitment can test demand under stated conditions. Distinguish polite interest, a requested demonstration, a paid evaluation and a completed order.
Investigate the decision behind the enquiry
Share the buying situation your team wants to understand and the customer evidence already available. We can discuss research that examines actual decisions and informs the communication brief.
Turn the research into a practical brief
Write the circumstances, desired progress, current alternatives and unresolved barriers. Keep representative observations close to the interpretation, with personal information removed. State where evidence is strong and where it is thin. Include the exceptions. A team should know whether a finding came from a repeated pattern among suitable buyers or from one memorable interview.
Use that brief to decide content and production. A technical demonstration may show the product working in the relevant context. A comparison may explain what changes when the buyer switches. A process illustration may clarify the input required and the next step. Review each proposed asset against the job. If the asset is beautiful but leaves the buying uncertainty untouched, give it a different role or reconsider it.
Test the solution after understanding the problem
Problem research and solution validation are different tasks. People can describe a difficulty accurately and still reject your proposed offer because of price, effort, risk or a missing requirement. Test the proposed value with suitable prototypes, demonstrations or real commitments appropriate to the business. Record what the test can and cannot establish.
Review the delivered experience after purchase. Did the product help the customer make the intended progress? What new difficulty appeared? Those answers can shape onboarding, retention and further product work. Jobs research should remain connected to use, rather than becoming a workshop document that nobody revisits once the campaign goes live. The customer’s original reason for buying is a useful standard against which to judge what the business actually delivered. Customer journey mapping is explained in a separate guide.
Questions people ask
Does JTBD replace segmentation?
It can reveal useful segmentation based on circumstances and desired progress. Commercial targeting still needs market size, reachability, fit and economics. Use the research to improve those decisions rather than discard them.
How many interviews are enough?
There is no universal number. The research question, variation in buyers and quality of the interviews matter. Qualitative patterns should be labelled as such; use suitable quantitative research when estimating prevalence.
Can we use JTBD for corporate buyers?
Yes. Examine the task, procurement context and people involved. Different members of a buying group may seek different progress or carry different risks, so avoid treating one interview as the entire organisation’s view.
Discuss the work your team needs next
Bring Quiamo a recent buying decision your team struggles to explain. A jobs to be done framework engagement can investigate the circumstances, alternatives and evidence buyers need, then translate those findings into a clearer offer and communication brief. The first conversation should focus on what changed in the customer’s world before the enquiry arrived, rather than on which campaign format the business wants to produce. Explore our brand strategy engagement to discuss the scope and deliverables.
Discuss the next step with Quiamo
Share the plan, the decision it needs to support and what you can already measure. We will tell you plainly which approach fits, what to track and what the evidence can and cannot show. The first call is free.
Sources
- Christensen Institute Jobs to Be Done theoryJobs focus on desired progress in particular circumstances.
Worked examples on this page are fictional and labelled. Search phrases and figures from external sources are cited; nothing here describes a Quiamo client result.
