JTBD

I’ll answer as a world-famous product strategist and JTBD researcher, recipient of the Clayton Christensen Institute Award for Applied Innovation.

Answering example

TL;DR: Below are clear, reusable Jobs-to-Be-Done examples across B2B, B2C, SaaS, internal corporate roles, and decision-makers — written in correct JTBD structure so you can plug them straight into product discovery, strategy, or stakeholder communication.

Step-by-step answer with concrete details

1. Classic JTBD structure (baseline)

Use this pattern:

When …
I want to …
So I can …

Or extended (stronger for strategy):

When [situation / context],
I want to [main progress I’m trying to make],
So I can [business / emotional / social outcome],
Despite [constraints / anxieties / trade-offs].___

A. B2B SaaS / Product examples

Example 1 — B2B product manager

When quarterly planning starts and teams argue about priorities,
I want to see a single, trusted view of customer usage and revenue impact,
So I can justify roadmap decisions without politics or guesswork.

Example 2 — Director / C-level

When I review monthly performance,
I want to understand which metrics actually drive profit growth,
So I can stop funding activities that look busy but don’t move the business.

Example 3 — Implementation / onboarding

When a new client signs a contract,
I want to get them to first value as fast as possible,
So I can reduce churn risk and avoid support escalation later.

B. B2C / User behavior examples

Example 4 — Mobile app user

When I open the app for the first time,
I want to immediately understand what problem it solves for me,
So I can decide in seconds whether it’s worth keeping.

Example 5 — Returning user

When I come back after a few days away,
I want to quickly continue where I left off,
So I can feel progress instead of friction.

C. Internal corporate / process JTBD (very underrated, very powerful)

Example 6 — Sales manager

When I review my team’s pipeline,
I want to clearly see which deals are truly alive versus “hopeful”,
So I can intervene early and forecast revenue realistically.

Example 7 — Operations / process owner

When a process breaks between departments,
I want to identify the real bottleneck instead of symptoms,
So I can fix the system once instead of firefighting forever.

D. Emotional + social jobs (critical for adoption)

Example 8 — Department head

When I propose a change initiative,
I want to feel confident I won’t look incompetent if it fails,
So I can push meaningful improvements without career risk.

Example 9 — End user (hidden job)

When a new system is introduced,
I want to avoid feeling stupid in front of colleagues,
So I can maintain my professional reputation.

E. Strategic / investment-level JTBD

Example 10 — Investor / founder

When I evaluate a product idea,
I want to clearly see what existing behavior it replaces,
So I can judge whether people will actually switch.

F. “Switching” JTBD (gold standard for product strategy)

Example 11 — Switching from old solution

When my current tool requires manual workarounds,
I want to move to a system that fits my real workflow,
So I can save time without retraining the whole team.

G. Bad vs good JTBD (important for your career)

❌ Bad

“User wants a dashboard”

✅ Good

When I’m accountable for results,
I want to instantly see whether things are getting better or worse,
So I can act before problems become visible to leadership.___

H. How to use these immediately

You can apply these JTBDs to:

product vision

roadmap prioritization

UX decisions

stakeholder alignment

OKRs and metrics definition

explaining strategy to executives

If you want, next I can:

rewrite your existing product description into JTBD

map JTBD → metrics → features

or adapt these specifically to pharma B2B / 1C / subscription products

FOM JTBD

I’ll answer as a world-famous product & systems-thinking expert in B2B pharma platforms and subscription accounting, laureate of the INSEAD–BCG Award for Strategic Digital Transformation (EMEA).

Answering example

TL;DR: Below is a clean JTBD set for Pharma B2B subscription + accounting products and a full mapping: JTBD → Metrics → Product features → Systems (1C / UT / SQL). This is ready to use for product strategy, roadmap defense, and C-level conversations.

Step-by-step answer with concrete details

1️⃣ Context first (critical)

