Guide

Product thinking and discovery

Forces of progress

Push and pull move people toward a new product. Anxiety and habit hold them. Great products fail when the last two win.

13 of 128 · 2 min read

Big push plus big pull still loses if anxiety and habit are larger. That is why great products fail to convert: onboarding is scary, data import is painful, switching cost is social ("our team knows the old tool").

Product work is not only increasing pull (more features). It is often reducing anxiety (guarantees, sandboxes, migration helpers) and interrupting habit (triggers, defaults, training).

Concept

Bob Moesta and the JTBD community describe four forces: push of the current situation, pull of the new idea, anxiety about the new, and habit of the present. The switch happens when toward > against.

The big idea

  • Push — pain, frustration, the workaround breaking.
  • Pull — hope, demos, peer stories, clear gains.
  • Anxiety — migration fear, learning cost, "what if it fails mid-quarter?"
  • Habit — muscle memory, sunk integrations, "good enough."

A moving company can sell a bigger house (pull) and a leaking roof (push) and still lose to "we know this street" (habit) and "what if the kids hate the school" (anxiety). Software is the same. The analogy breaks when the "move" is free and reversible — then anxiety should be cheap to kill, and if you haven't, that is a product bug.

Trade-off

Adding features increases pull but can raise anxiety ("this looks complex"). For switchers, invest in anxiety-killers: import tools, side-by-side mode, undo, human onboarding for high ACV. For new categories (non-consumption), push may be weak — you must create pull with a vivid job story, not a feature matrix.

Walking through a switch that stalls

A freelancer loves your invoice demo (pull) and hates chasing payment over email (push). They do not switch because import looks risky (anxiety) and their color-coded sheet already works (habit). A new PDF theme will not close this. An import, a side-by-side week, and a one-click pause-until-paid rule might.

In design review, ask which force you are changing — more pull, less anxiety, more push awareness. In postmortems of failed features, ask whether you optimized the wrong job or lost to habit and anxiety you never measured.

Common mistakes

  • Feature matrices as the only lever. More pull can raise anxiety.
  • Ignoring habit. Muscle memory and integrations are competitors.
  • No anxiety-killers on a migration. Sandboxes and imports are the product.

Check yourself

Users praise the demo and stay on spreadsheets. Which forces are winning?

Anxiety and habit. Add import, undo and a side-by-side path — not more features.

When is a feature matrix the wrong sales tool?

Non-consumption. People who hire nothing need a vivid job story, not checkbox parity.

Key takeaways

  • Switch = push + pull versus anxiety + habit.
  • Reduce anxiety as deliberately as you add features.
  • More pull can raise anxiety. For non-consumption, create pull with the job, not a matrix.

Further learning

Next, hear the forces in switch interviews.

Jobs to be done

What customers hire a product to do — and how JTBD reframes competition and features.

What is a job to be done

People hire a product to make progress in a circumstance — not to buy a feature list or a demographic label.

Switch interviews

Reconstruct the last time someone hired or fired a product. Past timelines beat hypothetical "would you switch?"