Customer Problems, Needs and Jobs to Be Done

Introduction

Entrepreneurial opportunities rarely begin with a product. They begin with a situation in which a person, organization, or community is trying to make progress but encounters friction, risk, cost, delay, uncertainty, or dissatisfaction. Customer discovery is therefore not primarily the search for attractive ideas; it is the disciplined investigation of problems worth solving.

This chapter develops four connected tools: problem statements, Jobs to Be Done (JTBD), customer journey mapping, and outcome-based analysis. Together they help an entrepreneur identify what customers are trying to accomplish, why the problem matters, what they do today, and what forces may cause them to adopt or reject an alternative. The analysis distinguishes functional, emotional, and social needs and evaluates pain intensity without assuming that every complaint represents a viable market.

The central principle is:

Customers do not simply buy products; they “hire” solutions to make progress in particular circumstances.

A successful discovery process converts vague observations such as “students need better learning” into evidence-based propositions such as “working postgraduate students need to prepare for examinations during short, fragmented evening periods, while retaining confidence that their preparation is sufficient.”

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Distinguish customer problems, needs, wants, preferences, and symptoms.
2. Formulate specific and testable problem statements.
3. Apply the Jobs to Be Done framework to functional, emotional, and social dimensions of demand.
4. Map a customer journey and identify moments of friction, uncertainty, and opportunity.
5. Use outcome-based analysis to prioritize unmet needs.
6. Assess pain intensity, existing alternatives, and the forces affecting switching.
7. Translate discovery evidence into product, positioning, and experimentation decisions.
8. Recognize methodological, ethical, and strategic limitations in customer-problem analysis.

1. From Product Ideas to Customer Progress

An idea-first approach asks, “What can we build?” A discovery-first approach asks, “What important progress is a customer currently unable to make easily, reliably, or affordably?” This distinction matters because customers evaluate solutions in relation to alternatives, not in isolation. A technically impressive product may fail if the problem is infrequent, low-priority, already adequately solved, or difficult to access.

1.1 Problem, need, want, and solution

A problem is an undesirable gap between a current state and a desired state. A need is a requirement or desired condition that explains why closing that gap matters. A want is a preferred form of satisfaction, often shaped by culture, experience, and marketing. A solution is a product, service, process, or behavior intended to address the problem.

For example, a commuter may experience late arrival at work (problem), require predictable arrival (need), want a comfortable electric vehicle (want), and use a ride-hailing service (solution). Confusing the want with the need can lead an entrepreneur to design a feature before understanding the underlying job.

Problems also have symptoms and causes. “Customers abandon the registration form” is an observable symptom. Possible causes include excessive data entry, unclear value, privacy concerns, or the absence of a required document. Discovery should investigate the causal chain rather than merely record the symptom.

1.2 Desirable problems

Not every problem is an opportunity. A commercially and socially meaningful problem commonly has several characteristics:

• It occurs with sufficient frequency or has sufficiently high consequences.
• The affected customer recognizes it or can be helped to recognize it.
• Existing alternatives are costly, inconvenient, risky, or inadequate.
• The customer has authority, ability, and willingness to act.
• A feasible solution can be delivered within legal, technical, and economic constraints.

The final criterion is important. A severe problem may still be unsuitable for a particular venture if the entrepreneur cannot reach decision-makers, meet regulatory requirements, or create a sustainable business model.

2. Problem Statements and Evidence

A problem statement provides a disciplined boundary for discovery. It should describe a customer, context, desired progress, and obstacle without prematurely prescribing a product.

A useful form is:

[Customer segment] struggles to [make progress] when [context], because [obstacle], resulting in [consequence].

Example:

Independent food vendors struggle to predict daily ingredient demand during seasonal festivals because sales information is fragmented and informal, resulting in stockouts, waste, and avoidable cash-flow pressure.

This statement is stronger than “food vendors need an AI inventory app” because it does not assume the solution.

2.1 Qualities of a strong statement

A strong statement is:

• Specific: identifies a real group and situation.
• Observable: can be investigated through behavior and evidence.
• Significant: describes consequences that matter.
• Neutral: does not embed a preferred feature or technology.
• Falsifiable: could be shown to be weak or inaccurate.
• Narrow enough to test: avoids combining unrelated problems.

