Product Communication

This is the canon page on communication in AJTBD. It covers how delivered value becomes understandable before purchase, why copy is derived from Job research rather than invented, and how pre-purchase expectations shape the first Aha Moment. It expands AJTBD key theses §24. It sits on top of Segmentation, Value Creation, Consideration Activators, and Critical Chain of Jobs — the operational core, where the customer's walk from State A to State B lives.

1. Communication transmits validated value to a validated segment

Communication is the transmission of already-created value to a target segment. It does not turn an unvalidated Job, a weak segment, or an undelivered value hypothesis into fact. The operating sequence is strict. Choose the target segment, validate the Core Jobs and Big Jobs, create value against the segment's success criteria, prove the value through sales or usage, then scale communication. Before that point, landing pages, ads, and sales scripts are research artifacts or demand tests. They are not facts to scale.

The source material for communication is the AJTBD research record. A usable record names the target segment, the Core Jobs with success criteria, the Big Jobs above them, and the Micro Jobs before purchase and activation. It also names current Solutions and their Problems, Critical Chain of Jobs blockers, specific fears, Consideration Activators, and the Critical Chain of Jobs from trigger to first Aha Moment. If those fields exist, the team has the content for the landing page, ad creatives, sales script, lead magnet, demo, and buyer-enablement assets. If they do not exist, the copywriter is forced to invent.

Communication is therefore not a separate creative step. It is the packaging of segment-and-Job knowledge into the customer's language: we know your context and trigger; we perform these Core Jobs so these Big Jobs land; we do it more energy-efficiently by these criteria; this proof is why the claim is believable; these specific fears are handled; here is the first step.

Operational consequences:

• Do not scale communication before value is proven. If the product has not created a real Aha Moment for the target segment, better copy only accelerates disappointment.
• Do not write copy without the Job record. A page without Core Jobs, Big Jobs, success criteria, Critical Chain of Jobs blockers, specific fears, and current-Solution Problems is category prose, not AJTBD communication.
• Treat every message as a risky assumption. The customer must recognize themselves, understand the value, believe the proof, and reach the first Aha Moment without the chain breaking.

2. A purchase requires seven assumptions to hold along the Critical Chain of Jobs

A purchase happens only when seven assumptions hold along the customer's Critical Chain of Jobs from trigger to first Aha. Each assumption belongs to a different methodology object. When the sale fails, diagnose the failed assumption before rewriting copy.

Real blockers and fears are different objects. A real blocker is a fact that prevents the Critical Chain of Jobs from running: financing path, documents, logistics, compliance, payment method, data format, migration path. It is fixed by changing reality. A fear is the customer's prediction of a chain-break, an unmet promise, a Tax Job, a personal risk, or an irreversible loss: "this broker feels shady," "I won't pull off buying a car from another state," "this workflow will fail in front of my team." Once reality can hold the claim, communication names the fear and shows why it is prevented, absorbed, reversible, insured, or irrelevant for this Solution.

The seventh assumption is not marketing polish. A broken chain after the customer already decided to move creates disappointment against the whole Solution. The customer does not say "the CTA had a bug." They update the prediction to "this company may not perform the Big Jobs reliably" (see Critical Chain of Jobs §2).

3. Every message names the Core Jobs, the value, and the specific-fear work

The base message has three parts: which Core Jobs and Micro Jobs we perform, what value the customer will notice, and which specific fears are handled. In canonical form: for this target segment, we perform these Core Jobs and Micro Jobs so these Big Jobs land; we perform them more energy-efficiently by these concrete success criteria; if the customer fears a break, an unmet promise, a Tax Job, a personal risk, or an irreversible loss, here is why that fear is not active for this Solution.

Value must be stated in criteria, not adjectives. "Fast," "safe," "reliable," "high quality" are not value statements until they are translated into the segment's success criteria. DoorDash says dinner at the door in 35 minutes. TurboTax says federal and state return e-filed with error checks. Stripe says test payment accepted in minutes. BetterHelp says matched with a licensed therapist after the intake quiz. The criterion is where the brain can predict the gain.

Promises about Big Jobs must match the Core Jobs the product actually performs. Big Jobs carry motivation, so communication usually needs them. But promising outcomes from Big Jobs the product cannot fully land inflates the customer's prediction and manufactures disappointment during the first transition. A product that performs Core Jobs such as "compare apartments by commute and rent" can say it helps Big Jobs such as "move to Austin without losing evenings to apartment search." It cannot promise "move to Austin stress-free" unless it performs the full chain.

