Capitalism in America; Review

The Moment That Stopped Me

Somewhere in the long middle of this book, the American worker walks off the farm and ends up at a desk. Greenspan and Wooldridge tell it as a handoff. The manual worker passes the economy to the knowledge worker and exits the story.

I read that passage twice because something about it didn't sit right with me. A week earlier I'd been standing in front of a fire alarm panel, an addressable system on a network, and I had to reconstruct its maintenance history myself because most of the paper trail never existed. Programming that panel was knowledge work by any definition Greenspan would accept. An hour later I was on a ladder terminating devices.

Nobody handed anything off in that room. The technician kept both, and the book never notices. That omission is what this review is about.

The Thesis

The argument is simple and they never hide it. America got rich because it tolerates creative destruction better than any other nation. New methods kill old ones. The refrigerator put an entire ice-harvesting industry in the ground, nobody reasonable wants it back, and the labor and capital that used to cut lake ice went off and built something better. Most countries protect the dying thing; America mostly lets it die. They keep score in productivity, and across three centuries the score is hard to argue with.

They're honest about the cost, which surprised me. The churn wrecks real livelihoods and real towns and the book doesn't pretend otherwise. Their claim is that the trade is worth it, and the long stretch on the 1930s is their proof of what freezing the churn buys you, a poorer country and a slower recovery. Strip the academic framing off and the argument is short. The old method dies so the better one can take its place.

Where It Lands

I came to this book expecting an argument and left agreeing with the engine, mostly because I've watched it run inside my own trade and can't pretend otherwise.

When addressable systems showed up, the old hands who swore by hardwired zone logic fought it. They were wrong. An addressable panel tells you exactly which device is in trouble, and a zone panel only gives you the hallway. The field figured that out faster than the arguments did, because the callback settles that kind of question, and the addressable panels earned fewer callbacks. Same story when cellular communicators came for the POTS dialer. I burned years chasing trouble signals that turned out to be a corroding copper pair somewhere between the panel and a central office the phone company had quietly stopped caring about. Somebody missed all of that gear, and the trade is better off without it.

There's a quieter thing the book gets right too. Tolerating the churn takes discipline, and the pressure always runs the other way, toward protecting whatever's dying. A tradesman deals with the same thing at a smaller scale, letting go of an old habit every time the code cycle moves.

Where It Misses

The book prices destruction in the units it can see, which means industries and jobs. Destroyed knowledge never gets a line item, so the book has no way to count it. When a trade loses its old hands, it loses things nobody ever wrote down, like what a smoke head really does after twenty years of coastal salt, no matter what the datasheet said at install. A productivity series can't measure that kind of loss. You find out about it during a fire.

The deeper miss is the workforce itself. In this book the worker is an output. The economy churns and the right workers are supposed to emerge on the other side, retrained by markets and mass schooling, and the story moves on. Schooling gets pages and apprenticeship gets nothing. The book never asks what happens when the next era needs a worker nobody is deliberately building, one who has to carry the old manual work and the new knowledge work at the same time, on the same paycheck.

That worker exists, and the federal government has already bet a reliability model on him.

The Trades View

Here's the book's thesis applied to my corner of the world, in a document most people will never read.

NFPA 72 requires the initiating devices on a fire alarm system tested 100% every year. That frequency didn't come from a desk. Like most fire code, it came out of fires where the devices didn't work. The Department of Defense runs on a different document, UFC 3-601-02, dated 7 Oct 21 with Change 1 on 18 Apr 25, which tells its users to apply its task frequencies "in lieu of the tasks and frequencies in the National Fire Codes." Its Table 2-1 puts the initiating devices on two-year test cycles. That is half the testing, on purpose.

The new frequencies came out of a reliability-centered maintenance model the Air Force summarized in AFCESA/CES Technical Report 01-10, if you want to look it up. The model assumed a fire demand of one event in fifty years, and it assumed the testing gets done right 99 times out of 100. Feed those numbers in and the math holds. The annual cycle dies and an optimized one replaces it, still rated at 99 percent system reliability. Greenspan would read that document and see his whole book in it. So do I. The model is defensible. This is creative destruction working exactly as advertised, applied to the maintenance of the systems that keep buildings from killing people.

Now walk the field. I have walked bases where 60 percent of the fire alarm systems sit permanently or partially disabled, maintenance gaps compounding reporting gaps year over year until the deficiency list quietly became the system of record. The model is still defensible, and the assumption underneath it hasn't held up.

Look at what 99 percent task effectiveness actually demands. Picture a tech on a ladder with a can of the aerosol the maker signs off on. He trips the smoke head, then checks its sensitivity against the limit the criteria track across five years. That is knowledge work, and he does it by hand. The write-up is a second task on top of the first, and it has to come out clean enough that the next tech who opens that panel can actually use it.

The criteria assume a technician fluent in both kinds of work, and they assume his paperwork will be as dependable as his testing. The spreadsheet that halved the testing also raised the bar on the person doing it, and nobody funded that side of it. The trade kept building manual workers for a job the model had already redefined.

I don't blame the UFC's writers. They built a model, and a model is a bet. This one was placed on us; the whole optimization depends on the technician doing the work right, and 60 percent disabled is what that unfunded assumption looks like a couple of decades in.

The techs in those buildings have been right the whole time, for whatever that's worth. They've said for years that the cycles don't survive staffing and turnover, and being right didn't get them anything. What the model never had was field data, and only the people who kept touching the gear know the true service life of these systems. The deferred costs are coming due now, and 60 percent disabled is the bill. Somebody has to price that recovery, and there's exactly one labor pool that can do it.

So the work runs toward us, and it's the unglamorous kind, basics executed at the level the model assumed all along. Train techs as knowledge workers, because the criteria already grade them that way, and that starts with an apprenticeship that teaches the write-up as deliberately as the terminations. The paperwork counts as the work now, and the report belongs to the building. Somewhere down the line another tech is going to stand where you stood and inherit whatever you left him.

Verdict

I expected to spend this review arguing with a central banker. Instead the book gave me the clearest description I've read of the force that rewrote my own trade's maintenance cycles, then showed its one blind spot by walking right past the person standing in front of the panel. Read it to understand the engine, because the engine is real and it isn't slowing down, and its newest models rest their assumptions on the trades whether the book sees that or not.