Avoid statements such as “everyone wants convenience,” “small firms need digital transformation,” or “users want an intuitive platform.” These are broad claims, not discovery hypotheses.

2.2 Evidence hierarchy

Customer discovery is stronger when evidence moves from opinion toward behavior. A practical hierarchy is:

No category is automatically conclusive. Payments may be compulsory, and observed behavior may occur under unusual conditions. Triangulation—combining interviews, observation, usage data, documents, and market evidence—is preferable to relying on one source.

3. Jobs to Be Done

Jobs to Be Done is a perspective on demand that focuses on the progress a customer seeks in a particular circumstance. The “job” is not identical to a product, demographic, or feature. A person may hire a spreadsheet, consultant, mobile application, or colleague to perform substantially the same job.

A useful job statement contains:

When [situation], I want to [motivation or progress], so I can [expected outcome].

For example:

When preparing a board report from inconsistent operational data, I want to reconcile the figures quickly and confidently, so I can make a defensible recommendation without delaying the meeting.

The job includes context and desired progress. “Use analytics software” is a solution-oriented description; “make a defensible recommendation from inconsistent data” is job-oriented.

3.1 Functional, emotional, and social jobs

A customer’s experience normally includes three layers:

1. Functional needs or jobs: what must be accomplished. Examples include transferring money, comparing suppliers, transporting goods, or scheduling an appointment.
2. Emotional needs or jobs: how the customer wants to feel or avoid feeling. Examples include feeling in control, reducing anxiety, avoiding embarrassment, or gaining confidence.
3. Social needs or jobs: how the customer wants to be perceived or relate to others. Examples include appearing competent, demonstrating responsibility, belonging to a community, or maintaining professional status.

These layers interact. A business owner may functionally need a financing decision, emotionally need certainty that the business will survive, and socially need to appear credible to employees and investors. A solution addressing only the functional layer may be rejected if it increases anxiety or threatens identity.

3.2 Core, related, and consumption jobs

The core job is the main progress sought. Related jobs occur before, during, or after the core job. Consumption jobs concern acquiring, learning, configuring, using, maintaining, and disposing of a solution.

For a meal-delivery service, the core job might be “obtain a dependable dinner after a long workday.” Related jobs include choosing a meal and coordinating household preferences. Consumption jobs include creating an account, tracking delivery, storing leftovers, and resolving an error. Many opportunities lie in related and consumption jobs rather than in the central service itself.

3.3 Circumstances over demographics

Demographics can assist segmentation, but they often do not explain switching behavior. Two people of the same age and income may hire different solutions because their circumstances differ. JTBD research therefore asks:

• What triggered the search or change?
• What was the customer trying to accomplish?
• What constraints were present?
• What did the customer use before and why?
• What trade-offs were accepted?
• What would make the current behavior unacceptable?

A job can be stable while the preferred solution changes with technology, regulation, income, or social norms.

4. Customer Journey Mapping

A customer journey map represents the sequence of stages through which a customer experiences a problem, searches for a solution, decides, uses it, and evaluates the result. It is not merely a process flow owned by the organization. It should represent the customer’s perspective, including invisible effort and emotional responses.

A typical journey has the following stages:

1. Trigger: an event makes the problem salient.
2. Recognition: the customer defines or interprets the problem.
3. Search and consideration: alternatives are explored.
4. Decision and access: a solution is selected, purchased, or adopted.
5. Onboarding and use: the solution is integrated into practice.
6. Recovery or adaptation: errors, exceptions, and changing needs are handled.
7. Evaluation and continuation: the customer decides whether to continue, recommend, or switch.

A journey map should record customer actions, goals, questions, emotions, pain points, touchpoints, alternatives, and evidence. The map can also identify the responsible actor: user, buyer, administrator, influencer, or service provider. These roles may be different people.

Mapping should distinguish the frontstage experience visible to the customer from backstage processes that affect it. A simple sign-up screen may conceal slow verification, manual approvals, or data duplication. Such backstage constraints can explain why an apparently attractive solution fails in practice.

5. Outcome-Based Analysis