4. Features are proof, not the message

Feature-first communication sells the mechanism while the customer is trying to evaluate the Job. The customer does not arrive asking whether the product has workflow automation, AI matching, SSO, dashboards, alerts, or importers. They arrive with Core Jobs, Big Jobs, success criteria, fears, current-Solution Problems, and a limited prediction of whether this Solution will be worth the switch. A feature-first message forces them to translate your mechanism into their own Job Graph, and most customers will not do that work.

A feature becomes communicable only after it is attached to a Job and a criterion. TurboTax's W-2 auto-import helps "file my federal and state return correctly" with lower cognitive cost. Stripe Checkout helps "accept online payments" without custom checkout engineering. Face ID helps "unlock my phone" without typing. A SOC 2 report helps a B2B buyer "pass security review" without personal blame. The same feature with no Job-and-criterion attachment is inert proof.

Therefore lead with the Job, the value, and the fear reduction, and use features as evidence. If a feature appears in the headline before the Core Jobs, Big Jobs, and success criteria are legible, rewrite it. If the feature cannot be tied to a concrete criterion or specific fear, it is not ready for communication.

5. The one-liner compresses What + Core Jobs + value

The one-liner's function is to enter the customer's brain before attention collapses. Its formula is:

[What it is] + [Core Jobs the product performs] + [value by criteria]

Examples:

• Fandango — movie-ticketing app for finding showtimes and buying seats before you arrive.
• Wyzant — online tutoring marketplace for finding K-12 tutors by subject, availability, and budget.
• Miro — collaboration canvas for running workshops and mapping work with a remote team.
• Bench — bookkeeping service that categorizes transactions and delivers tax-ready financials for small businesses.

The one-liner is used everywhere: hero copy, sales openings, commercial proposals, outbound intros, app-store descriptions, conference booths, founder explanations, demo intros. It is not a slogan. It is the compressed sale of Core Jobs and value.

The sales test is simple. After the one-liner has been heard, ask the buyer to repeat what the product is, which main Core Jobs it performs for them, and what value it gives. If they cannot repeat it, the one-liner has not landed.

6. Creatives are Job-language formulas selected by evidence, not inspiration

Ad and hero copy are formulaic recombinations of the research record. The work is not to invent a clever sentence. It is to plug Core Jobs, Big Jobs, triggers, Micro Jobs, Problems, values, barriers, and State-B images into formulas, then test which formula the target segment responds to.

These formulas are not a closed set. Combine them when the Graph requires it: Trigger + Problem + Core Jobs, Big Jobs + fear reduction + CTA, Orientation Jobs + named product + first step. The constraint is not the template. The constraint is that every clause must translate back into named Job levels and criteria. If a line contains two infinitive verbs, parse the hierarchy before using it.

Visuals should show State B, not the production process. Show the result the Big Jobs or Core Jobs create. DoorDash shows dinner on the table, not route logistics. Zillow shows move-in readiness, not a listing database. Peloton shows the completed workout ritual, not the bike hardware. TurboTax shows the accepted return, not tax-code forms. Process details belong only when the process itself is the value proof.

LLMs are variant generators after the Job record exists. A model can generate 100 headline variants, 100 visual prompts, or 20 sales-script openings. It cannot decide which Core Jobs of which segment are worth competing for, or which criteria create value. Generate variants after research, then select them by demand tests and sales evidence.

7. Consideration Activators is the content layer under ads, landing pages, content, and sales

Communication loads Consideration Activators before the customer reaches the product. Ads, content marketing, sales scripts, demos, review pages, peer stories, and offline environments all carry the same five components (detailed canon in Consideration Activators):

1. The new Job Graph is visible — the customer sees which Core Jobs they would now perform for their Big Jobs.
2. The value delta is concrete — the customer sees how much better the Big Jobs and Core Jobs land by their success criteria.
3. A concrete named product performs that Job Graph, with an entry path — name plus first step.
4. Specific fears are reduced — a fear is the customer's prediction that the Big Job won't be performed well through our new graph (a break, an unmet promise, a Tax Job, a personal risk, or an irreversible loss along the way), shown as prevented, absorbed, reversible, insured, or irrelevant.
5. The competing Job Graph is fired — shown as concretely less energy-efficient by the Big Jobs' criteria.

