Free: The 7-Day Idea Test — validate any business idea in one week Get the Playbook →

The JTBD Format: How to Write a Jobs-to-be-Done Statement

10 min read
In this article

You can describe your idea by who it’s for, or by what it does. Neither one tells you why anyone would switch from what they do now. The JTBD format fixes that. One sentence, three parts, zero features.


A person writing in a planner at a desk, organizing notes

What the JTBD Format Actually Is

Jobs-to-be-Done (JTBD) statement format is a single-sentence template for describing the progress a customer is trying to make in their life, independent of any product or feature. Clayton Christensen and his co-authors laid out the framework in Harvard Business Review, using the now-famous example of a fast-food chain that discovered people were not “hiring” its milkshake for taste. They were hiring it for a long, one-handed commute that would keep them occupied and not hungry until lunch. Same product, completely different job depending on the hour of day.

The format exists because most founders describe ideas backward. They start with the solution (“an app that tracks X”) and work toward a justification. The JTBD statement forces the opposite order: name the situation and the struggle first, and let the solution stay out of the sentence entirely.

For BeforeYouBuild’s purposes, this matters at one specific moment: before you build anything. A clean JTBD statement is a test. If you cannot write one without smuggling your product into it, you do not yet understand the job you think you are solving. That gap is cheap to find on paper and expensive to find after three months of development.


The Core Statement Format

The classic JTBD statement has three parts, in this order:

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

Each slot does specific work:

  • Situation. The circumstance that triggers the need. Specific enough to picture, not a demographic label. “When I am driving alone for more than 30 minutes” is a situation. “As a busy professional” is not.
  • Motivation. What the person is actively trying to do in that moment. This is a verb phrase, and it should describe an action, not a feeling about a product category.
  • Expected outcome. The state the person wants to reach. This is the actual finish line. It has nothing to do with features, screens, or pricing tiers.

Annotated example, continuing the milkshake case:

When I’m driving to work with nothing else to do for 20 minutes (situation), I want something filling and easy to consume one-handed (motivation), so I can arrive at work satisfied and not hungry before lunch (expected outcome).

Notice what is missing: no mention of milkshakes, smoothies, bagels, or any specific product. That is the format working correctly. A solution can satisfy this job. A solution is not part of the job statement itself.

Sticky notes organized in rows on a wall


Job Story Format: The Software-Native Variant

If you are evaluating a SaaS or digital product idea, you will more often see the job story format, developed by Alan Klement and popularized inside product teams through a guest post on Intercom’s blog. It keeps the same three-part logic but swaps the language for something closer to a product backlog:

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

The structural difference from the classic Christensen statement is subtle: job stories tend to describe a narrower, more immediate situation (a moment inside a workflow) rather than a broad life circumstance. Compare:

FormatExample
Classic JTBD statement“When I’m evaluating whether to pursue a new business idea, I want a structured way to score it, so I can decide without relying on gut feeling.”
Job story“When I finish a customer interview, I want to log what I heard against my assumptions immediately, so I can spot patterns before I forget the details.”

Both are valid JTBD format. The job story is simply scoped to a single moment inside a product experience, which is why product and engineering teams favor it for feature-level decisions, while the broader statement is more useful for evaluating whether an entire idea deserves to exist.


Functional, Emotional, and Social Dimensions

A format mistake that looks correct on the page: writing a JTBD statement that only captures the functional job and missing the other two dimensions entirely. Christensen’s research and later work by Ulwick’s Outcome-Driven Innovation school both treat a job as having up to three layers:

  • Functional. The practical task. “Get from point A to point B.” “Track monthly expenses.”
  • Emotional. How the person wants to feel while doing it, or after. “Feel in control of my finances.” “Not feel embarrassed showing up unprepared.”
  • Social. How the person wants to be perceived by others while getting the job done. “Be seen as the organized one on the team.”

You do not need three separate statements. You need to check whether your single statement is accidentally functional-only when the real switching trigger is emotional or social. A budgeting app that nails the functional job (tracking expenses) but ignores the emotional job (not feeling anxious opening the app) will lose to a worse tracker that feels calmer to use. Write the statement, then ask: if I only solve the functional part, does this job actually feel done to the person experiencing it?


Formatting Mistakes That Smuggle in a Solution

Most bad JTBD statements fail in one of four specific ways:

  1. The solution hides inside the motivation. “I want to use a mobile app to track expenses” names a product, not a job. Rewrite the motivation as the underlying action: “I want to know where my money went this week.”
  2. The situation is a demographic, not a moment. “As a solopreneur” describes a person, not a trigger. A moment is specific: “When I notice my bank balance is lower than expected.”
  3. The outcome is vague enough to mean anything. “So I can be successful” or “so I can feel good” cannot be tested against. A usable outcome is specific enough that you could ask someone six months later whether they got there: “so I can know, without opening a spreadsheet, whether I can afford a slow month.”
  4. The statement describes a feature request, not a struggle. “I want a dashboard that shows me three charts” is a wish list item. The job underneath it might be “I want to know, in five seconds, whether this month is on track” — and a dashboard is only one of several ways to satisfy that.

