Switching requires a force advantage. Bob Moesta and Chris Spiek's Progress Theory links adoption to problem pressure and solution appeal overcoming uncertainty and habit. Use the force balance to pinpoint conversion friction and design lower-friction customer migration.
Based on: Progress Theory (Bob Moesta)
Progress Force Mapping (The Four Forces of Customer Progress) is a breakthrough behavioral economics framework formulated by Bob Moesta and Chris Spiek within Clayton Christensen’s foundational Jobs to be Done (JTBD) architecture. Why do enterprise buyers and consumers stubbornly refuse to adopt a new solution even when it is demonstrably faster, cheaper, and superior? Conventional product managers assume adoption is a linear function of marketing volume and feature density (amplifying the “Pull”). Moesta proved that buying behavior is governed by a dynamic force field: customers do not purchase products; they “hire” solutions to make progress in a specific life or operational context. A customer switch occurs if and only if the forces generating momentum exceed the opposing forces of inertia.
The framework models consumer adoption across four adversarial vectors:
1. The Accelerating Vectors (Propelling Progress):
2. The Drag Vectors (Suppressing Progress):
3. The Progress Threshold Equation:
( ext{Adoption Probability} iff ( ext{Push} + ext{Pull}) > ( ext{Anxiety} + ext{Habit}))
If the drag vectors dominate, conversion velocity drops to exactly zero, regardless of ad spend.
Corporate enterprises disproportionately allocate 95% of capital to amplifying Pull (building features and spending on ad campaigns) while allocating 0% to extinguishing Anxiety and Habit. The Brainstorm Reactor calculates the true force vector:
Engineered for customer acquisition, churn diagnostics, and product switching dynamics. Inappropriate for purely internal computational geometry, server optimization, or cryptographic audits.
High-leverage deployment in SaaS conversion rate optimization, enterprise B2B sales playbook engineering, product-market fit discovery, and customer migration architecture.
Trace causes beyond symptoms. Sakichi Toyoda’s method in the Toyota Production System uses a five-tier causal recursion to isolate systemic or procedural root causes. Use the finding to target corrective action.
Not the first account determines the result, but systematic examination of who, what, where, when, why, how, and with what means. Rooted in classical rhetoric and refined through Lasswell’s communications model, it yields complete project charters, incident reconstructions, and launch plans with fewer factual omissions.
Not predefined categories, but bottom-up semantic resonance determines how observations are grouped. This foundational method in human-centred design and qualitative content analysis limits deductive bias, helping teams synthesise customer interviews, employee surveys and feature requests into coherent product and organisational themes.
Intuition is no substitute for analysis; its leverage lies in preconscious threat signals that test board decks and financial models for concealed risk. Because limbic pattern recognition can register discrepancies before cortical articulation, Brainstorm Reactor converts them into a final check for capital, safety, and ethics.
Select this method, describe your challenge, and let the structured AI pipeline do the rest.
Open Now