Ignoring 'Switching Forces'
Type: warning
Stage: Stage 1: Problem Proof
Difficulty: advanced
You can validate a burning problem, but if the anxiety or habit forces are too strong, the user will never adopt your solution — no matter how well it works.
Overview
The Jobs-to-be-Done framework identifies four forces that determine whether a user switches from their current solution to a new one: Push (pain of the current state), Pull (attraction of the new solution), Anxiety (fear of the new), and Habit (comfort with the old). Most Stage 1 founders measure Push and Pull. They ignore Anxiety and Habit — and those are the forces that kill adoption.
The four forces
• Push: The degree of frustration, cost, or failure in the current solution. This is what most founders research in Stage 1 — and it's necessary but not sufficient.
• Pull: The perceived superiority of your solution. Founders spend most of their time here: features, positioning, demos.
• Anxiety: Fear of switching — will the new solution work? Will it be hard to learn? Will it break existing workflows? What if the vendor disappears?
• Habit: The comfort and familiarity of the existing approach. 'We've always done it this way' is not irrational — it's a learned risk management strategy.
A user will only switch when Push + Pull > Anxiety + Habit. Most products fail because they focus exclusively on Pull while Push, Anxiety, and Habit are invisible.
Switch Interviews: how to surface the forces
A Switch Interview is a structured conversation designed to find the exact moment a user decided they needed something new — and what they did next.
Core questions:
• 'Tell me about the first time you realized your current approach wasn't working for this.'
• 'What made you start looking for an alternative?'
• 'What stopped you from switching sooner?'
• 'When you tried [alternative], what made you hesitate?'
The answers to the first two questions reveal Push. The answers to the last two reveal Anxiety and Habit.
Run Switch Interviews with people who have recently switched from one solution to another — not just people who are currently using a solution. The switch moment is where the most revealing behavior lives.
Common Anxiety triggers
In B2B contexts, Anxiety forces are consistently underestimated. The most common:
• Data migration risk — 'What happens to our existing data?'
• Learning curve — 'How long until my team is productive?'
• Integration dependencies — 'Will this work with [our CRM / ERP / existing stack]?'
• Vendor risk — 'What if this company shuts down in 18 months?'
• Approval friction — 'Our IT team will never approve this.'
If your target user operates in a compliance-heavy, enterprise, or regulated environment, Anxiety forces can be strong enough to block adoption entirely — regardless of how good your solution is.
What to do about it in Stage 1
You can't eliminate Anxiety forces until you understand them. In Stage 1, the goal is diagnosis:
1. For every interview subject, ask at least two questions about what has stopped them from switching in the past
2. List every Anxiety force that appears across your interviews — these become your onboarding and trust-building requirements in later stages
3. Check whether your target user has switched tools in the past 18 months — frequent switchers have lower Anxiety thresholds; rare switchers have higher ones
4. If your solution requires behavior change (new workflow, new interface, new mental model), plan for the fact that Habit will resist it — regardless of how obvious the improvement is
A product roadmap that includes no onboarding investment, no data migration path, and no trust-building mechanism has ignored Switching Forces. That's a Stage 1 error you'll pay for in Stage 5.