This is the canon page on Barrier Removal in AJTBD: the work of making a new Job Graph executable in reality for a specific segment. It connects Value Creation, Critical Chain of Jobs, Consideration Activators, Communication, and Behaviour Change.
1. A Barrier is a fact that makes the new Job Graph non-executable for a segment
A Barrier is an objective condition that prevents the customer from performing the new Job Graph or Critical Chain of Jobs. The condition can live before the chain starts, inside a chain node, at a hand-off, or inside a cycle. It can also live at the point where the chain has to prove the Big Jobs landed. If a missing prerequisite sits before the first visible action, treat it as node zero of the chain.
The customer usually knows the Barrier exists. They use it as the reason not to enter the new Job Graph with our Solution. Fears are predictions about a break that may or may not happen. Consideration Activators gaps are things the customer doesn't know to look for. A Barrier is different: it is a fact the customer can name the moment we ask — "my state isn't supported," "you don't have SSO yet," "you don't deliver to my ZIP code," "the import failed on my data." The customer hits the fact, recognizes it as a blocker, and routes around our Solution. Most of them do this silently, without ever telling us.
Every Barrier maps to a broken, impossible, too-costly, or too-risky Job. TurboTax without K-1 support blocks "file my federal and state return correctly" for LLC owners. DoorDash outside a ZIP code blocks "receive dinner at my address." A B2B SaaS without SAML blocks "pass IT security review."
A Barrier is segment-specific. The same product can be executable for one segment and blocked for another. Stripe's API worked for YC-stage startups with engineers, but local merchants needed no-code checkout. Zoom worked for corporate meetings, but K-12 schools needed FERPA, waiting rooms, locked meetings, and classroom controls. The product did not become bad. The segment's Critical Chain of Jobs changed.
2. Barrier Removal creates the possibility to switch Job Graphs
Value Creation creates the reason to switch Job Graphs. Barrier Removal creates the possibility. The customer does not merely switch a vendor label. They stop performing the old Core Jobs, Small Jobs, and Micro Jobs in one graph. They begin performing a new graph with our Core Jobs inside their Big Jobs. The Solution label changes because the graph changed.
Barrier Removal is the work of changing reality so the new Job Graph can be performed — not persuasion. It changes prerequisites, hand-offs, integrations, permissions, payment paths, logistics, legal paths, data formats, geography, role coverage, and broken chain links. If a migration path does not exist, a testimonial is not the fix. If a state is unsupported, a guarantee is not the fix. Communication can reduce a fear only after the feared break is no longer true.
Examples: Stripe Checkout made "charge customers online" executable for non-engineering merchants. Notion Enterprise made "adopt Notion org-wide" executable inside IT and security review. Belong made "rent out my duplex" executable for out-of-state owners. TurboTax K-1 support made "file my return correctly" executable for LLC owners.
3. Fears are predictions about Barriers, Problems, Tax Jobs, personal risks, or losses
A fear is not a Barrier. It is the customer's prediction that a Barrier, Problem, Tax Job, personal risk, or irreversible loss will happen. The customer may fear the Solution, the Core Jobs, the Big Jobs, a role hand-off, a downstream consequence, or their own ability to recover if something goes wrong.
When the fear is accurate, it is not a communication problem. If the customer says "IT will block this because there is no SSO" and there is no SSO, the team has found a Barrier. If the customer says "I won't be able to migrate my data" and no migration path exists, the team has found a Barrier. Calling it a fear produces false reassurance where reality work is required.
When the fear is inaccurate or no longer true, it becomes Consideration Activators work. The message names the concrete feared break and shows why it is prevented, absorbed, reversible, insured, or irrelevant for this Solution. Airbnb's AirCover reduces "the host will cancel and I'll be stranded." CarMax returns reduce "I'll be stuck with a lemon." DocuSign audit trails reduce "this signature won't hold up."
4. Barrier Removal comes before truthful fear reduction
The sequence is reality first, Consideration Activators second. Barrier Removal makes the claim true. Consideration Activators makes the truth usable in the customer's head. Reversing the order creates over-promise: the customer enters a chain that still breaks and registers a Problem against the whole Solution.
The conversion diagnostic is strict. If the chain cannot run, fix the Barrier. If the chain can run but the customer predicts a break, reduce the fear. If the chain ran and still delivered below prediction, improve value or repair the chain break that produced the Problem. These are different failures with different fixes.
Concrete Consideration-Activators-loading acts that reduce specific fears — live import previews, $1 test payments, ZIP and state support checks, same-segment case studies that name the feared break — are unpacked in Consideration Activators.
5. Barriers cluster into six recurring classes
- Missing prerequisite. The customer lacks a required document, license, role approval, payment method, device, data format, budget path, physical access, or legal permission. IRS identity PIN, driver's license, ACH authorization, healthcare data agreement, landlord access, vendor approval.
- Unsupported context. The product works generally but not in this state, ZIP code, country, school district, enterprise role, data environment, compliance regime, or physical setting. DoorDash coverage, state tax support, K-12 FERPA, Epic write-back, local repair network.
- Broken chain link. A necessary Job fails in reality: form validation loops, payment declines, app unlock fails, import loses data, checkout crashes, calendar link is dead, delivery hand-off misses the buzzer.
- Hand-off failure. Work passes between roles, vendors, systems, or institutions and loses ownership, context, or timing. Champion to IT; marketplace to seller; CRM to billing; doctor to lab to patient.
- Cycle or return-for-rework. The customer reaches a step, gets sent back, and pays the same Job again as a Tax Job: mortgage document cycles, prior-authorization denials, insurance-claim resubmissions, tax-prep missing-form loops.
- Irreversible-loss exposure. The chain may technically run, but the downside is too hard to recover from for this segment: losing money, missing a deadline, looking incompetent, damaging a customer relationship, being stranded, being unable to undo the purchase. Returns, insurance, guarantees, escrow, backups, audit trails, and human support can remove the exposure.
6. Barrier Removal mechanics are a non-exhaustive operator set on blocked Jobs
The list below is not a closed taxonomy of every possible Barrier Removal move. It is a compact operator set for asking what happened to the blocked Job. Did we repair it, delete it, take it off the customer, route it elsewhere, change the entry path, or make the downside reversible? New mechanics can be added when practice finds them. The test is whether the move changes reality so the new Job Graph becomes executable for the segment.
- Repair the broken Job in place. Fix the form, support the payment method, add K-1 handling, build SAML, support the data schema, make app unlock reliable.
- Kill the Job. Face ID killed "type my password." AirPods killed "untangle my headphones." One-click checkout killed repeated address entry. The Barrier disappears because the Job disappears.
- Take the Job off the customer. Belong takes showings, repairs, leasing, and rent collection off the out-of-state landlord. Wealthfront takes rebalancing off the investor. Bench takes tax filing off the small-business owner.
- Route the Job to a reliable partner. A real-estate agent routes mortgage, inspection, title, and moving Jobs to trusted vendors. Salesforce AppExchange routes adjacent revenue-stack Jobs to partner products. Apple's App Store routes thousands of phone Jobs to third-party apps.
- Change the entry path. Stripe Checkout gave merchants a no-code door instead of an API key. TurboTax interview flow gives non-experts questions instead of tax forms. BetterHelp's intake quiz performs earlier Orientation Jobs before therapist choice.
- Make loss reversible or absorbed. CarMax and Carvana reduce used-car downside with return windows. Airbnb reduces travel downside with AirCover. Costco reduces purchase regret with returns. B2B vendors reduce career risk with pilots, rollback paths, SLAs, and named support.
7. Barrier Removal is researched through motivated customers who hit the Barrier — mid-chain or before entering
The first source is motivated customers who tried and could not complete the chain. Existing customers already passed the hidden blocker, and non-motivated prospects are noise. The signal is the customer who wanted the Big Jobs, accepted the value, entered the transition, and got stuck.
The second source is motivated customers who saw the Barrier up front and chose not to try. This pool is invisible to standard funnel analytics, because they never entered. Find them by recruiting on motivation (right Big Jobs, right segment) without filtering on whether they used the product. Interview question: "Was there anything you saw or heard about {studied Solution} that made you not even try it?" The pre-entry opt-out cohort is harder to source than the failed-attempt cohort. It surfaces the largest single class of Barrier: the one the customer can name before walking the chain.
The research object is the exact Job where the chain became non-executable. Not "they didn't convert," but "payment method failed." Not "enterprise didn't buy," but "security review blocked because user-provisioning integration was missing." Not "landlords don't trust us," but "out-of-state access, repairs, and lease handoff had no runnable path."
Interview question: "Was there anything that stopped you from starting to use {studied Solution} to perform these Core Jobs?" Follow with: "What exactly stopped you? At which step? What had to be true for you to continue? Did you solve it another way?"
The output is a Barrier backlog. Each item names the segment, Big Jobs, Core Jobs, Critical Chain of Jobs node, real blocker, evidence that it blocks execution, and mechanic selected to remove it. Fear-reduction copy is downstream of this backlog, not a substitute for it.
Cross-references
- Value Creation — value as energy efficiency (outcome over cost), value mechanics, the Aha Moment and Problem as drivers of behaviour change.
- Critical Chain of Jobs — chain-breaks, Tax Jobs, preemptive avoidance, and mechanics for fixing broken chains.
- Consideration Activators — Consideration Activators components and why real blockers are not Consideration Activators.
- Communication — how Barrier reality and fear-reduction claims show up in messages, landing pages, and sales.
- Behaviour Change — forces that drive and block behavior change.