Leverage#

Summary#

For work of importance, start with what is true and choose moves that changes behavior of agents in the environment. Build new facts on the ground in small increments. Impose structural cost, risk or uncertainty of reversal. Watch for friction, entropy and adversaries that can frustrate the execution of the plan. Be persistent and keep the story tied to data, not intent. Negotiate incentives, not personalities: map what each actor must protect, what they need to gain, and the exchange terms that create commitment. Create alternative paths to goals of importance. Periodically prune portfolio of activities to protect strategic impact.

Nature of Leverage#

Exploring the nature of leverage in the context of developing power to influence.

Potential of Leverage#

Leverage is rooted in controlling something the other party needs, or the ability to impose costs, or shape uncertainty. These are the “facts on the ground”. The foundation of leverage is to create these up front.

The objective strength of one’s leverage is determined by the facts on the ground and the alternatives each party has access to. When negotiating, the subjective strength is what maters. This is the objective strength modified by the other party´s perception of both parties leverage in the situation.

Best Alternative to a Negotiated Agreement (BATNA). If you have strong alternatives, you are less dependent on the other party, increasing your objective leverage. This also applies inversely for your strength dependent on the alternatives of the other party.

Effective or subjective leverage also depends on how you and the other party perceives both positions now and in the future. As well as both parties perception about willingness to walk away from the negotiation.

Categories of Leverage#

Positive Leverage: The ability to provide or withhold benefits that the other party desires Negative Leverage: The ability to make or prevent the other party being worse off Uncertainty Leverage: The ability to frustrate or help the other party’s effort to predict the future

Sources of Leverage#

Positive sources (benefits and access):

  • Information: Knowing what the other party values
  • Resources and capabilities: Tangible assets (budget, capacity) and intangible capability (expertise, delivery reliability)
  • Relationships: Trust, credibility, and access to influential networks.
  • Normative legitimacy: Shared standards, policy alignment, and moral framing that support agreement.

Negative sources (cost and constraint):

  • Information: Knowing what the other party fears
  • Reversal cost: Financial, operational, and political cost imposed by undoing the new path.
  • Dependency pressure: Workflow, budget, or compliance dependencies that increase cost of refusal.
  • Enforcement position: Contractual rights, governance control, and escalation channels.

Uncertainty sources (predictability and timing):

  • Information asymmetry: Superior visibility into demand, risk, and counterparty constraints.
  • Timing control: Deadlines, sequencing, and option windows that shape urgency.
  • Scenario optionality: Maintaining credible alternatives while forcing counterparties to price uncertainty.

Mechanics of Leverage#

Define the causal chain before activity starts.

Creation: Leverage can be created from influence and effort converted into durable structure: process (defaults, dependencies, governance), and authority (legitimacy).

Conversion: If we change [process/authority], then [target behavior] shifts, producing [outcome].

Consumption: To influence another’s decisions, behaviors, or outcomes by means of a transaction.

World Model Principles#

Effective algorithms to manage leverage and work in general.

Strategic Reality Model (Ground Truth + Falsifiability)#

Model reality before mobilizing resources.

Ground-truth claim. What is true now, independent of internal narrative? Adversary/counterparty response. How stakeholders/competitors/regulators are likely to react? Critical dependency. Dependency that could break execution? Falsifier. Specific observation that would disprove the thesis?

Pre-commitment checks:

  • What must be true for this to work?
  • What would prove us wrong?
  • Access to useful external signal?

Wedge (Unique Advantage + Defensibility)#

Ensure we are building durable advantage.

Primary wedge: [proprietary data / distribution lock / workflow lock-in / regulatory moat / network effect]

Why Competitors Cannot Easily Replicate: capability, access, legal, integration, switching cost

First-Principles Execution Loop (Bottleneck Throughput)#

Drive speed and output by removing constraints, not adding activity.

Execution loop (in order):

  1. Identify the top system bottleneck.
  2. Delete non-essential steps.
  3. Simplify and reduce cycle time.
  4. Increase throughput at the bottleneck.
  5. Automate only after simplification works.

Tactical Empathy First (Counterparty Diagnosis)#

Understand their constraints before making any ask.

Before proposing terms, map what the other party must protect, what they fear losing, and what internal pressure they face.

Counterparty map:

  • Identity constraints: Role, status, and reputation they cannot compromise.
  • Loss fears: What failure, blame, or downside they are avoiding.
  • Operational pressure: Capacity, timeline, and dependency constraints.
  • Decision environment: Who must approve, who can block, and what proof is required.

Minimum conversation sequence:

  1. Mirror key language to surface what matters most.
  2. Label pressure and emotion without judgment.
  3. Summarize constraints to show understanding.
  4. Ask calibrated how/what questions to force practical design.
  5. End on a low-risk next step, not abstract agreement.

Attacker mindset (red teaming)#

Convert intent into controlled pressure and durable position.

  • Start with the end in mind, knowing your objective, plan all the way backwards to the current facts on the ground
  • Gather, weaponize and leverage information for the good of the objective
  • Never break pretext
  • Everything you do is for the benefit of the objective

Reversal Becomes Irrational#

Secure a position.

Help create a new fact on the ground and ensure that maintaining the initiative is cheaper, safer or simpler than reversal.

Incentives and Exchanges#

Assume incentives decide behavior.

Agent must protect [resources/status/risk]. Seek control of [resource/access/info/timing/sequencing]. If I deliver X, they deliver Y.

Campaign Sequence and command cadence#

Execute the loop.