JTBD identifies the job; outcome-based analysis examines how customers judge progress in performing it. An outcome is a measurable or assessable consequence that customers seek to maximize or minimize. Examples include reducing the time required to complete a task, increasing confidence in a decision, minimizing the likelihood of an error, or reducing coordination effort.

Well-formed outcome statements avoid product language. A useful template is:

Minimize the time required to [job step] while maintaining [quality or safety condition].

or:

Minimize the likelihood of [undesired consequence] when [context].

Outcomes should be:

• Important to the customer;
• Independent of a specific solution;
• Stable enough to compare across alternatives;
• Specific enough to investigate;
• Measurable or discussable using credible evidence.

5.1 Importance and satisfaction

Entrepreneurs often prioritize outcomes that are important but poorly satisfied by existing alternatives. A simple discovery matrix can classify each outcome as high or low in perceived importance and high or low in current satisfaction.

This is a directional framework, not a universal scoring law. If scores are collected, the measurement method should be documented. For example, respondents may rate importance and satisfaction on the same 1–5 scale, where 1 means very low and 5 means very high. A basic opportunity index might be used for exploratory comparison:

Here, O_i is the exploratory opportunity score for outcome i, I_i is perceived importance, and S_i is current satisfaction, measured on the same scale. The nonnegative term prevents high satisfaction from producing a negative “opportunity.” This index assumes that importance and satisfaction ratings are comparable and should not be treated as a validated demand forecast. Sampling bias, scale-use differences, and strategic context must be examined before making decisions.

For example, if importance is 5 and satisfaction is 2, then O_i = 5 + (5 − 2) = 8. If importance is 3 and satisfaction is 4, then O_i = 3 + 0 = 3. The first outcome deserves more investigation, but the result does not prove willingness to pay.

6. Pain Intensity and Existing Alternatives

Pain is multidimensional. A problem can be frequent but mildly irritating, or rare but catastrophic. A useful assessment considers:

• Frequency: how often the problem occurs;
• Severity: the magnitude of loss, delay, risk, or distress;
• Duration: how long the consequence persists;
• Urgency: how quickly action is required;
• Visibility: whether the customer and decision-maker recognize it;
• Reach: how many people or organizations experience it;
• Economic consequence: direct and indirect cost;
• Strategic consequence: effects on trust, reputation, compliance, or growth.

These dimensions should not be collapsed into a pseudo-precise score without evidence. A qualitative rating—low, medium, high—with supporting observations is often more honest during early discovery.

6.1 Alternatives are broader than competitors

The relevant competition includes every way customers currently make progress:

• A direct commercial product;
• A substitute product;
• Internal staff or expertise;
• Spreadsheets and informal workarounds;
• Delaying the task;
• Doing nothing;
• Asking a friend, supplier, or public institution.

The status quo is often the strongest competitor because it has no adoption cost and is familiar. Discovery should ask, “What did you do the last time this happened?” rather than “Would you use our proposed product?”

A useful alternative profile includes the job served, benefits, weaknesses, switching costs, trigger for use, and reason for continued adoption. Entrepreneurs should analyze not only why customers dislike an alternative but also why they tolerate it. Tolerance may reflect habit, trust, integration, low price, or the absence of a credible replacement.

7. Switching Forces

The Forces of Progress perspective explains movement between an existing behavior and a new solution. Four forces are especially useful:

• Push of the current situation: dissatisfaction, loss, risk, or frustration that motivates change.
• Pull of the new solution: perceived benefits or improved outcomes.
• Anxiety of the new solution: uncertainty, learning effort, privacy risk, reliability concerns, or fear of failure.
• Habit of the present solution: familiarity, existing routines, integration, trust, and sunk investment.

Adoption is more likely when push and pull outweigh anxiety and habit, but this is a conceptual model, not an additive equation. A customer may strongly dislike a current provider yet remain because migration threatens data integrity or regulatory compliance.

Switching costs include money, time, training, data migration, contractual penalties, social risk, workflow disruption, and loss of accumulated knowledge. In organizational markets, the user, economic buyer, technical approver, procurement function, and affected colleague may experience different forces. A product that pleases the user but increases compliance work may fail at approval.

8. Researching Problems Without Leading Customers

Customer discovery interviews should investigate actual events rather than invite speculation. Strong questions include:

