The Jobs-to-be-Done framing skill.

What this skill is for

The PM suite, grouped by where work happens.

JTBD-framing sits in upstream work: a framing technique applied within discovery synthesis, prioritization debates, and positioning work. Distinct from broader synthesis discipline that covers the full sequence regardless of which framing techniques apply.

The job statement structure

Three parts. Each demands specificity.

The structure forces specificity at all three levels. Vague situations, vague motivations, or vague outcomes produce job statements that drive nothing. Strong job statements emerge from interview data through clustering, not from whiteboard sessions.

What is in the skill

Thirteen sections covered in the body.

1. 01

   What this skill is for

   JTBD as framing technique. Distinct from discovery-research-synthesis (broader synthesis). Used in discovery, prioritization, positioning.

2. 02

   Feature-request-list vs persona-theater vs job-framing

   The keystone framing. Users hire products to do jobs; not preferences, not demographics.

3. 03

   The job statement structure

   When [situation], I want to [motivation], so I can [outcome]. Each level demands specificity.

4. 04

   Identifying struggling moments

   Jobs become visible at struggling moments. Discovery prompts that surface them. The recency-bias-as-feature principle.

5. 05

   Hire and fire criteria

   Why users adopt; why they switch away. Recent-switch interview discipline.

6. 06

   Functional, emotional, and social dimensions

   Three dimensions per job. Functional-only synthesis fails. Emotional dimension drives product feel; social dimension drives positioning.

7. 07

   Where JTBD adds clarity vs becomes ritual

   Honest about both modes. Discovery, prioritization, positioning. Not as ritual everywhere.

8. 08

   Applying JTBD to discovery

   Interview structure around jobs. Job clustering. Naming jobs from data. Pairs with discovery-research-synthesis.

9. 09

   Applying JTBD to prioritization

   Roadmap candidates evaluated by jobs. The 'no job, no priority' discipline. Pairs with roadmap-planning.

10. 10

    Applying JTBD to positioning

    Job-led vs feature-led positioning. Lead with what the product helps users accomplish. Pairs with creative-direction.

11. 11

    Common failure modes

    9+ patterns: workshop-as-deliverable, generic statements, feature-request statements, persona-job conflict, JTBD-as-mandate, functional-only.

12. 12

    The framework: 12 considerations

    Job-framing not feature-list, statement structure, struggling moments ground jobs, hire/fire criteria, functional-emotional-social, jobs from data, applied where it earns its keep.

13. 13

    Closing: jobs over features

    JTBD applied with rigor produces decisions; applied as ritual produces ceremony. The teams that benefit are the ones doing the analytical work.

Pairs with these platforms

Two platforms with JTBD-relevant workflows.

The skill is platform-agnostic. These platforms ship workflows that fit JTBD application: Notion (job statement libraries, struggling moments tracking), AirOps (workflows that generate job-statement candidates from interview data with human review).

• Notion-centric teams

  Notion

  Briefs as a queryable database

  Open the page

• Content teams that prefer managed workflow builders to build-it-yourself pipelines

  AirOps

  AirOps's official MCP and Claude Connector for AEO data and Brand Kits

  Open the page

Direction 7 closes

The second of five PM skills closing Direction 7.

Frequently asked questions.

What does 'jobs over features' actually mean?

Users hire products to do jobs. The job is what the user is trying to accomplish, not who the user is or what features they request. Job-framing produces decisions grounded in user motivation rather than user description (personas) or user preference (feature requests). The litmus test: take a product decision the team is debating and see if JTBD framing produces clearer arguments. If yes, the framing is earning its keep. If JTBD just adds vocabulary without resolving the debate, the framing is ritual.

When does JTBD become ritual?

Common ritual patterns: job-statement workshops as deliverables (the workshop produced artifacts; nothing changed in roadmap); job statements substituted for personas without analytical rigor; mandatory JTBD for every product question regardless of fit; JTBD as compliance because a leadership book endorsed it. The honest signal: if the team can show how recent product decisions were different because of JTBD analysis, the framework is earning its keep. If the team uses JTBD vocabulary but cannot trace decisions to JTBD analysis, it is ritual.

How is JTBD different from personas?

Personas are demographic; JTBD jobs are situational. 'Marketing Manager Maria, 35, urban' is a persona. 'When my team is rolling out a new feature and I need to communicate it to customers, I want to write a clear announcement, so I can ship without flooding support with confusion' is a job. Personas describe who; jobs describe what users are trying to accomplish. The two can coexist; JTBD is usually better for product decisions; personas are sometimes useful for marketing audience targeting. Conflict between the two often signals confusion about which framework drives which decisions.

What is the job statement structure?

When [situation], I want to [motivation], so I can [outcome]. Each level demands specificity. The situation is a moment, not a demographic. The motivation is product-independent and goal-directed (what the user is trying to do, not what feature they want). The outcome is the user's success criterion, not a feature output. Vague situations, vague motivations, or vague outcomes produce job statements that drive nothing. Strong job statements emerge from interview data through clustering, not from whiteboard sessions.

What are functional, emotional, and social dimensions?

Jobs have three dimensions. Functional: what the user is mechanically trying to do (assemble the board deck). Emotional: how the user wants to feel (confident the deck represents real progress; in control rather than behind). Social: how the user wants to be perceived (seen by the board as competent). Strong JTBD work surfaces all three; weak work is functional-only. Products that win on functional alone often lose to alternatives that also serve emotional and social. The social dimension is often the strongest for positioning.

Where does JTBD genuinely earn its keep?

Three modes: discovery (interviews structured around struggling moments and hire/fire decisions produce richer data than feature-elicitation interviews); prioritization (jobs ground roadmap debates in what users are trying to accomplish, cutting through stakeholder politics); positioning (job-led messages create stronger affinity than feature-led comparisons). Outside these modes, JTBD often becomes overhead without proportional value. The discipline is using JTBD where it adds clarity and skipping it where it would become ritual.