---
name: gravity-field-empowerment
description: "Activate when: user asks 'did this transformation actually work', 'how do I measure whether coaching/strategy/capital changed the business', 'why does our improvement not stick', 'how do I choose between competing empowerment options', or evaluates a business program by its immediate effect rather than long-term compounded velocity change.
  Do NOT activate when: the business survival horizon is under 12 months (integral effect cannot materialize), or no baseline growth metric exists to measure velocity change against."
---

# Gravity Field Empowerment

## Overview

Most improvement frameworks measure interventions by immediate effect — quarter-over-quarter lift, year-one ROI. This systematically undervalues interventions that produce permanent velocity changes vs. point-in-time additions. A consulting engagement adding $1M this year looks identical in a snapshot to one that permanently raises growth velocity 3 points — but over 10 years the compounded difference can be 10x.

The framework applies General Relativity: a gravitational field accelerates objects passing through it, leaving them at a permanently higher velocity afterward. The value of empowerment is the integral — cumulative area between empowered and baseline trajectory over all future time (the integral effect).

Compose with [second-order-thinking] (map downstream consequences of velocity change) · [margin-of-safety] (survive the intervention's cost) · [s-curve-technology-adoption] (identify which S-curve the business is on).

## When to Use

- Evaluating a major transformation (leadership, strategy, capital raise, org restructure) by long-term velocity, not short-term lift
- Diagnosing whether a past intervention produced a velocity change or merely an addition
- Choosing between competing empowerment options based on integral effect, not immediate cost
- Business has had repeated transformations with no lasting effect

**When NOT to use:** Survival horizon < integral materialization window · Baseline velocity unmeasurable · Evaluation horizon < 18 months · Justifying pre-decided programs.

## Coaching Novices (Adaptive Front Door)

**Engine mode:** user has a concrete case → run The Process directly.
**Coach mode:** user is unfamiliar → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. **What-it-is:** "Gravity field model distinguishes additions (revenue up in one period) from velocity changes (growth rate permanently higher). This framework identifies which interventions change the engine, not just fill the tank — the integral effect."
2. **Check fit:** "What is your current baseline growth velocity — revenue or key metric — and what is it vs. 12 months ago?"
3. **Elicit the real case:** "Name a specific transformation you've implemented or are considering. Was it an addition or a velocity change?"
> **[WAIT — do not advance until user responds]**
4. **Run The Process:** "Measure growth velocity before and 12-18 months after the empowerment ends. Which of the eight levers did it engage?"
> **[WAIT — do not advance until user responds]**
5. **Name the insight:** "Which lever would create a permanent 3-5% velocity increase right now? What is the 5-year integral effect worth in dollars?"
> **[WAIT — do not advance until user responds]**

## The Process

**Output:** Empowerment Field Analysis + Integral Effect Projection

1. **Establish v₀.** Measure growth rate on the primary metric for the last 12-24 months. *Gate: no quantified baseline → stop.*
2. **Identify the lever.** Pick ONE of eight: Cognition · Strategy · Capital · Resources · Scarcity · Org Change · New Growth · Lean Ops. *Gate: if all eight look equal, diagnosis is incomplete.*
3. **Define the acceleration period.** Start event, end event, observable acceleration signals. *Gate: must have a defined end — open-ended programs are unmeasurable.*
4. **Measure v₁.** 12-18 months after end event. Delta = v₁ − v₀. v₁ > v₀: velocity change (field). v₁ ≈ v₀: addition or no effect. *Gate: evaluate at the prescribed time, not earlier.*
5. **Calculate integral effect.** Project (v₁ − v₀) × revenue × compounding factor over 3, 5, 10 years. *Gate: use measured v₁, not aspirations.*
6. **Stop-rule:** No specific, measurable velocity outcomes defined → motivation speech, not gravitational field. Return to Step 2.

**Output template:**
`Business · Date · Metric | v₀: [X]% per [period] over [N mo] | Lever: [one of eight] + rationale | Period: [start → end] + signals | v₁: [X]% · Delta: [±pp] · [field/addition/no effect] | Integral: 3yr [Δ] · 5yr [Δ] · 10yr [Δ] | Cost: [total] · Breakeven: [date]`

*→ Method in Action: [The 1919 Eddington Eclipse Observation and GPS](examples/1919-eddington-eclipse-observation-and-gps.md)*

## Empowerment Field Packs

**Pack 1 — Early-Stage (Pre-PMF):** Cognition (founder shifts to customer-problem focus → retention rises) · Strategy (ICP narrowed → sales cycle shortens) · Capital (seed removes hiring constraint) · Scarcity (moat identified → win rate rises).

**Pack 2 — Scaling (Post-PMF):** Org Change (founder-led → function-led → decision speed rises) · Resources (channel partnerships → CAC falls) · New Growth (second market → revenue concentration falls) · Lean Ops (gross margin improvement → unit economics improve).

## Applying It Well

1. **The integral is the point.** Evaluate on the 5-10 year integral, not year-one effect.
2. **One lever, maximum field.** All eight simultaneously = noise, not fields.
3. **The baseline must be real.** No baseline = no velocity delta = no framework.
4. **18 months minimum.** Year-one results conflate additions and velocity changes. Capability installation (changed decisions, new markets, org restructure) creates velocity change; information transfer (workshops, reports) creates additions.

*→ Primary sources: [references/sources.md](references/sources.md)*

## Common Rationalizations

**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**

| Fake move | Reality |
|---|---|
| [D] "Everyone feels more energized and aligned." | Feeling is not velocity. Measure growth rate before and 18 months after. |
| [D] "Our metrics aren't mature enough to measure baseline." | Build metric maturity before spending on empowerment programs. |
| [D] "Value exists but is hard to quantify." | Unquantifiable value is the standard defense of addition-generating programs. |
| [D] "We need a holistic transformation across all eight levers." | Diffuse effort creates less acceleration than a strong field in one lever. |
| [D] "Results will show up in years 2-3." | If velocity hasn't measurably increased at 18 months, more time is unlikely to help. |
| [D] "Our business is too complex for one lever to dominate." | Every business that scaled found the dominant lever per stage. |
| [D] "Worth it for team development even if growth didn't change." | Valid goal — name it as that, not as a gravitational field. |
| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |

## Red Flags

- No quantified baseline velocity before the intervention · Lever not identified · No defined end point for the program · Evaluating within 12 months · Success criteria = "alignment" not growth velocity · Repeated programs with no velocity change · Program = information delivery, not capability installation

## Verification

- [ ] Quantified v₀ for the primary metric
- [ ] ONE primary lever identified
- [ ] Acceleration period has start and end events
- [ ] Velocity evaluation scheduled 12-18 months after end event
- [ ] Observable acceleration signals specified
- [ ] Integral projection uses measured v₁ (or labeled forecast)
- [ ] Cost compared to 5-year integral; survival horizon sufficient

---
*Part of **deciqAI Knowledge Skills** — 225 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/s/gravity-field-empowerment** · Built by deciqAI · github.com/deciqAI · Contributions welcome.*