Pull Forces: Making Your Product Magnetic Without Overpromising

Pull is the Jobs-to-be-Done force describing how attractive a new solution feels once someone pictures living with it — the imagined better life, not a feature list. It only works when it stays credible: oversell it and you manufacture the expectation-driven anxiety that kills the switch instead of causing it.

Pull is the pictured upside of switching — how much better life looks after adopting your product — and it's one of four forces, alongside push, anxiety, and habit, that decide whether someone actually changes behavior. Calibrate it to match real, specific progress; inflate it and you trade attraction for suspicion.

What Pull Actually Is in the Forces of Progress Model

Pull is the magnetism of an imagined future — what Clayton Christensen, Bob Moesta, and Chris Spiek named as one of four Forces of Progress that decide whether someone actually switches products. It's the force pulling a person toward the new thing, as opposed to the push that shoves them away from the old one.

The four-forces model, laid out in Christensen's Competing Against Luck and refined through Moesta and Spiek's demand-side sales research, treats switching behavior as a tug-of-war rather than a funnel. Christensen frames it against a stark backdrop: he cites the large majority of new products failing despite record R&D spend, and traces most of that failure back to teams who understood their own product better than the progress a customer was actually trying to make.

Two forces move someone toward change; two hold them in place. Pull is the only one of the four that's purely aspirational — it lives entirely in the prospect's imagination of "after," which is exactly why it's so easy to inflate and so damaging when it's wrong.

Notice that pull and anxiety are opposites answering related questions — one imagines gain, the other imagines loss. That relationship is the whole point of this article: the same claim that builds pull, pushed too far, is what feeds anxiety. For the full background on the model these forces sit inside, see this complete guide to Jobs-to-be-Done.

Pull Is About the Outcome, Not the Object

Theodore Levitt's 1960 Harvard Business Review essay "Marketing Myopia" made the case that companies fail when they define themselves by the product they sell instead of the customer outcome the product produces — a railroad thinking it's in the railroad business instead of the transportation business. Pull is where that distinction becomes concrete: it's never the feature list that pulls someone forward, it's the outcome they picture the feature list producing.

That's why a pull statement built around specs — more integrations, a faster API, a new dashboard — rarely moves anyone. A pull statement built around what the specs let a person finally stop worrying about is a different animal entirely. The imagined life, not the shipped capability, is what does the pulling.

Why Teams Inflate Pull — and the Anxiety It Actually Creates

Teams inflate pull because vague, aspirational language is easier to write than concrete proof, and ambitious claims feel more visionary in a pitch deck. But when the pictured future outruns what the product can credibly deliver, prospects don't experience extra desire — they experience risk, which is the anxiety force doing its job.

This isn't just a hunch about tone. Expectation-disconfirmation theory, the marketing model Richard Oliver formalized in 1980 and that still underpins most customer-satisfaction research, says satisfaction is a function of the gap between what someone expected and what they actually experienced. A bigger promise doesn't just raise the ceiling — it widens the gap available to disappoint, even when the underlying product is genuinely good.

Geoffrey Moore made a related point in Crossing the Chasm: early adopters will forgive a rough, visionary pitch, but the pragmatist majority — a group Everett Rogers' diffusion-of-innovation research puts at roughly two-thirds of any market — wants evidence, references, and a whole product before they'll act on pull alone. Fog plays well to a room of believers and terribly to everyone else.

Three tells that a pull claim has drifted into fog:

1. It has no unit. "Faster," "smarter," and "seamless" describe a direction, not an amount.
2. It has no comparison point. Better than what, exactly — the spreadsheet, the old tool, last quarter?
3. It can't be falsified. If no plausible piece of evidence could ever contradict the claim, prospects' instincts read it as marketing, not information.

Each of those gaps is a place anxiety moves in to fill the vacuum pull left behind.

The Pitch-Deck Incentive

Fog is also, frankly, an organizational habit of its own. A roadmap slide that says "cut close time" invites a hard follow-up question from a skeptical VP: cut it by how much, based on what evidence? A roadmap slide that says "reimagine the close" invites applause instead. Teams under pressure to look ambitious reach for the applause line, and it quietly migrates from the internal deck into the external positioning without anyone deciding it should.

The fix isn't lowering ambition — it's separating the aspiration a team holds internally from the claim it makes externally. Internally, "reimagine the close" can be a rallying cry. Externally, in front of a prospect who has to bet their own credibility on the switch, only the falsifiable version of that ambition should show up.

Aspirational Fog vs. Specific Progress: The "Close the Month in Two Days" Test

Aspirational fog promises transformation without naming a unit of progress — "work smarter," "unlock your team's potential." Specific progress names a task, a comparison point, and a plausible number: "close the month in two days instead of eleven." It creates real pull because it's falsifiable, and prospects can only picture what's falsifiable.

Chip and Dan Heath's concreteness principle from Made to Stick explains why this works at a cognitive level: abstract claims are forgettable and unverifiable, while concrete claims recruit sensory, checkable detail that the brain can actually hold onto and test against reality. "Close the month in two days" is concrete. "Transform your finance operations" is not.

