What a Job Actually Is

A Job Is a Structured Story of Motivation

The previous chapter left us with a causal chain. A customer problem is downstream. A Solution was hired for a Job. The Solution underperformed. A Problem appeared.

In AJTBD, a Job is a unit of motivation: a description of the person's current situation, the transition they expect to perform, the expected outcome they want to reach, and the higher-level Job they are trying to perform by reaching it, ultimately to satisfy a need.

Here is a fully described Job for Skyscanner:

• When
  • Context:
    • I am a parent in Austin.
    • My PTO dates are approved.
    • The family will travel for a week.
    • The budget is real, and itinerary quality matters too.
    • We have checked bags, and the kids need the trip to be physically manageable.
  • Negative emotions: I am afraid to buy the wrong tickets: hidden baggage costs, a brutal layover, seats split across the cabin, or a schedule that makes the first day of vacation miserable.
  • Consideration Set: I know the usual ways to do this — Google Flights, Kayak, the airline sites — and I know it can be worth paying more through a reliable seller if the total trip becomes safer: bags included, normal connections, seats together, fewer support nightmares if something changes.
  • Trigger: My manager approves the vacation dates, so the trip moves from "we might go" to "I need to buy the flights."
• I want [expected outcome]: "buy round-trip flights from Austin to Cabo for my family."
  • Success criteria:
    • Total fare under $3,800 including bags.
    • All connections finish the same day.
    • Connection window between 90 minutes and three hours, manageable with kids.
    • Four seats together.
    • Arrival time preserves the first vacation day.
• So I can
  • Higher-level Job: "start the family trip with budget, logistics, and seating under control before we leave."
  • Positive emotions: feel relief, control, anticipation, and the quiet satisfaction that the trip is real and already stable.

This is a Job. Google Flights, Kayak, Expedia, Costco Travel, an airline website, a travel agent, or a spreadsheet of possible itineraries are possible Solutions for performing it. The Job is the motivation structure that makes one of those Solutions worth hiring.

The same Job can be written at three fidelity levels:

Short form: "I want to buy round-trip flights for my family, with seats together, under $3,800."

Working form: "When my vacation dates are approved and I am booking for a family of four, I want to buy round-trip flights from Austin to Cabo with workable layovers, seats together, baggage included, and a total price we can absorb, so I can start the trip with the plan already stable before we leave."

Full form: the eight-element structure above.

The short form works in speech, the working form in briefs, design reviews, and positioning. The full form is the source of truth when the decision is expensive: which segment to serve, which Solution to build, which criteria to optimize, which competitors matter, what to charge for, what promise the product can truthfully make.

Notice that even the short form keeps the main success criteria. Compress past them and the line stops naming a Job — it becomes a bare verb that several different Jobs can hide under.

A Job Specifies the Transition Behind the Booking Session

The Skyscanner example above specifies the transition the person wants to perform. It sets the conditions a Solution must satisfy before the customer can judge it good.

The specification is not the performance. One performance might look like this: Thursday at 9:40 p.m., the parent opens Skyscanner, filters Austin to Cabo, checks baggage rules, rejects a cheaper itinerary with an overnight layover, compares the airline site, texts the spouse about the $3,740 option, chooses seats together, and finally buys. That one evening is one performance of the Job. The Job is the motivation structure that made that evening make sense.

The Job can repeat; each performance happens once. Next year the same parent may perform a similar Job with different dates, prices, constraints, and stress level. Treating one performance as the Job overgeneralizes a single story. Naming only the handle loses the story entirely.

The eight elements are a working map of the transition the customer's brain already has to predict before action begins. Each one captures a different piece of the information the person uses to decide whether the transition is worth performing.

Context tells us which situation produces these criteria. It is the set of features of the person and the situation that makes this person want this outcome with these criteria. In the Skyscanner Job, parent, Austin, spring break, approved PTO, two kids, real budget, checked bags all matter because they change what "good flight" means. Details that leave the criteria unchanged stay outside the Job-record. Context is used for segmentation, research recruiting, routing, and personalization: it tells the team when a shared expected outcome belongs to separate Jobs.

Negative emotions tell us what staying in the current situation costs. Fear, anxiety, frustration, impatience, shame, and doubt signal that staying where they are is expensive for the person. In the flight example, fare comparison sits inside a larger fear: creating a bad trip before the trip begins. Negative emotions are used to estimate intensity, write communication in the customer's actual language, and discover which higher-level motivation really matters. Job-records that skip these emotions usually stay under-specified.

The Consideration Set is what the person already knows about ways to get this done. It is the knowledge loaded in the customer's head before action starts: which ways exist, which concrete products can perform them, how they compare, and which fears are already reduced enough to consider acting. The parent knows reliable travel sellers can show total prices, baggage rules, connections, seat options, and support paths before purchase. A different set of knowledge would send the same Trigger toward a travel agent, a friend, or a delay. The Consideration Set is used in acquisition and education, because it decides which way the customer even considers when the moment to act arrives.

The Trigger tells us why action starts now. A customer can live in the right context, with the Job half-awake, for weeks. The Trigger is the internal or external event that flips them from considering the Job to spending energy on it. In the Skyscanner example, the approved PTO is the moment the trip stops being hypothetical. Trigger knowledge is used for timing: outreach, reminders, lifecycle messaging, partner placement, and sales motion work better when they meet the customer at the moment the Job becomes active.

