JTBD Needs: measuring functional, emotional and social needs

What is JTBD Needs?

JTBD Needs is the Jobs-to-be-Done variant that captures what customers expect from a working relationship and how well those expectations are met — separated into functional, emotional and social needs.

The separation is the core of the method. In an overall score, the three levels merge into an unremarkable number. Kept separate, they often paint a clear picture: everything is fulfilled on the technical side, and yet something is missing that appears in no proposal and no service level.

When does JTBD Needs fit — and when doesn't it?

Needs fits services and long-term business relationships — wherever the job is done not by a product but by a working relationship. Typical occasions:

• customers cancel “for pricing reasons,” and a discount program is on the table
• the renewal rate is falling even though the performance metrics are fine
• buyers choose the more expensive offer, and nobody knows exactly why
• customers upgrade to a higher package, and the package is to be redesigned

Needs does not fit when a single purchase or drop-off needs to be explained — that is what JTBD Switch is built for. Nor for the usability of an interface; that is what SUS and UEQ+ are for.

Which three levels does JTBD Needs measure?

Level	Question	Examples at an IT service provider
Functional	What has to be done in the end?	systems run, incidents get fixed, appointments are kept
Emotional	How should the working relationship feel?	not having to chase anyone by phone, being sure someone is thinking ahead
Social	How does the working relationship make the customer look to others?	to their own management, as someone who has IT under control

At service providers, the functional level is usually well measured — it's in the contract. The other two aren't written down anywhere, and that is exactly why the gap lies there.

How is the questionnaire structured?

One block per level with a few needs, two ratings for each.

1. Importance: How important is this to you?
2. Fulfillment: How well is it met today?

Add one or two open questions, for example about what bothered you most recently about the working relationship. In the IT service provider case study, there are three needs per level and two free-text fields, 16 questions in total.

Two rules for wording: needs, not services — “not having to chase anyone by phone myself” instead of “ticket system with status display.” And no presupposed answers — “Do you find our prices reasonable?” only confirms the pricing narrative instead of testing it.

How is JTBD Needs analyzed?

For each need, importance and fulfillment are compared; the gap is reported, separated by level. A need with high importance and low fulfillment is the biggest problem area — and usually the most solid justification for taking action.

It is also revealing how reasons map onto the levels. “Too expensive” is rarely a functional statement. Often it means: “I can't prove internally what we're paying for.” That is a social need — and no discount solves it.

Example: not a discount, but a report

In the IT service provider case study (in German), two larger customers have canceled, both “for pricing reasons.” Sales is calling for a discount program. 96 contacts respond, including the two who canceled.

Level	Need	Importance	today
functional	Systems run, incidents get fixed quickly	9.1	met
emotional	Not having to chase anyone by phone myself	8.8	partially met
emotional	Being sure someone is thinking ahead	8.6	not met
social	Looking to my own management like someone who has IT under control	8.9	not met

Functionally, everything is met. The most important unmet need in the entire study is social — and it appears in no contract, no service level and no reporting. The discount program is rejected. Instead, there is a monthly one-page report to pass on, proactive status updates and a dedicated contact person for each customer.

What are the limits of JTBD Needs?

• The list of needs decides. What isn't asked about doesn't show up. Open questions catch part of it.
• People are reluctant to name social needs. Honest answers require an analysis that is credibly anonymous.
• Small populations. In B2B, 100 contacts are often the entire customer base. Shares then show orders of magnitude, not representative values.
• No product diagnosis. Needs shows what is missing from the relationship, not which feature to improve.

How does JTBD Needs work in usabiq?

JTBD Needs is included from Decision Pro — and therefore also in the 14 days every sign-up starts with.

• Scored without a language model. Importance and fulfillment are calculated per need and per level, not summarized generatively.
• Additional open questions are analyzed separately; automatic theme detection runs only for JTBD Switch, JTBD Story and the free-form questionnaire.
• Compare segments with statistical confidence — if a group is too small for a conclusion, usabiq says so instead of showing a number.
• Three participation modes: logged-in users only, mixed, or fully public via link.
• Decision Engine: the gaps are turned into a prioritized list of problems, opportunities and quick wins.