• “Tell me about the last time this happened.”
• “What did you do first?”
• “What alternatives did you consider?”
• “What was difficult or risky?”
• “What did the workaround cost you?”
• “Who else was involved in the decision?”
• “What would cause you to change your current approach?”

Weak questions include “Would you buy this?”, “Do you like this idea?”, and “Would an app solve the problem?” Such questions invite politeness and hypothetical optimism.

A professional discovery process normally includes a research plan, purposive sampling, a discussion guide, consent procedures, systematic note-taking, coding of recurring patterns, disconfirming evidence, and a decision rule for further investigation. Interviewers should separate verbatim evidence from interpretation. For example:

• Evidence: “I spend about two hours every Friday reconciling three files.”
• Interpretation: “Reconciliation is a high-pain job.”
• Hypothesis: “A reliable automated reconciliation service may have value.”

The interpretation and hypothesis require further validation.

9. Illustrative Case: CareRoute for Independent Clinics

The following is a fictional illustrative case.

Background

A venture team proposed CareRoute, a digital referral-coordination service for independent medical clinics. The initial idea was a mobile application that would allow patients to book specialist appointments directly.

Problem investigation

Early interviews with clinic owners suggested that “patients struggle to find specialists.” However, observation of the referral process revealed a different pattern. General practitioners spent time calling specialist offices, checking whether referrals had arrived, and following up when patients failed to attend. Patients were often anxious because they did not know what would happen next. Specialist offices disliked incomplete information and unpredictable schedules.

The original problem statement—“patients need an appointment app”—was therefore too narrow. A revised statement was:

Independent clinics struggle to coordinate referrals and keep patients informed after a consultation because information is fragmented across calls, forms, and office systems, resulting in administrative effort, patient anxiety, and missed appointments.

JTBD analysis

The core functional job for the referring clinic was “transfer a patient to appropriate follow-up care with confirmation that the referral is progressing.” Related jobs included obtaining complete information, communicating status, and recovering from failed appointments. Emotional needs included reducing uncertainty and avoiding the feeling of losing control over patient care. Social needs included appearing organized and trustworthy to patients and partner clinics.

Journey analysis

The journey map identified a critical moment after the referral was issued. Patients did not necessarily need to choose among dozens of specialists; they needed confirmation, understandable instructions, and visibility into the next step. The major existing alternatives were phone calls, fax, manual spreadsheets, and patients calling clinics themselves.

Approach

The team tested a narrow service rather than immediately building a full application. For four clinics, staff used a lightweight referral tracker and standardized patient messages. The experiment measured referral confirmation time, staff follow-up effort, incomplete referral rates, and missed appointments. Patients were asked about clarity and confidence, while staff recorded exceptions.

Outcome

The pilot showed that the strongest early value proposition was not direct patient booking. It was coordinated status visibility and exception handling for clinic staff, combined with clear patient communication. The team postponed complex scheduling integration and focused on the workflow where pain and evidence were strongest.

Learning points

1. The initial solution assumption obscured the broader coordination job.
2. Observation exposed backstage work invisible in interviews.
3. Existing manual alternatives were competitors but also sources of workflow knowledge.
4. Functional, emotional, and social needs reinforced one another.
5. A narrow service experiment produced more reliable learning than a large application build.
6. In healthcare, privacy, consent, data security, professional responsibility, and regulatory compliance are part of the problem definition, not later additions.

10. Managerial, Ethical, and Technological Implications

Problem discovery affects segmentation, positioning, pricing, service design, sales strategy, and resource allocation. A job-oriented positioning statement focuses on the customer’s progress: “help clinic teams confirm and communicate referrals with less uncertainty,” rather than “an AI-enabled healthcare workflow platform.” Pricing should reflect the value and risk associated with the job, while recognizing who receives value and who pays.

Ethically, entrepreneurs must avoid manufacturing anxiety, exploiting vulnerable customers, or treating stated distress as permission to collect unnecessary data. Research participants should understand the purpose of the study, the use of recordings, confidentiality arrangements, and any compensation. Sensitive domains such as health, finance, education, employment, and identity require heightened safeguards and compliance with applicable law.

