Switch Formula From Data, Not From Assumptions
Switch Formula is one of the most powerful tools in Jobs-to-be-Done. It describes the critical moment when someone abandons one solution and picks up another. Get this moment right, and you understand how to build the product, how to market it, and who to target.
Most teams build their Switch Formula from assumptions. “The customer switches when the pain gets unbearable” — that’s not a formula, it’s a guess.
The Four Forces
Switching happens according to one equation:
Push + Pull > Anxiety + Habit
Push — forces driving the customer away from the current solution. Dissatisfaction, a triggering incident, a context shift.
Pull — the attractiveness of the new solution. A promise of improvement, specific capabilities, a compelling narrative.
Anxiety — fear of switching. Risk of failure, loss of control, the learning curve.
Habit — inertia of the current solution. Familiarity, deep integration with existing workflows, team resistance.
Two Classic Mistakes
Mistake 1: Projection. Teams project their own motivations onto customers. In practice the primary push might be something completely different — say, a new manager with different reporting requirements. You’d never guess this without data.
Mistake 2: Overestimating Pull. Teams overvalue their own key features while underestimating organizational barriers and training requirements. The feature is great. The switching cost is invisible until it isn’t.
Extracting Each Force From the Knowledge Graph
Push From the Graph
Push comes from nodes typed as pain, constraint, trigger. The graph tracks which pains appear most often and what weight they carry — confidence × frequency. You’re not ranking pains by feeling, you’re ranking them by evidence.
Pull From the Graph
Pull comes from solution, feature, metric nodes. The critical difference: Pull here is based on what the customer actually wants, not what the team assumes they want.
Anxiety From the Graph
Anxiety is the most commonly skipped force — and it can outweigh everything else. In the graph it surfaces as organizational and psychological barriers. If these aren’t showing up in your interviews, you’re not asking the right questions.
Habit From the Graph
Inertia is measured through current solution usage data and the degree of organizational integration. The question isn’t “do they like the current tool” — it’s “how deeply embedded is it.”
Switch Formula as an Artifact
In AICPO, Switch Formula is one of 46 auto-generated artifacts. The structure:
- Push: pains with confidence scores + switching triggers
- Pull: desired outcomes with direct quotes from conversations
- Anxiety: organizational, psychological, and technical barriers
- Habit: current solution, duration of use, integration depth
Every element is backed by evidence from real conversations. Not vibes — sources.
What to Do With It
For marketing: decide whether to lead with Push (show you understand their pain) or Pull (paint the desired outcome). These are different campaigns targeting different psychological states.
For onboarding: the strongest anxiety should be addressed in the first minutes of product use. Not in the FAQ. In the product.
For strategy: if Habit is too high and Pull is insufficient, that’s a signal to pivot toward a different segment with lower switching resistance.
It Updates Automatically
Knowledge Graph v2 uses bi-temporal storage — every node has temporal validity. Switch Formula automatically refreshes when context or competitive landscape changes. The formula isn’t a one-time artifact, it’s a living document.