My work develops a single body of thought: how enterprises transform knowledge, evidence, assumptions, judgment, and uncertainty into consequential commitments — and how those commitments become operating performance, enterprise value, risk, and returns on capital.
My early study of markets turned on a distinction I could not stop thinking about: the difference between being wrong because uncertainty resolved adversely, and being wrong because the model was looking at the wrong variables in the first place.
The first kind of wrong is the honest cost of operating under uncertainty. The second is a failure of reasoning wearing the costume of bad luck. Markets are unusually good at telling the two apart — prices move, and profit and loss reports every day. That daily verdict became a reference point for everything that followed.
What drew me next was infrastructure — and a realization that reframed it. Infrastructure is accumulated decision-making made physical. A port, a grid, a rail network is the visible residue of thousands of prior choices about capacity, sequencing, risk, and capital, most of them long forgotten by the time their consequences are load-bearing.
Reading infrastructure this way makes its failures legible. What looks like an engineering problem is often a decision problem that took years to surface.
Companies are similarly accumulated decision-making made operational. That recognition led to years of enterprise modeling and simulation — building representations of corporate value chains detailed enough to run real conditions against real operating behavior.
The models kept revealing the same thing: many apparently operational failures originated in earlier decisions — commitments whose load-bearing assumptions were never named, whose owners were never assigned, and whose correction triggers were never set.
Logyc grew out of that work — enterprise digital twins, modeling, simulation, and value-chain intelligence connecting operational constraints to financial consequences. But better information alone did not solve the problem I had found.
Organizations that could see more clearly still committed to decisions that reality would later overturn, because the clarity lived in the model rather than in the moment of commitment. What was missing was not data. It was infrastructure connecting distributed knowledge to consequential commitments.
Decision Architecture is the discipline I developed to close that gap: surfacing assumptions before commitment, integrating distributed intelligence, making causal reasoning explicit, defining the genuine downside and the signals that would indicate a thesis is failing, assigning responsibility, and preserving the reasoning so reality can test it over time.
The Decision Before the Decision is the operational distillation of that work — the discipline that closes the gap between what an organization could know before commitment and what it actually understands at the moment it chooses to act.
Logyc is where this discipline becomes an operating enterprise business — the Decision Infrastructure that connects consequential commitments with the assumptions, decisions, ownership, and conditions required to deliver them.
I have grown up and built in Silicon Valley and remain an active member of its community. The work across The Decision Before the Decision and Logyc is not two separate ventures. It is one argument, expressed as both a body of thought and the infrastructure that makes it operational.
The gap between what an organization could know before commitment and what it actually understands at the moment it acts.
