Field Notes

Pattern: Organizations apply integration thinking (centralize, standardize, control inputs) to problems requiring federation thinking (distribute, verify outcomes, govern at service layer). This creates governance theater while actual capability and control evaporate through shadow systems. Context: Government and enterprise leaders facing AI adoption using governance frameworks designed for stable technology (mainframes, ERPs, data warehouses). Works well…

Or: Finding Security Holes The Hard Way Before We Called Them That Act 1: The Takeover In mid-1999, I took over an e-commerce business from a friend. He’d bought a bunch of inventory (crash pads and other gear for bouldering) and then got busy with his actual professional job. The pads were sitting in his…

Or: Why Tacit Knowledge Fails When You Need It Most I can execute complex work. I’ve been doing it for 20 years across disaster response, federal systems architecture, and forward-deployed operations. The capability is real. The track record is documented in systems that still run, after-action reports, and infrastructure that absorbed actual pressure. But recently,…

Your brain is a cognitive miser. It is constantly trying to answer one question fast: “Can I safely ignore this and live?” Because in the real world, you cannot afford to analyze every stick like it might be a snake. You also cannot afford to get the snake wrong. So your brain runs a quick…

A ribbon cannot measure the invisible stack of work it points to. Someone asked me when I was proud to see a colleague or friend recognized. I thought for a while. I did not choose the biggest award I have ever witnessed. I chose a moment where the token was trivial compared to the signal…

The Conventional Wisdom

Integration is brittle. Federation is resilient.

This is what every systems architect learns. Integration creates tight coupling, single points of failure, cascading breakdowns when one component fails. Federation distributes risk, enables graceful degradation, scales more easily across organizational boundaries.

Most enterprise systems are designed like the network is a law of physics.

Field work teaches the opposite.

Signal drops. Bandwidth lies. Security domains get segmented. And the mission still moves forward.

Stewardship of Operational Knowledge – On Finally Documenting What I Know A personal reflection on the transition from hiding to documenting. The Silence For 20 years, I kept quiet about what I knew. I had the knowledge. I saw the patterns. I understood things that only emerge from sustained operational exposure in federal disaster response,…

Why Mislabeling Group Types Breaks Decisions People use “team” and “committee” as if they mean the same thing. They do not. A team is built for shared outcomes. A committee is built to manage competing interests. Confusing them creates conflict, delays, and sometimes failure. I learned this during a trip to the Hubbard Brook Experimental…

Competent Enough to Know What to Learn Next The Photo Distribution Problem There’s a GoPro time lapse somewhere in my files showing (found it!) three hours of work compressed into ninety seconds. My wife and I are standing over a drafting table that used to belong to Princeton University (still has the brass plate), spreading…