AI can support transcription, clustering of interview notes, journey-event detection, and analysis of support conversations. It should not replace human judgment about meaning, vulnerability, or consent. Automated coding may reproduce demographic or linguistic bias, expose confidential information, or turn tentative interpretations into apparently objective findings. Teams should minimize data, protect access, retain audit trails, validate models against human review, and disclose material limitations.

11. Limitations and Common Errors

JTBD and journey mapping are powerful lenses, not complete theories of human behavior. Customers may not accurately recall triggers, may rationalize decisions after the event, or may be unable to articulate tacit needs. A job statement can also become so abstract that it loses practical usefulness. Furthermore, different stakeholders may have conflicting jobs, and institutional constraints may dominate individual preference.

Common errors include:

• Asking customers to design the product;
• Treating every complaint as an urgent problem;
• Sampling only enthusiastic early adopters;
• Ignoring non-users and people who rejected a solution;
• Confusing satisfaction with loyalty;
• Measuring stated willingness to pay without observing commitment;
• Mapping an internal process rather than the customer experience;
• Overfitting a solution to one dramatic story;
• Ignoring accessibility, culture, and power differences;
• Treating a quantitative score as more valid than its sampling and measurement process.

Best practice is iterative triangulation: investigate events, observe behavior, compare alternatives, test a narrow intervention, and revise the problem definition when evidence contradicts the initial assumption.

Chapter Summary

Customer discovery begins with customer progress rather than product features. A problem is a meaningful gap between a current and desired state; a need explains why closing the gap matters. Strong problem statements identify a customer, context, obstacle, and consequence without prescribing a solution.

Jobs to Be Done frames demand around progress in a particular circumstance. Jobs include functional, emotional, and social dimensions and may be core, related, or consumption jobs. Customer journey maps reveal triggers, decisions, touchpoints, backstage work, pain points, and moments where customers use alternatives. Outcome-based analysis identifies the results customers seek to improve or avoid, particularly outcomes that are important but poorly satisfied.

Pain intensity should be assessed through frequency, severity, duration, urgency, visibility, reach, and consequences. Existing alternatives include workarounds, internal labor, delay, and doing nothing. Switching depends on the push of the current situation, pull of a new solution, anxiety about change, and habit of the present solution. Rigorous discovery relies on behavioral evidence, triangulation, ethical research, and small experiments. The ultimate objective is not merely to describe a problem but to determine whether it is sufficiently important, accessible, solvable, and valuable to justify entrepreneurial action.

Key Terms

Alternative: Any method customers use to accomplish a job, including competitors, workarounds, or inaction.

Backstage process: An internal activity that affects the customer journey but is not directly visible to the customer.

Core job: The principal progress a customer seeks to make.

Customer journey map: A representation of customer actions, needs, emotions, touchpoints, and problems across stages of an experience.

Emotional need: A desired feeling or emotional state associated with making progress.

Existing alternative: A current product, service, behavior, or workaround used instead of a proposed solution.

Functional need: A practical requirement to accomplish a task or outcome.

Habit of the present: Familiarity and routine that discourage switching.

Job to Be Done: The progress a customer seeks in a particular circumstance.

Outcome: A consequence or result that customers seek to improve, maximize, minimize, or avoid.

Pain intensity: The significance of a problem assessed through dimensions such as frequency, severity, urgency, and consequence.

Problem statement: A specific, evidence-oriented description of a customer obstacle and its consequences.

Push: Dissatisfaction or negative pressure arising from the current situation.

Pull: Perceived attraction of a new solution or improved outcome.

Related job: A task connected to the core job before, during, or after its performance.

Social need: A desired effect on identity, status, belonging, or how others perceive the customer.

Switching cost: Money, time, risk, effort, or disruption associated with changing from one alternative to another.

Trigger: An event that makes a problem salient and initiates search or change.

Workaround: An improvised or indirect method used to accomplish a job when the preferred solution is unavailable or inadequate.

Review Questions

Short Answer Questions

1. Distinguish a customer problem from a customer solution, using an example.
2. What are the functional, emotional, and social dimensions of a job?
3. Why should customer interviews focus on recent behavior rather than hypothetical preference?
4. Identify four dimensions that can be used to assess pain intensity.
5. What is the difference between a core job and a consumption job?

Long Answer Questions