Cadence (each cycle)

  • Cadence question: “What new fact exists in this cycle that did not exist in the previous cycle?”
  • Cadence control loop, what to: keep, stop, start

Campaign Sequence

  • Phase 1 Pilot: low-friction pilot, first visible commitment, monitor adoption/event threshold.
  • Phase 2 Integration: capability and workflow integration, team dependence begins, monitor usage/throughput threshold.
  • Phase 3 Expansion: proof and scaled rollout, cross-stakeholder benefit, monitor outcome threshold.
  • Phase 4 Codify: policy and budget baseline, governance and funding anchor, monitor official baseline inclusion.

Kotter 8-step mapping

  • Pilot: (1) create urgency, (2) build guiding coalition.
  • Integration: (3) form strategic vision and initiatives, (4) enlist a volunteer army.
  • Expansion: (5) enable action by removing barriers, (6) generate short-term wins.
  • Codify: (7) sustain acceleration, (8) institute change in culture, policy, and budget.

Facts on the Ground#

Make the desired path the default path.

  • Default shift: behavior becomes opt-out, not opt-in.
  • Resource lock: budget/capacity/headcount formally allocated
  • Process lock: core workflow routes through new path

Economics of Stickiness (Cost of Delay + Reversal)#

Make trade-offs explicit and auditable.

Behavior is shaped by choice architecture, not just logic. People typically keep the default, overweight near-term hassle, and react more strongly to potential loss than equivalent gain.

Thaler lens for stickiness:

  • Status quo bias: staying put feels safer than switching, even when switching is better.
  • Loss aversion: stakeholders resist changes framed as losses of control, budget, or status.
  • Endowment effect: once teams “own” a process, they value it more than outsiders do.
  • Mental accounting: costs and benefits are judged by budget bucket and timing, not total value.

Design levers:

  • Default the desired path and require explicit opt-out for alternatives.
  • Reduce switching hassle (approvals, forms, training, migration steps) in the first cycle.
  • Front-load visible gains and back-load unavoidable costs where possible.
  • Frame reversal as concrete loss (time, risk, rework), not abstract inefficiency.
  • Add commitment devices: dated milestones, public owners, and automatic review points.

Cost model (decision-grade):

  • Cost of delay: value not captured per cycle + risk accumulated per cycle.
  • Cost of reversal: migration effort + coordination disruption + credibility/political cost.
  • Hassle cost: user effort to adopt or continue (clicks, approvals, handoffs, retraining).

Measurement pack:

  • Time-to-adopt (first use to routine use).
  • Opt-out rate from new default.
  • Reversal attempt rate and reversal completion rate.
  • Cycle loss estimate from delay (throughput, risk, or quality impact).

Cycle question:

  • Did we reduce hassle, increase salience of loss from delay, and strengthen the default in this cycle?

Commitment Quality (Real Commitment vs Agreement)#

Treat yes as unverified until ownership and execution are explicit.

Commitment tests:

  • Language test: Is this concrete commitment language or polite agreement language?
  • Ownership test: Who does what next, by when, and with what dependency?
  • Evidence test: What observable signal confirms movement this cycle?
  • Resistance test: What happens if internal opposition appears?

Completion criteria:

  • Named owner for next action.
  • Dated next milestone.
  • Observable proof of execution.
  • Explicit consequence of delay or non-delivery.

Counter-Moves#

Preempt resistance and uncertainty.

Assume credible counterparties will test, delay, or reroute your initiative. Build explicit branches for likely responses before pressure appears.

Counter-move map:

  • Deny: They reject premise, urgency, or evidence.
  • Delay: They agree in principle but stall ownership and timing.
  • Dilute: They accept scope but remove the mechanism that creates impact.
  • Divert: They reframe toward adjacent work that consumes capacity.
  • Escalate: They move decision rights to a forum where you are weak.

Preemption actions:

  • Pre-wire decision owners before formal asks.
  • Package evidence at decision-grade quality (cost, risk, throughput, adoption).
  • Define minimum acceptable scope and explicit no-trade boundaries.
  • Prepare fallback path with reduced scope but preserved direction.

Cycle question:

  • Which counter-move appeared this cycle, and what branch did we execute?

Narrative Control (Legitimacy System)#

Who defines success shapes decisions.

Narrative is not spin; it is the operating frame that determines what is considered valid, urgent, and fundable.

Legitimacy stack:

  • Problem frame: Why this matters now in business and risk terms.
  • Success criteria: How outcomes are measured and by when.
  • Evidence standard: What proof is required to continue investment.
  • Decision rights: Who can approve, block, or reinterpret results.

Narrative operating rules:

  • Name the baseline before proposing change.
  • Use comparative deltas (before/after), not intent language.
  • Tie wins to shared institutional goals, not team identity.
  • Publish regular scorecards so interpretation cost stays low.

Failure mode to avoid:

  • Allowing opponents to redefine success after evidence is produced.

Avoid overextension#

Protect strategic throughput by limiting active fronts.

Overextension destroys leverage by fragmenting attention and weakening proof. Run fewer initiatives with higher completion quality.

Portfolio discipline:

  • Keep a strict cap on concurrent campaigns.
  • Rank work by strategic impact and reversibility risk.
  • Pause or stop activities that do not improve leverage position.
  • Reserve capacity for response to counter-moves and unforeseen friction.

Pruning test (each cycle):

  • If this effort stopped now, what strategic outcome would be lost?
  • Is there new evidence of traction, or only continued activity?
  • Does this work strengthen a wedge, or just consume resources?

Completion over motion:

  • Prefer finishing one phase to launching two new pilots.