Wild card: written to one of my adult children opening an old box of plans after I am gone Someday one of my kids is going to find a box of my old construction material and make the mistake of asking: “Mom, what building was this?” And if I am still alive, God help them.
Because I am not going to say: “Oh, that was the building with the nice lobby.” No. I am going to say something deeply unreasonable like:
That floor took this many concrete trucks. They poured this section first. The cutoff was over there. The next pour picked up here.
There were this many linear feet of black iron sprinkler line in this size, this many in that size. The wire guidance was 10-6 copper in the concrete floor. That took this many rolls. The black iron came on this many trucks.
The concrete took this many days. And my child is going to stare at me with the same expression people have used on me for most of my life. Why do you know that? Fair question.
I don't know. I just do.
I CANNOT TELL YOU HOW MANY LIGHTS THERE WERE
This is the part that makes the memory funnier. I cannot tell you every sprinkler head. I cannot tell you every light. In some buildings I could give you a strong estimate.
But not the actual number. Apparently my brain did not index the building by ceiling fixtures. It indexed the building by material flow. Truckloads.
Linear feet. Rolls. Pours. Sequences.
Cutoff points. What came first. What had to arrive. What physically became the building.
That is how I remember things. Not as decoration. As architecture becoming matter.
THE BLUEPRINT WAS NOT A PICTURE TO ME
A blueprint tells you what the future is supposed to become. That always fascinated me. Line. Dimension.
Symbol. Note. Then somebody orders material. A truck arrives.
People move it. Something gets cut. Something gets installed. Concrete gets poured.
A line that used to live on paper becomes a physical boundary a human may walk past for fifty years without ever thinking about it. I loved that transformation. Intention becoming matter. I think my brain started counting because quantities are how intention crosses the boundary.
The drawing says a thing exists. The takeoff tells you how much reality it requires.
THE CUBIC FEET MATTER BECAUSE GRAVITY IS NOT IMPRESSED BY VISION
You can have a magnificent architectural concept. At some point somebody needs enough concrete. Not inspirational concrete. Cubic feet.
Enough trucks. Enough time. A sequence. A place for the pour to stop.
A place for the next section to begin. There is something wonderfully honest about that. Vision is allowed. Then physics invoices you.
That may be one of the reasons I later became such an operational person. I like the place where ideas are required to become true.
THE BLACK IRON HAS TO ARRIVE
Same with sprinkler lines. A drawing can show the path. Somebody has to know how many linear feet of black iron that path becomes. Different sizes.
Different quantities. Material movement. Delivery. Storage.
Installation. Suddenly the abstract system has weight. This is probably why software people making folders wherever they feel like it can drive me completely insane. In construction, you cannot casually say:
“Well, this pipe is basically equivalent over here.” No. It occupies space. It intersects other systems.
Somebody has to install it. Somebody has to reach it later. Location is function. Architecture is not a suggestion.
THE COPPER IN THE FLOOR
Wire guidance in concrete is one of those details my brain apparently decided was important enough to keep forever. 10-6 copper lines. Feet of it. Rolls of it.
What went into the floor before the floor stopped being accessible. That is sequencing. Before the concrete, you have opportunity. After the concrete, you have a very different problem.
This is why I love state transitions. They matter. Before pour. After pour.
Before departure. After departure. Before production tooling. After tooling.
Before deployment. After deployment. Some changes are cheap before the transition and expensive after it. A good engineer understands when the state is about to become harder to reverse.
THIS BECAME MY ENTIRE LIFE WITHOUT ME NOTICING
Construction should have been one chapter. Then Amazon happened. Suddenly I was standing inside fulfillment buildings and doing the same thing with different nouns. Instead of concrete trucks:
volume. Instead of black iron: conveyance. Instead of copper in the slab:
logic embedded into the operating architecture. Instead of pour sequence: Critical Pull Times. Instead of material staging:
freight staging. Instead of trucks delivering construction material: trailers carrying completed work away. I did not consciously say:
Ah yes. I shall now transfer my construction-based systems model into fulfillment. I just looked at the building and it made sense.
THE WAREHOUSE WAS A COMPUTER
Then it got even more ridiculous. I looked at the warehouse and saw a computer. Package enters. Identified.
State assigned. Routed. Processed. Buffered.
Diverted. Recirculated. Exception. Truck leaves.
Cache cleared. Of course. I have said that my mental image of a computer still somehow has a 386 living inside it. That is apparently what happens when your brain learns one organizing structure early and then refuses to stop applying it to everything else.
When I first saw C, the logic felt familiar. Variables. Pointers. Functions.
Conditions. Loops. Queues. Flow through architecture.
Years later, the warehouse looked like C made out of steel. Now software looks like a warehouse with no forklifts. Apparently this is my personality.
I APOLOGIZE TO MY CHILDREN
This means none of you can stand in a grocery-store line with me without risking a lecture about queues. You cannot show me a messy closet without me thinking about location architecture. You cannot say a business is busy without me asking about throughput. You cannot say a website “basically works” if the file structure is insane.
You cannot ask me how many trucks it took to build a floor unless you have time. I did not choose this burden for you. You inherited it by proximity.
THE FUNNY PART IS THAT I DO NOT THINK I HAVE A GOOD MEMORY
I forget ordinary things. Where did I put that? Why did I come into this room? What day is it?
Normal human nonsense. Then show me an old building and my brain goes: Oh yes, seventeen years ago, material came in from over there, this section went first, the cutoff was here, the sequence changed because of that, and we needed roughly this many trucks. What the hell.
Memory is not one thing. Apparently mine likes relationships. If the fact belongs to a system, it has somewhere to live. If it is an isolated fact, good luck.
That is why I remember architecture.
THE BUILDING EXISTS AS A GRAPH IN MY HEAD
I do not mean a literal computer graph. I mean relationships. This feeds that. This came before that.
This amount required this movement. This constraint changed this sequence. This system occupied this space. That is how expertise gets compressed.
The individual facts stop being individual. They become environment. Then a tiny cue loads the environment. A photograph.
A building name. A material. Zoop. The system is there.
THE SAME THING HAPPENED WITH FULFILLMENT CENTERS
Someone could send me a tiny exception years later. A site. A weird behavior. A fragment.
And suddenly I knew which questions mattered. Where is the freight? What should be happening? Which direction do I look?
That is not magic. It is indexed context. The same reason I can remember a concrete-pour sequence. The event is attached to a system.
THE SAME THING HAPPENED WITH PRODUCTS
Product development looks completely unrelated until you inspect the structure. Idea. Prototype. Material.
Testing. Manufacturing. Packaging. Freight.
Inventory. Marketplace. Customer. Same basic brain.
What enters? What changes state? What depends on what? Where does truth live?
What is expensive to reverse? What happens next? The product is another building. The business is another building.
Software is another building. God help us, apparently everything is a building.
WHY I COUNTED TRUCKS
Truckloads are an interface between design and reality. A quantity on paper becomes a delivery schedule. A delivery schedule becomes site capacity. Site capacity becomes sequence.
Sequence becomes labor. Labor becomes progress. Progress becomes the building. If the trucks do not arrive, the line on the blueprint does not become matter.
That makes the truck part of the architecture even though nobody puts the truck in the final photograph. I have always loved those invisible dependencies. The things that make the visible thing possible.
THE KIDS WILL PROBABLY CARE ABOUT THE WRONG DETAILS
If my children read this someday, they will probably care less about how many feet of black iron were in a building than I do. Reasonable. They may care that their mother could tell them. That is the autobiography part.
Facts are funny when they reveal the shape of a person. The fact that I can tell you a concrete-pour sequence and not the light count tells you something about what my attention considered important. Movement. Dependency.
Sequence. Capacity. That is me.
THE MATERIAL QUANTITY IS A STORY ABOUT PEOPLE TOO
Every truckload had a driver. Every pour had a crew. Every line of black iron had people moving, cutting, fitting, installing. Every roll of copper became somebody's physical work.
This is why systems thinking never made people disappear for me. The system is made of humans and materials interacting under constraints. A perfect plan that humans cannot execute is not a perfect plan. A beautiful blueprint that ignores field reality will get corrected by field reality.
That lesson followed me everywhere.
THE PERSON CLOSEST TO THE WORK KNOWS SOMETHING
The installer knows something. The driver knows something. The operator knows something. The new associate knows something.
The customer knows something. The engineer knows something. The manager knows something. None of them owns complete truth alone.
Good systems collect distributed truth before making expensive decisions. I learned that in buildings. I used it in operations. I use it in software now.
THE COST OF BEING WRONG CHANGES BY STATE
This may be the most important thing construction taught me. Before the pour, move the line. After the pour, good luck. Before production, change the prototype.
After ten thousand units exist, congratulations on your inventory problem. Before deployment, fix the architecture. After customers depend on it, change control matters. The earlier you discover the problem, the cheaper the problem usually is.
That is why I like prototypes. Mockups. Test runs. Baselines.
Small changes. Cheap truth. Find the error while it is still pencil.
THE ERASER IS ONE OF THE BEST ENGINEERING TOOLS EVER INVENTED
I loved blueprints. I also loved that plans could change when reality taught us something. There is no honor in defending the wrong line because you drew it first. Erase it.
Revise. Document the change. Understand what the revision touches. Then proceed.
That is still how I want to work. I am loyal to the system functioning. Not to my first idea.
WHY MY CAREER LOOKS LIKE SOMEBODY DROPPED A TOOLBOX
Computers. Army. Construction. Engineering.
Ecommerce. Toy manufacturing. Warehouses. Conveyance.
Ship dock. Regional networks. Software. AI systems.
From the outside, that is ridiculous. From inside my head, it is one long story. Take an idea. Understand the architecture.
Quantify what reality requires. Sequence it. Move it through constraints. Observe.
Fix. Scale. Then discover the next constraint. The materials changed.
The brain did not.
THE BLUEPRINT BOX
So if one of you does find a box of my old plans someday, keep at least one. Not because the paper is sacred. Because it is funny evidence. Your mother was apparently the kind of human who looked at lines on paper and remembered truckloads decades later.
And if you find my notes in the margins, I hope they make you laugh. There will probably be arrows. Quantities. Something underlined too aggressively.
Maybe an irritated note about sequence. That seems on brand.
THE THING I WOULD ACTUALLY WANT YOU TO KEEP
Not the truck count. You can forget the truck count. Keep the habit. When something complicated is in front of you, do not panic because there are too many pieces.
Find the architecture. What depends on what? What has to happen first? What becomes expensive to change later?
Where is the bottleneck? Who knows something you do not? What would make the next state possible? Then work the problem.
That is what the blueprints gave me. That is what the warehouses reinforced. That is what coding made explicit. And if someday you are building something I cannot even imagine, I hope the same questions still work for you.
They probably will. The materials change. The logic has a way of hanging around.
A STRANGE KIND OF INHERITANCE
People leave jewelry. Furniture. Recipes. Photographs.
I will apparently leave operating logic. That makes me laugh. Maybe one of you will someday be trying to figure out why a business process is failing and hear my voice in your head asking what changed upstream. Maybe you will be building something and stop before the irreversible step because you realize the state is about to become expensive to change.
Maybe you will look at a system everybody says is hopelessly complicated and start drawing arrows. If that happens, congratulations. I got you. You inherited the weird part.
I hope it serves you as well as it served me.
THE PRACTICAL TEST
Whenever I teach this idea, I come back to one practical test: can somebody else use the reasoning? A story is entertaining. A method is transferable. If another manager or owner can read the story and recognize a problem in their own environment, then the experience has become more than history. They can ask the same questions, establish their own baseline, inspect their own constraints, and build an answer appropriate to their own system. That is what I want from these stories.
Not imitation. Recognition. The specifics belong to my life. The logic should travel.
AND THEN REALITY GETS A VOTE
Every plan eventually reaches the point where discussion stops and the system answers. The truck arrives or it does not. The customer buys or does not. The queue clears or grows.
The floor accepts the design or exposes the flaw. The user understands the interface or starts inventing a workaround. I like that moment. It is honest.
You learn what part of your model survived contact with reality. Then you update it and keep moving. That loop—design, observe, learn, redesign—is probably the most consistent habit in my entire career.
THE QUANTITIES WERE NEVER JUST NUMBERS
They were the proof that the drawing had consequences. A line on paper became an order. The order became a truck. The truck became material on site.
The material became labor. The labor became sequence. The sequence became a place somebody could later walk through without ever knowing the chain behind it. That chain is what my brain remembers.
Maybe that is why I have always been so drawn to operations. Operations is the invisible chain becoming visible long enough to improve it. Then, if you do the work well, the chain disappears again into something that simply functions. I have always found that beautiful.