Human Capacity Infrastructure

Band-Aids, Six Sigma, and Fire Codes

One bad habit. One proven fix. One analogy your aunt will remember.

Molly Woodbridge · mollywoodbridge.com · v1.3

The thesis

Public-trust institutions know how to buy AI. They do not yet know how to institutionalize AI.

This explainer lives in the gap between those two sentences.

The habit

The Band-Aid Cycle

Skip the upstream baseline. Pay the downstream tax. Budget the tax as if it were normal. Repeat.

Skip the upstream baselineIt looks like savings. It is a loan.

Problems compound quietlyInterest accrues where nobody is looking.

Fund the downstream fixesNow with staff, programs, and urgency.

Call the tax the budgetThe loan payment becomes a line item.

Repeat until the budget is entirely tax. It is not a failure of caring. It is a failure of sequence.

The cycle, invoice one

Exhibit: Education

The skipped upstream

Proper nutrition
Physical movement and play
Early health care

The downstream tax

Remedial tutoring
Behavioral intervention programs
High school retention staff

The upstream side is not hypothetical. The LiiNK Project at TCU has spent over a decade producing peer-reviewed research on movement and play as baseline conditions for learning.

We pay full price downstream to fix what we declined to prevent at a discount.

The cycle, invoice two

Exhibit: Workforce

The skipped upstream

Honest job information
Realistic fit screening
Non-negotiables named before applying

The downstream tax

Churn and ghosting
Mis-hires and burnout
Re-recruiting the same seat, annually

GateForce85 is my prototype for the upstream half: a documented, seeker-side decision-support model that scores opportunities against a person's stated non-negotiables before they spend six months finding out the hard way.

Job transparency is nutrition for the labor market. Skipping it has a tuition rate.

See GateForce85

The cycle, invoice three

Exhibit: AI Adoption

The skipped upstream

Who reviews the outputs
Who owns the decisions
What gets documented, and how you leave

The downstream tax

Cleanup and do-overs
Vendor gravity: the vendor's defaults become your operating model
Institutional memory that evaporates

The tools arrive, the training happens, and everyone assumes implementation has occurred. It hasn't.

Most organizations don't have that layer. They have software.

The pattern

One pattern. Three invoices.

Sector	Skipped	Paid for
Education	Nutrition, movement, early care	Tutoring, intervention, retention
Workforce	Honest information and fit	Churn, burnout, rehiring
AI adoption	The operating discipline	Do-overs, lock-in, lost memory

When the same failure appears in three unrelated sectors, it is not a sector problem. It is a sequence problem.

Has anyone ever fixed a problem shaped like this?

Twice. Once with a Greek letter, once with a clipboard.

Exhibit A

Six Sigma: a discipline that outlived its tools

1986. Motorola. An engineer named Bill Smith connects field failures to factory defects and proposes something unglamorous: a shared way of measuring, naming, and removing defects before they leave the factory.

No software was purchased. A method was institutionalized. The tools came and went. The discipline stayed.

3.4

defects per million opportunities: the standard the name refers to. The habit it replaced: inspect at the end, fix in the field, call it quality.

How a discipline actually scales

One practitionerBill Smith, a working engineer. Not a committee.

Real conditionsMotorola's actual defect data. Not a whiteboard.

One executive championCEO Bob Galvin made it the company's language.

One public validationThe Malcolm Baldrige National Quality Award, 1988. Then GE, Honeywell, and a decade of adopters.

No mass persuasion campaign. A sequence.

What Six Sigma had on day one

Coined vocabulary. Belts, DMAIC, sigma levels. Language that traveled without its author.
Portable documentation. Methods written down, so the discipline outlived Bill Smith.
Repeatable frameworks. The same process worked on the next problem. And the next.

Human Capacity Infrastructure has all three. The vocabulary is already working: the Band-Aid Cycle, Vendor Gravity, GateForce85. That is not a coincidence. It is the checklist.

Six Sigma proves the scaling model. It does not explain HCI at Thanksgiving. For that, we need fire codes.

Exhibit B

Fire codes: the simpler story

Fire codes did not appear because nobody had buildings. They appeared because everyone had buildings, and each one burned in its own creative way.

Whole cities burned before shared standards existed. The response was not to ban buildings, and not to trust each builder's personal enthusiasm for safety. It was a common standard that made every building legible, inspectable, and survivable.

Nobody calls a fire code anti-building.

The lesson survived because it was boring, written down, and enforced. Aspirations were not involved.

A code is not the thing it protects

A fire code is not

The fire department
A sprinkler vendor
A ban on buildings
A one-time inspection
A poster about fire awareness

A fire code is

A shared standard, so no builder invents safety alone
Exits designed before occupancy
Load limits named before the furniture arrives
Inspections that repeat
Boring on purpose. That is the feature.

HCI carries the same disclaimers: not an AI tool, not a training program, not a policy document in isolation, not an IT function, not a one-time implementation.

The translation

HCI is fire codes for AI adoption

The fire code says	HCI says
Exits designed before occupancy	Exit criteria designed before dependency
Load-bearing walls, named	Decision rights, named
Inspections that repeat	Human review gates
Blueprints kept on file	Documented workflows
Standardized materials	Portable, tool-agnostic formats

The building is the tool. The code is whether it holds.

Why now, why here

The buildings are already going up

The problem is no longer absence. The problem is fragmentation. Each institution is writing its own fire code from scratch. Alone.

City of Fort WorthAI governance is in place, and a city audit found 18 of 27 departments already using AI tools.

United Way InstituteOpened with Dell Technologies to build nonprofit capacity in data, technology, and AI.

State of TexasA statewide AI governance law is in effect, with requirements reaching into local government.

The proposal

Fire codes were adopted one city at a time

Not by mass persuasion. By one jurisdiction proving the standard, and neighbors declining to reinvent it. The test for a shared Human Capacity Infrastructure standard is deliberately small:

One shared capacity standard. Written down. Portable. Nobody's product.
One workflow. Real work.
Named owners. A standard without owners is a poster.
Measurable outcomes. Falsifiable on purpose.
90 days. Long enough to mean something. Short enough to commit.

If it works, we will know. If it does not, we will also know. Both outcomes beat guessing.

You do not wait for the fire to write the code.

Human Capacity Infrastructure: the operating layer between buying AI and institutionalizing it.

Molly Woodbridge · mollywoodbridge.com

Back to mollywoodbridge.com