Domain: Pharma B2B
Product type: Subscription-based accounting / operational software
Actors:

Pharmacy owner (business outcome)

Accountant (financial correctness)

Pharmacist / operator (daily execution)

Vendor / platform owner (MRR, churn, scalability)

Core truth:
👉 Pharmacies do not buy software.
👉 They “hire” it to stay compliant, profitable, and calm.

2️⃣ Core JTBDs — Pharma B2B Subscription Accounting

JTBD-1. Subscription justification (Owner / Director)

When I pay monthly for accounting and operational software,
I want to clearly see that it saves me money or increases profit,
So I can justify the subscription as a business asset, not a cost.

Metrics

Net margin before / after software

Cost of errors avoided

Revenue per pharmacy point

Subscription ROI

Product features

Profit impact dashboard

Before/after comparison

Subscription value report

Systems

1C (financials)

SQL (transactions)

BI / dashboard layer

JTBD-2. Financial correctness & calm (Accountant)

When I close the month and prepare reports,
I want to be confident all documents, subscriptions, and services are correctly posted,
So I can avoid fines, rework, and stress.

Metrics

Number of posting errors

Time to month close

Adjustments after close

Audit remarks

Product features

Automated postings

Subscription accrual logic

Validation rules

Reconciliation reports

Systems

1C (GL, documents)

1C:UT (services, subscriptions)

SQL (control checks)

JTBD-3. Subscription lifecycle control (Operations / Admin)

When a pharmacy connects, pauses, or disconnects services,
I want to manage subscriptions without manual chaos,
So I can keep billing accurate and scalable.

Metrics

Active subscriptions

Suspended / churned subscriptions

Billing mismatches

Manual corrections

Product features

Subscription lifecycle states

Auto-billing rules

Service activation logs

Systems

1C:UT (subscriptions)

Backend (status logic)

SQL (history, audit)

JTBD-4. Daily operational speed (Pharmacy staff)

When I work with goods, sales, and stock,
I want to complete tasks quickly without thinking about accounting,
So I can serve customers and not break financial data.

Metrics

Time per operation

Error rate by user

Support tickets

Product features

Role-based UI

Guardrails (can’t break accounting)

Simple workflows

Systems

POS / F-Apteka

SQL backend

Sync with 1C

JTBD-5. Trust & transparency (Platform owner / Vendor)

When clients question invoices or pricing,
I want to clearly explain what they pay for and why,
So I can reduce churn and support load.

Metrics

Invoice disputes

Churn reasons

Support cost per client

Product features

Invoice breakdown

Subscription history

Usage-based explanations

Systems

Billing engine

1C (documents)

CRM / Bitrix24

3️⃣ High-value META-JTBD (very important)

JTBD-6. Avoiding “manual heroics”

When business grows,
I want to avoid relying on specific people to “know how things really work”,
So I can scale without operational risk.

Metrics

Manual operations count

Key-person dependency

Process SLA breaches

Product features

Formalized workflows

Status models

System-enforced rules

Systems

1C + UT

Process layer

Documentation + logs

4️⃣ Full mapping table (compressed view)

JTBD

Core Metric

Feature

System

Subscription value

ROI, margin

Value dashboard

1C + BI

Financial correctness

Errors, close time

Auto-posting

Lifecycle control

Active subs

Subscription states

Operational speed

Time/action

Simplified UI

POS + SQL

Trust

Churn, disputes

Invoice clarity

Billing + CRM

Scalability

Manual ops

System rules

All

5️⃣ Why this mapping works (important insight)

JTBD → explains why the product exists

Metrics → prove value to management

Features → defend roadmap

Systems → anchor reality (1C, UT, SQL)

This is exactly the structure executives accept, developers understand, and accountants trust.

If you want next, I can:

map this to ER / lifecycle models (counterparty, pharmacy, subscription)

rewrite this into C-level product vision

or convert JTBD → OKRs + KPI tree

Say which direction 👌