The expected outcome is the primary Job phrase. This is the I want to + infinitive part: "I want to buy round-trip flights from Austin to Cabo for my family." It names the end state the person is trying to reach. People remember it as the handle, so it works in speech; source-of-truth records need the rest of the Job structure around it. The outcome must stay active and verbal. Noun phrases like "flight booking" or "retirement management" hide the motivation and turn the Job back into a category label.

Success criteria define what "good enough" means. Criteria are the operational spec of the expected outcome: under $3,800, same-day connections, seats together, bags included, arrival time that preserves day one. Criteria need concreteness more than numbers; a qualitative criterion is usable if the team can tell when it has been met. Success criteria are used to design the product, measure value delivery, define activation, price the offer, and split segments. The minimum viable Job-record is expected outcome plus success criteria. Further compression removes the precision the team needs to build.

The Higher-level Job tells us what this Job is for. The parent wants the booking confirmation because it starts the family trip with budget, logistics, and seating under control. The Higher-level Job carries the motivation above the expected outcome and keeps the team from mistaking the product's task for the customer's purpose. It is used in positioning, roadmap scope, and strategy. It also sets a limit: claim your product performs the Higher-level Job after it performs all the Jobs underneath it.

Positive emotions tell us how the customer expects to feel once the Job lands. Relief, control, anticipation, calm, pride, and confidence are part of the desired arrival. They are the emotional side of "the Job landed." Positive emotions are used in communication, onboarding, Aha design, and trust calibration. A functional outcome paired with exposure, confusion, or fear signals an unfinished transition.

Later in the book, we will make the brain side explicit: the brain predicts, spends energy, compares what happened with what it expected, and uses emotion as a signal of movement toward or away from goals. For now, the practical consequence is enough: a person evaluates the predicted transition.

Criteria Split One Expected Outcome Into Several Jobs

The fastest way to see the structure is to hold the expected outcome steady and inspect how criteria change.

Take "I want to buy flights." A parent booking spring-break flights for a family needs seats together, bags included, and layovers the kids can survive. A consultant flying to a Monday client meeting needs a schedule that protects arrival certainty and can be changed if the meeting moves. A college student flying home needs the lowest cash price with a workable airport transfer. An office manager booking an offsite needs receipts, policy compliance, and a way to coordinate several travelers while staying out of help-desk mode.

One handle can sit above several criteria stacks. Each criteria stack marks a separate Job.

The same split runs at solo scale. "Get my first 100 users" is one handle: a venture-track founder needs them this month, with a growth story to show investors; a solo builder needs them paying, organic, and cheap to support. Two criteria stacks, two Jobs — and two different products to build.

The pattern appears outside travel too. TurboTax, a CPA, and IRS Free File all sit under "file my tax return"; ChatGPT, Stack Overflow, and a senior engineer all sit under "unblock this code problem"; Coursera, a private tutor, and an internal company workshop all sit under "learn this skill." Categories form around the verb. Competitive sets form around the criteria.

This is where segmentation begins to become causal. Shared segment membership requires a similar expected outcome, context, and success criteria. Different criteria under one expected outcome produce separate Jobs, separate value logic, separate fears, separate willingness to pay, and often separate products.

Each Verb Is a Separate Job

The second discipline is grammar.

A Job statement contains exactly one "I want to + infinitive" clause. When a sentence contains two infinitive verbs, the sentence is usually hiding a hierarchy.

"I want to rent out my duplex and generate predictable monthly income" sounds natural. It hides two Jobs.

"Rent out my duplex" is one Job. It is performed in order to "generate predictable monthly income from my real estate," which is a higher-level Job. If a founder leaves both verbs in one sentence, the product team loses the hierarchy. Property management features, tenant-screening workflows, rent-collection reliability, financial reporting, and owner anxiety all collapse into one foggy line.

This matters because a product's promise attaches to a specific Job and contributes selectively upward. A rental-management company may fully perform "find and manage a tenant for my duplex" and help the owner perform "generate predictable monthly income from my real estate." "Build long-term financial security for my family" remains a higher motivation above the service's actual reach. Saying the higher-level Job out loud is valuable. Claiming the product performs it fully creates strategic confusion and bad promises.

The same grammar check saves many product discussions:

• "Create invoices and get paid faster" splits into "create invoices" and "get paid faster."
• "Publish content and grow my audience" splits into "publish content" and "grow my audience."
• "Analyze churn and convince the executive team to fund retention work" splits into "analyze churn" and "convince the executive team to fund retention work."

The connector words are clues: and, to, so that, in order to, while. They usually mean the team is holding two Jobs at once. Parse the hierarchy before using the statement.

Wes Calls It a Spreadsheet

Match the depth of the Job-record to the weight of the decision: full for choosing where to compete, light for everyday product work. And interviews are not the only source: reviews, sales-call fragments, support tickets, onboarding notes, and lost-deal notes can all be parsed into Job hypotheses — by hand or with an LLM — and they stay hypotheses until a real past performance confirms them.