The pattern across every "specific progress" row is the same: a real moment, a real number, a real comparison. None of them require hype — they require the team to actually know the job well enough to name what changes.

A Quick Test Before You Publish the Claim

Before a pull statement goes on a homepage, in a sales deck, or into onboarding copy, run it through a short gut check:

• Can a prospect picture the exact moment this happens to them — a specific day, meeting, or task?
• Is there a number or comparison in the sentence, even an approximate one?
• Could a skeptical buyer ask "compared to what?" and get a real answer back?
• Would the claim still be true, directionally, for a below-average customer — not just the best case?

If any answer is no, the claim is still fog, no matter how confident it sounds.

Where Pull Shows Up Along the Journey — and Why Habit Fights Back

Pull isn't a one-time pitch; it recurs at every moment a prospect mentally compares "life now" to "life after" — during discovery, during the internal champion's pitch to their boss, during onboarding, and during the first real test under pressure. Positioning has to survive each of those moments, not just the landing page headline.

Mapping where pull spikes and where it sags is exactly what a complete guide to the customer journey is built to surface: the emotional highs where pull is doing real work, and the dips — often mid-onboarding — where anxiety or habit temporarily wins the tug-of-war. A positioning claim that only holds up on the homepage isn't pull; it's marketing that hasn't met the job yet.

Habit is the quieter opponent, and it's rarely a single stubborn person — it's usually a self-reinforcing loop. The spreadsheet process survives because the controller trusts it, trusting it means nobody questions it, and nobody questioning it reinforces the trust further.

Seeing that loop clearly, rather than treating habit as one person's resistance, is a systems-thinking exercise. The reinforcing and balancing loops involved are exactly what a systems thinking overview helps a team trace before it tries to out-pull a habit loop with a slogan.

That matters for pull specifically because an inflated claim often gets deployed as a shortcut past habit — "it'll be so much better that nobody will miss the old way." Real habit loops don't dissolve because a promise is big; they dissolve when the new path is demonstrably less effortful at the specific moment habit usually wins, like the first time a controller has to close a month without their familiar checklist.

Turning Pull Into a Job Statement You Can Actually Ship

The discipline that keeps pull honest is writing it into a real job statement — a structured sentence with a subject, a struggling moment, and a measurable direction of progress — rather than a slogan a designer drops into a hero banner. A slogan can say anything. A job statement has to be specific enough to build against.

Following a real JTBD job statement format forces the pull claim to answer three questions before it ships:

• Who is pulled — which role, in which situation, is imagining this better life?
• What progress are they picturing — closing the books, not "being more efficient"?
• What evidence would prove it happened — two days instead of eleven, not "faster"?

That discipline matters past the positioning page, too. A pull claim that survives a pitch deck often collapses the moment it reaches engineering, because "make closing faster" isn't buildable and "seamless experience" isn't testable. Writing the claim so it can survive the handoff to engineering is the same exercise as writing it so it can survive a skeptical prospect — both audiences need a concrete, falsifiable unit of progress, not a mood.

It also helps to know which pull claims are worth making in the first place. Not every underserved outcome deserves a headline promise — some are already well satisfied by existing tools, and the pull would be manufactured rather than genuine. Running candidate outcomes through the opportunity score formula — importance minus satisfaction, per Anthony Ulwick's outcome-driven innovation method — is how a team finds which "better life" claims are actually underserved enough to be worth building a positioning statement around.

Reading Pull as Its Own Signal, Not a Vibe

The tool walks you through naming push, pull, anxiety, and habit for a specific job statement, the same structure Christensen, Moesta, and Spiek described, layered onto the JTBD and Ulwick opportunity scoring work already in the workspace. It won't tell you your positioning is right — no tool can — but it's designed to stop a team from confusing "we wrote something inspiring" with "we identified genuine, evidenced attraction," which is the exact confusion this whole article has been warning against.

Key Takeaways

• Pull is the imagined better life, not a feature list — it's one of four Forces of Progress (push, pull, anxiety, habit) that together predict whether someone actually switches.
• Inflated pull doesn't create more attraction — it creates more anxiety, because a bigger promise widens the gap between expectation and experience that expectation-disconfirmation theory says drives dissatisfaction.
• Concrete, falsifiable claims beat aspirational fog. "Close the month in two days instead of eleven" creates pull; "transform your operations" does not.
• Pull has to survive the whole journey, not just the landing page — map where it spikes and sags rather than assuming one strong pitch carries a prospect all the way through.
• Habit is usually a reinforcing loop, not a single stubborn holdout — systems thinking helps a team see the loop it's actually competing against.
• Write pull into a proper job statement — subject, struggling moment, measurable progress — so it survives both a skeptical prospect and an engineering handoff.
• Not every underserved outcome deserves a bold promise. Score the opportunity first, then decide what's worth saying out loud.