Map the Physics, Not the Sociology

Driving back from the lake last week I listened to Lex Fridman interview Jensen Huang. Two things stuck.

First, Jensen pointed out that every company's org chart looks the same. Hamburger companies. Software companies. Car companies. Same boxes, same layers, same reporting lines.

Second, he described how NVIDIA runs. He calls it extreme co-design: no one-on-ones, no siloed ownership. Every expert, whether memory, CPU, GPU, optics, or cooling, is in the room on every problem. The problem decides who's needed. Not the org chart.

That reframed something I've been chewing on.

Agents are the forcing function.

AI agents don't organize by department. They organize by process. An agent doesn't care whether a task belongs to "marketing" or "ops" or "finance." It cares about the trigger, the data, the output, and the next state. And when it hits ambiguity, it just fails visibly. That's what finally makes the cost of unclear process real.

Map the flow first. Build the system around the flow. Put humans where judgment is irreplaceable and let agents handle everything mechanical. The org falls out of the work, rather than the work getting crammed into the org.

The alternative is the cul-de-sac most companies are stuck in. They ask where AI can help with what they already do, bolt agents onto workflows designed around 2010 staffing assumptions, and get a slightly faster version of the wrong thing. The org chart is a fossil. Pouring agents into it preserves the fossil.

Every company is a flow. We've been treating them like relay races.

Walk through how value actually gets created in your business. You'll find separate threads with separate owners and separate rulebooks, mostly running in parallel, meeting at the finish line because that's where the calendar said to meet.

Ask a twenty-year veteran to describe the process and they'll describe the people: the roles, the handoffs, the way it's always been done. That's not the work. That's the sociology that grew up around it.

The work itself has physics. Information gets created somewhere and consumed somewhere else. State changes at specific gates. Some dependencies are real. Most are inherited from habit. The sequence is often arbitrary because that's the order the humans got to it.

Look at the physics and you'll find your future org.

Doing the map.

Mapping isn't a metaphor. It's a literal exercise. You're looking for the stages, the gates, the decision points. Where information gets created and where it's consumed. Where the work branches and where it converges. Which dependencies are real and which are inherited from habit.

The output is a flow diagram that fits on a wall, not a process doc. Run the exercise honestly and the answer rarely matches the org chart.

Who maps it.

If you're building from scratch, you have the rare gift of designing the org around the work from day one. Don't waste it by hiring the org chart your industry expects.

If you're inside an existing company, you're looking for someone who can hold the whole flow in their head and see the shape of it. They've usually done the work for years, but the years are the proxy. The thing you actually want is the wiring. Some twenty-year veterans have it, some five-year operators do too. These are the people who become more valuable in the new world, not less, and the move isn't to extract their knowledge and move on. You build the company around the way they think.

Either way, the instruction is the same. Forget the people, the roles, and how it's always been done. Map the work, not the desks.

A concrete example.

At Lineage we run real estate transactions. The conventional view in our industry is three parallel processes, each with its own owner: buying, lending, insurance. Streams cross at predictable handoffs and converge at the closing table. That's the sociology, and it's how every competitor in the category operates.

The physics view is different. There's one deal moving through stages, and most of what looks like the structure of the work is actually the structure of how the industry staffed itself decades ago. The system you need to build when you see that looks nothing like the org chart you'd inherit.

The honest part.

In larger organizations, this transition will cost some roles. The mechanical layer compresses, and the work that compresses is done by real people. Pretending otherwise is dishonest, and the leaders who skip past it lose credibility with everyone who has to live the change. The new work that emerges is real and valuable, but it doesn't always fall to the same people. Operators owe both halves of that truth to their teams.

This isn't a tooling exercise. It's an architecture exercise. The companies that win are the ones that designed themselves around the work, not the ones that bolted AI onto a structure they inherited.

Map the physics. That's where the future is.

AI: 25% | Human: 75% — Jesse drove the framing from a Jensen Huang interview and an internal note to a teammate. Claude abstracted the email into thematic content, structured the first draft, and drafted iterations based on feedback. Jesse edited every pass.