Target user and JTBD

One-liner: Describe a primary user and their core job to be done.
Time: 20 to 30 min
Deliverable: Persona and JTBD Statement

Learning goal

You will be able to: Define a primary user and a clear job to be done for your AI app.

Success criteria (observable)

• The persona includes role, context, and constraints.
• The JTBD statement follows a clear structure.
• The statement matches the chosen problem.

Output you will produce

• Deliverable: Persona and JTBD Statement
• Format: One page doc
• Where saved: Course folder under /generative-ai-2026-build-ai-apps-and-agents/

Who

Primary persona: Digital nomad building for a defined niche Secondary persona(s): Users who influence purchase Stakeholders (optional): Anyone who approves budgets

What

What it is

A persona that captures role, context, and constraints plus a JTBD statement that names the outcome. Together they anchor what you build and how you explain it.

What it is not

It is not a demographic profile or a list of features.

2-minute theory

• JTBD focuses on the outcome a user hires the product to achieve.
• Personas add real world context so the outcome is believable.
• Clear JTBD makes messaging and UX decisions simpler.

Key terms

• JTBD: The job a user hires a product to do.
• Persona: A short profile that describes a target user and context.

Where

Applies in

• Product decisions
• Marketing and onboarding

Does not apply in

• Low level performance tuning

Touchpoints

• Landing page
• Onboarding
• Support articles

When

Use it when

• You have selected a problem and niche
• You need to align features to outcomes

Frequency

Once per product idea, revisit quarterly

Late signals

• Features do not map to a user goal
• Messaging feels generic

Why it matters

Practical benefits

• Clearer product scope
• Better sales messaging
• Faster user validation

Risks of ignoring

• Building for the wrong user
• Confusing product narrative

Expectations

• Improves: clarity and focus
• Does not guarantee: conversion

How

Step-by-step method

1. Name the primary user role and context.
2. List top constraints and pain points.
3. Write a JTBD statement with outcome and timeframe.
4. Validate it against your problem and niche.

Do and don't

Do

• Make the JTBD outcome concrete and time bound
• Keep the persona short and realistic

Don't

• Use demographics without context
• Write a JTBD that sounds like a feature list

Common mistakes and fixes

• Mistake: Persona is too broad. Fix: Add role and workflow.
• Mistake: JTBD is vague. Fix: Add outcome and time constraint.

Done when

• Persona includes role, context, and constraints.
• JTBD statement has a clear outcome.
• Statement matches the chosen problem.

Guided exercise (10 to 15 min)

Inputs

• Your selected problem
• Notes about user workflows

Steps

1. Draft a three line persona.
2. Write one JTBD statement.
3. Check it against the problem statement.

Output format

Field	Value
Persona
JTBD statement
Key constraints
Proof it matches the problem

Pro tip: If you can swap the user role without changing the JTBD, it is too broad.

Independent exercise (5 to 10 min)

Task

Tighten the JTBD statement by removing vague words.

Output

A revised JTBD statement.

Self-check (yes/no)

• Does the persona include role and context?
• Does the JTBD name a concrete outcome?
• Is the time or situation explicit?
• Does it align with the problem?

Baseline metric (recommended)

• Score: 3 of 4 checks met
• Date: 2026-02-06
• Tool used: Notes app

Bibliography (sources used)

1. Jobs to Be Done Theory. Strategyn. 2024-01-01. Read: https://strategyn.com/jobs-to-be-done/

2. Competing Against Luck. Clayton Christensen. 2024-01-01. Read: https://hbr.org/product/competing-against-luck/8654-PDF-ENG

Read more (optional)

1. JTBD Canvas Why: Helps structure outcome focused product thinking. Read: https://jtbd.info/