Skip to content
Bill Eisenhauer edited this page Aug 7, 2026 · 5 revisions

🏠 Leverage Lab

Owner: Bill Eisenhauer Last Updated: August 6, 2026 Status: 🚧 Living research Contributors: Bill Eisenhauer


A company-neutral field guide for finding and moving constraints in software delivery systems where humans, agents, platforms, and partners all contribute capacity.

Leverage Lab is a small deterministic simulator. This wiki explains the operating hypothesis behind it and offers practices that can be adapted without adopting the simulator's constants.

The argument in one picture

flowchart LR
    A["More build capacity"] --> B["More implementation output"]
    B --> C{"Can the rest of the system absorb it?"}
    C -->|No| D["WIP, rework, and attention pressure"]
    C -->|Yes| E["More accepted and owned outcomes"]
    D --> F["Locate the governing constraint"]
    F --> G["Run a bounded intervention"]
    G --> H["Collect a learning receipt"]
    H --> F
Loading

In prose: adding production capacity only creates leverage when shaping, context, verification, integration, adoption, and ownership can absorb the added output. When they cannot, the useful response is a measured constraint-learning loop rather than another blanket transformation.

Start here

If you want to… Read…
Understand the core claim Operating Hypothesis
Understand why work should be ready before commitment Kitting and Wait States
Design work across people and agents Human-Agent Delivery System
Run constraint-focused learning cycles Constraint Learning Loop
Inspect the simulator's math and limits Simulator Model
Use the lab with a team Facilitator Guide
Trace the ideas to public material Sources and Further Reading

What this is—and is not

This is an operating hypothesis, not a benchmark, maturity model, branded transformation, or diagnosis of a particular company. It combines established flow and constraint ideas with an emerging question: what changes when implementation becomes more abundant through agents?

The reusable proposition is:

Measure value at the boundary where work becomes accepted and owned. Improve the current system constraint. Then look again, because a successful intervention changes the system.

Repositories


Next: Operating Hypothesis

Clone this wiki locally