The Typical Next Move Theory Case
In 2023, a dental-clinic owner applied AJTBD to the business and ran twenty interviews with satisfied, high-margin clients.
The team chose one Core Job: "I want to get my whole mouth restored in a single day." The segment had many dental problems, enough money, and one dominant success criterion: everything done in one visit, asleep for all of it — sleep dentistry, in the trade — instead of feeding the problem one tooth and one appointment at a time.
The clinic rebuilt the diagnostic session, the lab workflow, the communication, and the landing page around that Core Job. Conversion grew by about 40%, and monthly revenue by about 37% — the numbers are in the full case study.
This is a typical case. I have watched hundreds of my graduates run the same move: find the most profitable Core Job where they can create added value and attract customers, then focus the product and communication around it — instead of letting the company serve five implicit segments at once.
The usual product story is more embarrassing.
A stakeholder has a brilliant idea. The idea survives a CEO meeting. Money appears. A commitment appears. Then the stakeholder walks to the product lead: "We need to build this."
The product lead looks at it and thinks, "No one needs this." He runs a dozen interviews, hears polite vagueness instead of demand, and says it again: "I don't think anyone needs this." The answer comes back: "We already committed."
So they build.
Then marketing and sales ask, "What are we supposed to say?" Product answers, "Here are the features we shipped. Also, it has AI." Marketing turns the features into nicer sentences. Sales gets a deck. Launch goes out.
The stakeholder reports launch. The product slowly dies.
The model underneath that story is the one almost every company runs: value is the product team's craft, messaging is marketing's, pricing is finance's, the funnel is growth's — separate disciplines, separate owners, glued together in coordination meetings. It is wrong, and the story above is what being wrong looks like from inside.
Nothing mysterious happened. The customer's Core Job was never chosen, so every handoff replaced it with something easier to carry: commitment, feature list, AI label, launch report. The org chart made one upstream absence look like separate problems: weak product, weak messaging, weak conversion.
The Nature of Product Is to Perform Core Jobs
Your product exists to produce planned profit. It has one way to do that: performing important Core Jobs for enough people more energy-efficiently than their alternatives — faster, easier, simpler, cheaper, calmer, safer.
That is the entire demand side of business: people getting their Core Jobs done. People Don't Need Our Products. They do not care about the technology, features, or business model. They want to move from State A to State B with less energy than expected and feel the small positive shock of "oh, this actually did it."
The strange part is how few founders, product managers, and marketers truly operate from this. Many know the sentence. Few let it decide the roadmap, pricing, landing page, sales script, funnel, operations, and unit economics.
Christensen saw the unit — the Job. Goldratt taught that one upstream constraint decides what every downstream effort is worth. Push both ideas to their limit and you arrive at the conclusion it took me thirteen years of studying strategy to accept: strategy reduces to one type of decision.
Everything in product, marketing, and communication flows from the Core Jobs our product competes to perform.
Watch the clinic do it, artifact by artifact.
The Jobs came first. Choosing the right Core Jobs of the right segment is more than half the success — everything after follows from that choice. The clinic spent its twenty interviews on exactly that choice.
Then came value. Value is energy efficiency: the more energy-efficiently a product performs the Job, the stronger the customer's pull toward it. For the chosen segment the Job was "get my whole mouth restored in a single day," so value lived in completeness: one diagnostic, one plan, one price, one day under sedation. The same waiting room held people with a different Job — "fix this one aching tooth, cheap, after work" — and for them value lived in price and an evening slot. Same clinic, same chairs, two Jobs, two definitions of better. The team does not get to define "better" from the inside; the target segment's success criteria define it. A team that designs for the criterion it personally admires is usually designing for itself.
The landing page rewrote itself next. Communication is the transmission of already-created value to the target segment — and after twenty interviews, the headline was already sitting in the transcripts: the whole mouth, one day, asleep, handled. Before, the page said what every clinic's page says: modern equipment, caring doctors, an individual approach. After, it named the Job and the criteria in the patient's own words. The 3D scanner and the in-house lab stayed on the page — demoted from message to proof.
That demotion is the general rule. Feature-first copy makes the customer translate your mechanism into their own situation, and most customers will not do that work. Features earn their place as evidence once the Job is legible: Stripe's nine lines of code prove "accept payments today," TurboTax's W-2 import proves "file my return without errors," a SOC 2 report proves "pass security review without personal risk."
The funnel followed. A funnel can be beautifully optimized and still fail — a CTA bug and a wrong target segment both show up as "low conversion," and only one of them is a funnel problem. The clinic's funnel was short. The landing page had to make the one-day path thinkable for a person who has spent years dreading dentists, and answer the specific fears the interviews kept surfacing: the sedation itself, being upsold work they don't need, walking around mid-treatment without teeth. Then one low-cost next step — a single diagnostic visit that ends with a full plan and one price. That is chain design, not brochure layout.
Pricing stopped being a price list. A full one-day restoration costs what a used car costs; against a per-tooth price list it looks insane. But the chosen segment wasn't buying teeth one at a time — they were buying "close the dental question for good," and against years of piecemeal visits, repeated anesthesia, and standing dread, one large number looked fair. Willingness to pay attaches to the Job and its budget, not to the procedure. A price that looks expensive against the old Job can look cheap against the Big Job above it.
Unit economics are the financial expression of the same choice: budget per Job times frequency, minus the cost to acquire and serve. The one-day segment is one large check, low frequency, high margin, expensive leads — the economics of a surgical center. The one-aching-tooth segment is small checks, high frequency, thin margin, cheap leads — the economics of a corner store. Pick a different Job and the whole P&L changes shape. A spreadsheet cannot rescue a wrong Job. It can only make the wrongness precise.
Operations got the hardest homework. A one-day promise is an operational claim: the lab synced to the sedation date, the implant inventory confirmed before the patient is under, one coordinator who answers the phone, no mid-treatment surprises. For a segment that fears uncertainty more than pain, operations is where the promise is either kept or quietly broken. A different segment would demand a different operating system from the same clinic.
Even the roadmap derived from it. The clinic invested in whatever made the one-day promise more complete — in-house lab capacity, faster imaging, a second sedation team.
If the team does not choose the Core Job deliberately, something else chooses it. Then the artifacts start fighting each other: product builds for one customer, marketing speaks to another, sales discounts for a third, support absorbs a fourth, and finance asks why margin is leaking.
That was the dental clinic lesson in operational form. The clinic grew because the chosen Core Job explained what value to create, how to communicate, which fears to reduce, how to price, and what operations had to guarantee.
Once you have chosen an economically attractive segment and proved that customers buy the value, product work can become directed work across functions instead of coordination after the fact. Every function aims at the same target: one segment, one Core Job, one value hypothesis, one path the customer walks, one proof that the value is bought.
This is not free. Taste, execution, distribution, sales ability, operational discipline, and money still matter. The difference is that every function knows what it is extending: product performs the Core Job better; marketing communicates the value in the segment's language; growth attracts people from that segment while the Core Job is active; sales reduces fears and helps the customer switch; operations keeps the chain from breaking. The work becomes simpler because the functions stop pulling in different directions.
Wes Wants the Actual Lever
That answer is the usual one. The audit is uncomfortable because it exposes how much product work is already strategy by accident. The team that added SSO chose the enterprise buyer and the security-review chain that comes with them — usually without noticing. The team that added a premium plan chose a segment whose Job budget could carry the price.
None of this requires an org chart. A solo builder shipping a fourth product in a year is every department at once — and the departments still disagree. The landing page promises "your bookkeeping, done for you," the price assumes a hobbyist's budget, the onboarding shows off the AI instead of closing the books. Three artifacts, three implicit segments, one person. The same audit is how a team of one catches its own scatter before the launch does — and at that scale the answer sheet is brutal in its simplicity: the first ten paying customers.
When the focus is chosen, disciplines can move fast without hallucinating strategy. When it is not, speed is just a faster way to scatter.
The Error Has a Direction
If every artifact flows from the target segment's Core Jobs, the next question becomes harsher: when the upstream Core Job or segment is wrong, where exactly does the error travel?