Jobs-to-be-Done for healthcare and digital-health products

JTBD shines in healthcare because the gap between "what the buyer says they want" and "what the user is actually trying to accomplish" is wider in healthcare than in almost any other category. Personas built from buyer requirements consistently miss what patients, clinicians, and caregivers are really hiring a product to do.

The healthcare buyer/user split

Healthcare almost always has multiple distinct "job hirers":

• Patient: the end recipient of care. Job is usually a mix of clinical outcome ("manage diabetes") and lived experience ("not feel like a sick person").
• Caregiver: family member or paid support staff. Job is usually about reducing their own burden while supporting the patient.
• Clinician: the provider delivering care. Job is delivering good care efficiently within constrained time, plus protecting their license and avoiding burnout.
• Institutional buyer: health system, payer, or employer purchasing the product. Job is managing cost, quality outcomes, and risk.

A product that serves only the institutional buyer's job is bought but not used. A product that serves only the patient's job is loved but not bought. Effective healthcare products serve at least two of these jobs simultaneously and don't conflict with the others.

Writing JTBD statements for healthcare

The standard JTBD template — When [situation], I want to [motivation], so I can [expected outcome] — works in healthcare with sharpened inputs:

• Situation: specific clinical or life moment (a new diagnosis, a flare-up, a discharge transition, a routine follow-up)
• Motivation: explicit and honest (often emotional or social, not just functional)
• Outcome: measurable in either clinical terms ("A1C below 7") or experience terms ("feel confident I can manage a flare without going to the ER")

Examples that actually drive product decisions:

• "When my insulin pump alerts me and I'm in a meeting at work, I want to silence and respond to it discreetly, so I can manage my condition without my coworkers noticing."
• "When I'm caring for my elderly parent who just came home from the hospital, I want a clear daily checklist of what to do and what to watch for, so I can keep them safe without calling the doctor for every question."
• "When I'm a primary care physician with 15-minute appointments, I want a 30-second summary of a new patient's recent history before I walk in, so I can be present in the room instead of scrolling notes."

These statements look different from "patients with diabetes" or "PCPs aged 35–55" personas — and they drive sharper product decisions.

Functional, emotional, and social jobs in healthcare

Christensen's job dimensions matter especially in healthcare because emotional and social jobs often dominate clinical jobs in determining whether a product gets adopted:

• Functional job: "manage my chronic condition"
• Emotional job: "feel competent and in control"
• Social job: "look like a healthy person, not a sick person, to my family and coworkers"

A diabetes management product that solves only the functional job (great glucose tracking) but ignores the emotional job (the patient feels constantly reminded they're sick) under-performs even when clinically effective. CGM products that succeed treat the social dimension explicitly — discreet wearables, less-medical UI, language that doesn't pathologize.

The regulatory overlay

Healthcare regulation determines what your product is allowed to claim and how. Map each candidate job to its regulatory framing before committing to specs:

• "Diagnose" → FDA regulated as a medical device
• "Help decide whether to seek care" → allowed without medical-device classification (with careful claims)
• "Treat" → FDA regulated; clinical trials usually required
• "Support a treatment plan" → less regulated; depends on integration
• "Provide information about a condition" → low regulatory bar; consumer health framing

The JTBD statement and the regulatory framing have to match. A statement that promises diagnosis is a statement that requires FDA clearance. The framework is not just a product tool — it's a go-to-market gate.

How to do JTBD discovery in healthcare

Standard JTBD discovery requires interviews. In healthcare, interview design needs extra care:

• Recruit from real "trigger moments" — patients within 30 days of diagnosis, caregivers within 30 days of a hospital discharge, clinicians fresh off a clinic session
• Avoid leading clinical framings — ask about the situation and what they tried, not about their diagnosis or treatment plan
• Listen for emotional/social cues — what they felt, what they hid from others, what they wished they could do without being noticed
• IRB / compliance: if interviewing patients about specific conditions, work with research ethics review depending on jurisdiction

Aim for 30+ interviews per job hypothesis before committing to product direction.

When JTBD isn't the right tool

For pure operational improvements inside a health system (RCM, scheduling, staffing), use process analysis rather than JTBD. For clinical efficacy questions (does this treatment work?), use RCT methodology. JTBD is the right tool when the question is "what should this product do for users in this category?" — and in healthcare, that question has more layers than a generic SaaS JTBD would suggest.

Related

• JTBD framework — the full framework page
• JTBD explained — long-form guide
• JTBD vs Personas — when to use each
• SWOT for healthcare — companion strategy analysis