Close-up of hands typing on a laptop keyboard with text visible on screen

If your draft statement reads naturally with a specific product name inserted into it, the format has failed. A correct JTBD statement should sound slightly awkward if you try to insert your solution, because the solution was never supposed to live in that sentence.


Writing One From Scratch: A Worked Example

Say you have an idea for a tool that helps freelancers send better client proposals. Here is the format applied step by step:

Step 1: Name the trigger moment, not the role. Not “as a freelancer” but “when a potential client asks for a proposal after an initial call.”

Step 2: Name the actual action being attempted, stripped of any tool. Not “I want proposal software” but “I want to put together something professional-looking fast, before the client’s interest cools off.”

Step 3: Name the finish line, specific enough to fail or succeed against. Not “so I can win more clients” (too broad to test) but “so I can send it within 24 hours without looking like I threw it together.”

Combined statement:

When a potential client asks for a proposal right after our call, I want to put together something professional-looking fast, so I can send it within 24 hours without looking rushed.

Notice this statement is already useful before you have built anything. You can take it into five conversations with freelancers and ask: does this match your experience? Where does it break down? You cannot run that same test on “I want proposal software,” because that sentence does not describe a moment anyone recognizes living through.


Using the Format Inside an Evaluation, Not as the Finish Line

A clean JTBD statement is an input to your evaluation, not the evaluation itself. Once you have a statement that survives the mistakes above, the next step is checking it against real behavior: has anyone already tried to solve this job, badly or otherwise? The idea validation framework covers how problem fit and demand signals fit together once you have a job worth testing. If you have not yet run customer conversations to confirm the job is real rather than assumed, the Mom Test question bank gives you the exact questions to ask without leading the answer.

The format is cheap. It costs you fifteen minutes and a blank page. The mistake to avoid is treating a well-formatted statement as proof the job is real. It is a hypothesis written clearly enough to test, nothing more.


Frequently Asked Questions

What is the JTBD format in one sentence?

It is a three-part template, “when [situation], I want to [motivation], so I can [expected outcome],” used to describe the progress a customer is trying to make without naming any product or feature.

What is the difference between a JTBD statement and a job story?

They share the same three-part structure. In practice, job stories (the Intercom/Alan Klement variant) tend to describe a narrower moment inside a specific product workflow, while the classic Christensen-style JTBD statement usually describes a broader life circumstance. Use the broad version to evaluate whether an idea deserves to exist; use the narrower job story once you are deciding between specific features.

Do I need to interview customers before I can write a JTBD statement?

No. You can draft a first version from your own observation or experience. What you cannot do is treat that first draft as confirmed. Writing the statement is step one. Testing it against real conversations, where people describe their situation in their own words, is what tells you whether the statement matches reality or just your assumption about reality.

Can one idea have more than one JTBD statement?

Yes, and this is common. Different customer segments, or the same person at different moments, often hire a similar solution for different jobs (the milkshake example is the classic case). If you find yourself writing several unrelated statements for one idea, that is a sign to pick the one with the strongest evidence behind it and evaluate that one first, rather than trying to serve all of them in a single version of the product.

Why does the statement leave out the solution entirely?

Because the job existed before your product idea did, and it will keep existing if your specific idea fails. Separating the job from the solution is what lets you test demand for the underlying struggle before you have committed to one particular way of solving it. If the solution is baked into the statement, you can no longer tell whether people want the job solved or just agreed to be polite about your specific idea.


Two people reviewing a document together at a table

Turn the Statement Into a Decision

A well-formatted JTBD statement tells you what to test. It does not tell you whether to build. That is a separate step, and it is the one most people skip.

The Idea Validation Scorecard takes the job you have defined and scores it against nine other evaluation criteria, including demand signals and willingness to pay, to produce a go, wait, or kill recommendation.

Run the Idea Validation Scorecard →

Free. About 15 minutes. No email required.


Keep Reading

What to Do Next

Choose the path that fits where you are right now.

Get the 7-Day Idea Test (Free)

Download the free 7-Day Idea Test. One task per day. Four evidence signals. One clear go, wait, or kill result — before you spend months building the wrong thing.

Send Me the Playbook

Choose Your Next Step

Find the path that fits where you are right now.

Get the Playbook

Start Reading

Read the step-by-step setup guide for your platform.

Free Download

Get the 7-Day Idea Test (Free)

Seven focused days. One task per day. By Day 7 you will know — with real evidence — whether your idea is worth pursuing. Free PDF, instant delivery.

Free. No spam. Unsubscribe anytime.