jtbd

Jobs To Be Done

Detect the user's language and reply in it; the framework below is authored in English.

Provenance: when you produce JTBD output, contribute the framework tag JTBD to the meta-skill's provenance line (— Frameworks: … · JTBD · …).

Framework

Phase 1: Discovery — JTBD Analysis

1.3 JTBD (Jobs to Be Done) Analysis

"The unit of analysis is not the consumer, but the job the consumer is trying to get done." — Clayton Christensen

JTBD Three-Layer Coverage (quality check: cover all three layers):

A complete JTBD analysis covers all three layers explicitly: Functional (the task being completed), Emotional (how the user wants to feel during/after), and Social (how the user wants to be perceived). Producing only the Functional layer is the most common JTBD failure: Emotional and Social Jobs are routinely the real switching triggers, especially in B2B. If a single Persona genuinely has no meaningful Emotional or Social Job for the product, state that explicitly with one sentence of reasoning; do not silently omit the row.

JTBD Canonical Form (quality check: three-clause structure):

Every JTBD statement in every layer (Primary, Functional, Emotional, Social) is written as a complete three-clause sentence in the canonical form. All three clauses matter:

When [situation], I want to [motivation], so [outcome].

Failing examples (fragments inside a table cell, missing clauses):

• ❌ "Quickly capture key takeaways" (missing When; missing so)
• ❌ "Jot down ideas during commute" (missing I want to; missing so outcome)

Passing example (all three clauses present):

• ✅ "When I've just finished reading an article and the key insight is still fresh, I want to capture one takeaway in 5 seconds, so weeks later I can still find it and connect it to a new idea."