Low diatribe

My 30-year career stalled. Not slowed — stalled. The options narrowed over months until one remained: take a job making pizzas at a regional chain in one of the lowest-income counties in Iowa. The kind of place that describes itself, without irony, as a pizza restaurant that happens to sell gas.

I took it as a bridge. A way to get from where I was to somewhere else. Something to fill the gap while the real thing materialized.

That's what you tell yourself. That this is temporary infrastructure. That you're just crossing.

I've read William Gibson since the 80s. His Bridge trilogy — people making a home out of infrastructure that was never meant for one — sat with me the way good speculative fiction does: not as prediction, but as a lens. A way of seeing systems that weren't built for people somehow becoming human anyway.

I found that this bridge was a Bridge.

Not a gap crossing — an ecosystem. Complete in its own logic, running on its own rules. I'd entered cautiously, deliberately — trying to learn the system before presuming to understand it, resisting the pull to lead with thirty years of pattern recognition. That lasted less than a week. The system has a way of finding what you know and putting it to work whether you offer it or not.

The prep flow, the ticket timing, the way a good line runs versus a broken one, the informal hierarchies that actually move things versus the official ones that don't. I couldn't unknow what I was seeing.

I'd estimate the system runs at about 25% of what it could be. Which sounds damning until you remember that's roughly the efficiency of an internal combustion engine — most of the energy going to heat, friction, noise, everything except forward motion. That's not a design flaw unique to this kitchen. That's the baseline condition of most systems. And like an engine, it runs. The business continues.

That's not a failure story. That's a resilience story.

Systems that were never designed for what they became, improvised and layered and patched until they developed their own coherence. Structures held together not by design but by the accumulated weight of people making do. Not optimized. Not planned. Alive in ways the original blueprint never anticipated and couldn't have produced.

The thing I keep coming back to: it's a human-based system that isn't particularly human-focused.

It runs entirely on people — their judgment, their presence, their improvisation under pressure. Without the people, there is no system. And yet the system isn't built around the people mattering. Their experience, their dignity, their growth — these aren't load-bearing in the design.

Everyone in that store except the store manager is an hourly employee. To corporate, the people running the system are, by design, interchangeable. My "full time" schedule was consistently 32-34 hours per week — enough to stay well under the overtime threshold.

The corporate apparatus has opinions about human-centeredness. There are initiatives — a C.A.R.E.S. acronym (Commitment, Authenticity, Respect, Evolving, Service), growth opportunities, all the trappings of investment in people. They arrive as laminated posters and all-staff emails, addressed to everyone, written for no one in the room. The distance between the sentiment and the floor isn't cynicism — it's friction. The store manager talks about human things, but she's spending her energy herding the room into basic compliance. The sentiment never lands because there's no space left to carry it.

And yet the store isn't cold. People look out for each other, cover shifts, absorb the rough nights without complaint. The care is real — it just didn't come from the poster. It came from the people who showed up anyway.

But seeing it at this scale, in this place, where the margins are thin and the options are fewer — it's harder to look away from.

I've built a career trying to create the opposite. Environments where talented people naturally do their best work. Systems that are human-based and human-focused. Being inside something that separates those two things so cleanly has been its own kind of education.

The lessons from a pizza kitchen aren't lesser lessons because of where they came from. Flow under pressure. The cost of a broken system at volume. What good handoff looks like. How a team degrades when communication fails. How much a single person who gives a damn can hold together. These are real. The context is just unexpected.

I pulled every lesson I could find. Not because I was holding them in reserve for somewhere legitimate.

That word — legitimate — is worth sitting with. It arrived with the job, carried in by every well-meaning question about what I was doing next, every careful pause after they heard the answer. The implication was structural: this doesn't count. This is a waiting room. The real work happens somewhere else, in a context that confers validity, and until you're there, you're between things.

I've been actively dismantling that framing. Not because the kitchen is secretly prestigious — it's not — but because the framing itself is the problem. Lessons don't have a dress code. Systems don't care where you learned to read them.

So I use what's available. I build with what's there. I redesign the order system in my head while I toss dough and spread cheese — not as an abstraction, but because I can see exactly what's broken and exactly how to fix it. The dough doesn't mind.

On my fifth shift — the last day of what passed for training — the kitchen manager asked if I had my key. When I said yes, she said: Cool, you'll be okay closing by yourself tonight, right?

Sure. What else was I supposed to say?

On my ninth shift, she asked if I wanted to be shift lead.

Nine shifts. Not nine months. The bar for leadership in that kitchen isn't tenure or credentials — it's showing up and being someone the system can lean on. She reads people fast. She delegates without ceremony. She's been running that kitchen long enough to know exactly what it needs, and she moves accordingly.

When the fryer needs cleaning or the oil needs changing, she's one of maybe two people in that kitchen who will just do it. I'm the other one.

Competence recognizing competence. No announcement required.

Almost the entire staff is under 30. A majority of that is teenagers.

The system doesn't care about my resume or their age. It cares whether you show up and whether you can hold your piece of it together. The teenager who knows the oven timing is as essential as anyone. In that kitchen, we're all just keeping it running.

The kitchen is its own subsystem within the larger store. I don't see much of the floor, the front counter, the gas pumps — I'm fairly isolated back there, and that isolation has its own logic. Occasionally a decree arrives from the store manager, addressed to everyone, clearly written for a handful of teenagers. I read it, note that it doesn't quite fit the room I'm standing in, and get back to the dough. She's doing her best with an unruly bunch. I haven't come up with a better approach myself. Corporate to store. Store to kitchen. The distance between the message and the floor is consistent at every level of the hierarchy.

I've only ever worked the closing shift. Most nights I close alone. Occasionally someone stays until an hour or two before the end, but the final stretch is always mine — the fryer, the surfaces, the reset for whoever opens tomorrow. Nobody marks it. You just do it and leave.

I dropped to part time when the consulting contract came. I kept the option open deliberately — I'm still there on weekends, still one of the people holding a piece of it together. Still living on the Bridge.

Still showing up to a system that needs me without particularly seeing me. Still pulling lessons from anything available.

The Bridge didn't give me somewhere to get to. It gave me somewhere to be. And being there has shown me something that a single path — however well-built — never could have.