Strategy as a Gravity Well

The most expensive meeting in any organization is the one where a team presents a genuinely better approach and the room decides to stay the course. Not because the alternative is wrong. Because the existing commitment has accumulated too much mass — capital deployed, teams hired, vendor contracts signed, reputations staked — and that mass bends every adjacent decision toward itself. The room is not choosing. It is orbiting.

I call this the Strategic Gravity Well. Every significant commitment a company makes begins accumulating mass the moment resources flow into it. Past a critical threshold, that mass warps the decision space around it. New initiatives get evaluated not on their own merits but on their proximity to the existing well. Hiring skews toward skills that reinforce the current trajectory. Budgets flow downhill toward the center of gravity. The well does not need advocates. Physics handles advocacy.

How Wells Form

A gravity well starts as a bet. A company commits to a cloud migration, an ERP deployment, a data platform strategy. In the first quarter, the commitment is lightweight — a team of 4, a pilot budget, a slide deck. Escape is trivial. Most organizations could walk away with minimal loss.

Then mass accumulates. By month 6, 20 engineers are building on the platform. By month 12, three downstream teams depend on it. By month 18, the VP who championed it has tied their promotion case to its success. By month 24, the vendor contract has a 3-year lock-in with $2M in early termination penalties. Each increment is rational in isolation. The compounding is where the physics changes.

Every strategic commitment has an inflection point where the cost of continuing becomes lower than the cost of escaping — regardless of whether continuing is the right decision. Past this point, the organization is no longer choosing the strategy. The strategy is choosing the organization.

This is distinct from sunk cost fallacy, though it looks similar from the outside. Sunk cost is a cognitive bias — an irrational weighting of past expenditure. Gravity wells are structural. Even a perfectly rational actor facing $2M in termination penalties, 20 engineers who would need retraining, and a VP whose career is entangled with the outcome would calculate that staying the course is cheaper than escaping. The trap is not irrational. It is mechanical.

The Three Properties of a Gravity Well

Every strategic gravity well has three measurable properties. Mapping them is the first step toward regaining decision autonomy.

Mass is the total resource commitment: capital deployed, headcount allocated, contractual obligations, and — critically — reputational investment. A CTO who has publicly evangelized a platform at three conferences has added reputational mass that does not appear on any balance sheet but exerts real gravitational pull. In my experience, reputational mass often exceeds financial mass in its distortion effects. A $5M investment that nobody's career depends on is easier to exit than a $500K initiative championed by a board member.

Pull radius measures how many adjacent decisions the well distorts. A narrow well — say, the choice of a specific monitoring tool — affects only the observability team's workflow. A wide well — the decision to build on AWS vs. Azure — pulls hiring, training, architecture, vendor negotiations, and partnership strategy into its orbit. The pull radius of a cloud commitment typically extends to 40-60% of an engineering organization's decisions within 18 months of adoption, based on what I have seen across deployments.

Escape velocity is the force required to break free. This is not just the financial cost of switching. It includes the coordination cost of realigning 20 teams, the political cost of declaring a previous strategy wrong, the opportunity cost of the 6-18 months spent migrating, and the institutional trauma of admitting that the organization's gravitational center was in the wrong place. Most organizations never calculate escape velocity explicitly. They feel its pull and rationalize compliance as alignment.

Why AI Adoption Fails in Existing Wells

The most common AI adoption pattern I encounter is grafting. An organization with an existing gravity well — typically centered on a data platform, a cloud migration, or an ERP system — attempts to "add AI" to the existing initiative. The AI workstream gets pulled into the well's orbit immediately. It inherits the well's governance structure, its vendor constraints, its architectural assumptions, and its success metrics.

The result is predictable. The AI initiative optimizes for compatibility with the existing well rather than for its own potential. The team selects models that integrate with the current stack rather than models that best serve the use case. The deployment timeline aligns with the platform's roadmap rather than the market window. The success metrics become "AI features shipped on the platform" rather than "business outcomes achieved through AI". The well absorbs the initiative. Within 12 months, "AI adoption" has become a line item in the platform budget, indistinguishable from any other feature request.

AI initiatives grafted onto existing strategic gravity wells inherit the well's constraints, timelines, and success metrics. The initiative optimizes for compatibility with the well rather than for its own trajectory — and the organization calls this "strategic alignment".

The alternative is what I call orbital independence — launching the AI initiative with its own gravity well, separate budget authority, distinct success metrics, and a team that does not report through the existing well's chain of command. Amazon's approach with AWS — initially a separate entity with its own P&L — is the canonical example of creating a new gravity well rather than grafting onto the retail operation's existing one. The new well must accumulate enough mass to sustain itself before the parent well's pull recaptures it.

The Gravity Well Audit

The practical application of this framework is a gravity well audit — a structured exercise for mapping an organization's strategic wells and making conscious choices about each one.

Action	Use When	Risk And Example
Orbit — continue operating within the well's pull	Well is productive and aligned with market direction	Risk: complacency; the well may drift as the market shifts. Example: staying on AWS when cloud-native is your competitive advantage.
Escape — invest the force needed to break free	Well is decaying or the market has shifted away from its center	Risk: massive coordination cost; 6-18 month productivity dip. Example: migrating off a legacy ERP when it blocks real-time data access.
Create — launch a new well with independent mass	New capability requires trajectory incompatible with existing wells	Risk: resource split; confusion about "which strategy". Example: standing up an AI team with its own budget and reporting line.

The audit itself is straightforward. List every strategic commitment with more than 10 people or $1M allocated. For each, estimate mass (total resources including reputational), pull radius (count the adjacent decisions it influences), and escape velocity (what would it actually cost to reverse this commitment, including political cost). Then ask: is each well where we want our gravity to be?

Most organizations that run this exercise discover two things. First, they have 2-3 gravity wells they never consciously chose — commitments that accumulated mass through incremental decisions until they became load-bearing strategic infrastructure. Second, the wells they did consciously choose are pulling decisions they never intended to capture. A cloud migration decision from 2021 is still shaping hiring criteria in 2026. A data platform commitment is still dictating how AI gets deployed. The well does not care about the original intent. It cares about mass.

The connection to the physics of organizational progress is direct: gravity wells are the primary source of the organizational mass that resists acceleration. They are also the reason optimal estrangement matters — sometimes the only way to see your own gravity wells clearly is to step outside their pull radius. And entropy arbitrage becomes possible precisely at the boundaries between wells, where the gravitational pull is weakest and the decision space is most open.

The dangerous question is not "what is our strategy?" Every organization has an answer to that. The dangerous question is: "did we choose this strategy, or did it accumulate enough mass to choose us?"

Related Reading

• Entropy Arbitrage: The Business Model — Gravity wells are where entropy arbitrage concentrates
• Optimal Estrangement — Strategic gravity requires the right distance from execution
• The Physics of Progress — Strategy-as-gravity is the organizational physics thesis applied to planning