Consideration Activators should load before the sales conversation when the Solution is unfamiliar. The customer should arrive already knowing that a different Graph exists, how large the value delta is, which named product runs it, what first step to take, which specific fears are handled, and why the old Graph is weaker. If the first salesperson or first landing page has to create the category from zero, the purchase path carries the full Consideration Activators cost at the most expensive moment.

Specific stories are the most compressed Consideration Activators format. A Belong story about a landlord who receives guaranteed rent while repairs are handled, a Wealthfront story about a founder whose portfolio auto-rebalanced after a liquidity event, a Stripe story about a marketplace that passed payments review without building payouts from scratch — each story carries Job Graph, value delta, named product, fear reduction, and competitor firing in one unit. Abstract "we save time" carries almost none of it.

8. A landing page is a short Critical Chain of Jobs, not a brochure

A landing page is a short Critical Chain of Jobs whose State B is enough belief and motivation to take the first step. The visitor arrives with a trigger, partial Consideration Activators, a prediction, fears, a current-Solution habit, and limited attention. The page must move them through recognition, value prediction, proof, specific-fear work, competitor firing, and a low-cost first Micro Job.

The canonical landing sequence follows the Consideration Activators and transition logic:

1. One-liner — what it is, Core Jobs, value.
2. Focus Jobs — the Core Jobs together with the Big Jobs they serve.
3. Context and trigger — the visitor recognizes "this is my situation."
4. Value by concrete criteria — how much more energy-efficiently the Core Jobs and Micro Jobs land.
5. How the Core Jobs are performed — features as the proof layer, not as the message.
6. Current-Solution Problems — why the existing Job Graph produces Problems, Tax Jobs, risks, or chain-breaks.
7. Specific-fear reduction — feared breaks, unmet promises, Tax Jobs, personal risks, or irreversible losses handled.
8. State B / Big Jobs reminder — what the higher-level results look and feel like.
9. Consideration Activators and CTA — named product, first step, low activation cost.

The sequence is a diagnostic, not a decoration rule. If the page has motivated traffic but does not move people to the next step, ask which transition step failed. The visitor did not recognize the context. The value was not concrete. The proof did not connect to the criterion. A real blocker remained in the Critical Chain of Jobs. A specific fear stayed active. The competing Solution was not fired. Or the CTA required too much cost before the first Aha Moment.

9. Communication sets the customer's prediction before the product can beat it

Pre-purchase communication shapes the prediction the product must beat. Brand, ads, peer stories, screenshots, pricing, reviews, sales promises, and the landing page all enter the customer's predicted value calculation before first use. The first Aha Moment is then measured against that prediction (see Value Creation §4–§6 and Scientific Foundations §3, §4, §11 — common currency, purchase decisions, reward prediction error).

Expectation management is therefore a value lever. Overstated communication creates an expectation the product cannot exceed. Reality lands below prediction, and the customer experiences disappointment even when the product performs the Core Jobs objectively well. Under-specified communication can also fail, because the customer never predicts enough value to enter the transition. The target is an honest prediction that the product can beat early.

Operational consequences:

• Never promise Big Jobs the product only partially performs. Promise the Core Jobs honestly and show the Big Jobs they contribute to.
• Place the first Aha Moment as far left as possible. The longer the chain before value is noticed, the more time habit, fear, interruption, and competitor Consideration Activators have to pull the customer away.
• Use proof to tune prediction, not to decorate. Social proof, guarantees, demos, customer logos, and cases should answer the exact prediction the customer is forming: will this Graph run for someone like me, at my criteria, without breaking?

Cross-references

• AJTBD key theses §24 — short form: communication through Jobs, landing-page blocks, creative formulas.
• Segmentation — target segment, causal segmentation criteria, and proxy audiences.
• Value Creation — value as energy efficiency (outcome/cost), predict-and-compare driving behaviour change, Aha Moment, expectation management.
• Consideration Activators — the five Consideration Activators components, channels, and category-creation mechanics.
• Critical Chain of Jobs — the operational core: chain structure (breaks, hand-offs, cycles, time-gaps), chain execution (predictions, interruptions, drop-offs, Solution switches, per-step emotions, knows-how vs first-time), and Previous Job / Next Job strategy.
• Behaviour Change — behavior-change forces, trigger timing, and the familiar vs. unfamiliar Core Jobs distinction.
• Job Structure — eight elements of a Job, success criteria, triggers, emotions, and the Big/Core/Small/Micro hierarchy.