1. Explain how a problem statement can guide customer discovery while avoiding premature solution assumptions.
2. Describe the stages and uses of a customer journey map, including the distinction between frontstage and backstage activity.
3. Explain Jobs to Be Done and compare it with demographic segmentation.
4. Discuss existing alternatives and switching forces in the adoption of a new entrepreneurial offering.
5. Evaluate the strengths and limitations of outcome-based analysis in prioritizing opportunities.

Analytical / Application Questions

1. Choose a service used by university students. Construct a problem statement, identify its core job, and list one functional, one emotional, and one social need.
2. Map the journey of a customer who recently abandoned a digital service. Identify the trigger, major friction points, existing alternatives, and likely switching forces.
3. For three outcomes, assign importance and satisfaction ratings on a 1–5 scale and calculate O_i = I_i + max(I_i − S_i, 0). Explain why the resulting ranking should not be treated as proof of market demand.

Multiple Choice Questions with Answers

Question 1

Which statement best represents a Jobs to Be Done formulation?

A. A professional needs a premium project-management application.

B. A professional wants a modern dashboard with many features.

C. When preparing a time-sensitive project report, a professional wants to reconcile updates quickly so a credible decision can be made.

D. A professional belongs to the high-income technology segment.

Correct Answer: C. When preparing a time-sensitive project report, a professional wants to reconcile updates quickly so a credible decision can be made.

Question 2

Which is the strongest early evidence that a problem may have commercial significance?

A. A participant says the proposed idea sounds interesting.

B. A participant already spends time and money using a workaround for the problem.

C. A participant agrees that the problem is theoretically important.

D. A participant likes the founder’s presentation.

Correct Answer: B. A participant already spends time and money using a workaround for the problem.

Question 3

Which item is an emotional need?

A. Submit an invoice electronically.

B. Reduce the number of form fields.

C. Feel confident that a financial decision is safe.

D. Appear environmentally responsible to peers.

Correct Answer: C. Feel confident that a financial decision is safe.

Question 4

What is the primary purpose of a customer journey map?

A. To list every feature planned for a product.

B. To represent the customer’s experience, actions, needs, and friction across stages.

C. To calculate the exact market size automatically.

D. To replace customer interviews with internal assumptions.

Correct Answer: B. To represent the customer’s experience, actions, needs, and friction across stages.

Question 5

Which of the following is an existing alternative?

A. Only a direct competitor’s product.

B. Only a product with identical technology.

C. A spreadsheet, manual labor, delay, or doing nothing, as well as competing products.

D. Only an alternative that customers rate positively.

Correct Answer: C. A spreadsheet, manual labor, delay, or doing nothing, as well as competing products.

Question 6

In the switching-forces perspective, anxiety of the new solution refers primarily to:

A. Dissatisfaction with the current situation.

B. The attraction of improved benefits.

C. Uncertainty, learning effort, risk, or fear associated with change.

D. The frequency with which the current solution is used.

Correct Answer: C. Uncertainty, learning effort, risk, or fear associated with change.

Question 7

Using O_i = I_i + max(I_i − S_i, 0), what is the opportunity score when importance is 5 and satisfaction is 2?

A. 3

B. 5

C. 7

D. 8

Correct Answer: D. 8

Question 8

Which interview question is least leading and most behavior-focused?

A. Would you buy our proposed application?

B. Do you agree that current solutions are poor?

C. Tell me about the last time you encountered this problem and what you did.

D. Would an automated feature solve this for you?

Correct Answer: C. Tell me about the last time you encountered this problem and what you did.

Question 9

An outcome-based opportunity is generally most attractive when the outcome is:

A. Low in importance and highly satisfied.

B. High in importance and poorly satisfied.

C. Low in importance and poorly satisfied, with no consequence.

D. Already fully solved by a trusted alternative.

Correct Answer: B. High in importance and poorly satisfied.

Question 10

Why should an outcome score not automatically be treated as a demand forecast?

A. Outcomes cannot ever be discussed by customers.

B. Importance and satisfaction ratings may be biased and do not prove willingness to pay or adoption.

C. Quantitative data are always less useful than opinions.

D. All customers must receive identical solutions.

Correct Answer: B. Importance and satisfaction ratings may be biased and do not prove willingness to pay or adoption.