Writing

On systems, pressure, and the architecture of good decisions.

A small number of pieces. Each one earned.

June 2026
What Coordination Architecture Looks Like in a Live Deal

Inside Round 2, management teams discover the story they’re defending doesn’t actually live anywhere. It lives across copies — the CIM, the model, the data room, every answer already emailed to every bidder — made at different times, under different pressure, by different hands. And the people whose judgment matters most are burning it on reconciliation.

“The expertise in the room was always the asset. The architecture is what makes sure it survives contact with the room.”

Read →
May 2026
The Operating Layer Nobody Staffs Until It’s Too Late

Every transaction has a coordination layer that keeps ownership, narrative, and information flow coherent as pressure builds. Most teams don’t staff it. The absence doesn’t announce itself — it shows up as drift, as rework, as the slow erosion of the operating position the leadership team set out to hold.

“Past a certain level of pressure, stability stops being a function of effort and becomes a function of architecture. The improvisation that works at low volume collapses under load.”

Read →
April 2026
What Charles Perrow Would Notice in a Diligence Process

Perrow’s Normal Accident Theory holds that in complex, tightly coupled systems, serious failures aren’t aberrations — they’re the predictable consequence of the architecture itself. The same logic applies to transactions. What looks like a coordination problem is often a design problem.

“At a certain level of complexity, coherence doesn’t emerge from effort. It has to be designed in — ideally before the pressure arrives, because designing it under pressure is genuinely difficult.”

Read →