After Taleb: Why I Built Operating in the Dark for...

Summary

• That separation eventually produced six zones: uncertainty, responsibility, constraint, decision architecture, the operator, and permanent crisis.
• Operating in the Dark: The First Cycle brings together the first three books — uncertainty, responsibility and constraint — while adding chapters, connections and conclusions that become visible when the three are treated as one field.
• Operating in the Dark: The Complete Cycle does the same with the second half, connecting decision architecture, the operator and permanent instability, again with additional material and conclusions.

AI Generated Summary

Nassim Nicholas Taleb gave us one of the most useful modern languages for thinking about uncertainty. Long before I began writing Operating in the Dark, his work had already established a territory that interested me professionally: randomness, fragility, exposure, the limits of prediction, the difference between what a system appears capable of surviving and what happens when an event arrives from outside its assumptions. Fooled by Randomness, The Black Swan and Antifragile changed the vocabulary around risk because they attacked an extremely persistent illusion — that the world becomes more controllable simply because our models become more sophisticated. I had no interest in rewriting that territory. My problem appeared somewhere else, after uncertainty had already entered the room.

In practical work, uncertainty rarely remains a single problem for long. A manager may lack information. Another may have enough information but no authority to act. A founder can possess both and still lack capital, time or organizational capacity. A company may have money, people and authority while its internal architecture prevents those resources from reaching the point where they are needed. Sometimes the organization works and the person carrying its critical decisions is already overloaded. In other situations the whole structure remains technically functional while everybody inside it is unconsciously waiting for an external environment that has ceased to exist. These conditions are often compressed into the same language of uncertainty, leadership or crisis. Operationally, they are radically different.

I began separating them.

That separation eventually produced six zones: uncertainty, responsibility, constraint, decision architecture, the operator, and permanent crisis. Inside each I began assembling frameworks around problems I had encountered repeatedly through years of managing projects, teams, products, transformations and complex systems. The purpose was not to create another universal management doctrine. I wanted to know where one type of problem ended and another began, because interventions become dangerous when those boundaries are ignored. A psychological problem requires one kind of work. An authority problem requires another. An information problem can look remarkably similar to incompetence from outside. A structural failure can survive several generations of talented managers because everybody keeps attempting to repair the people occupying the structure.

This became the six-book core of Operating in the Dark.

There is another reason I wanted to separate these zones. I believe the problem is considerably more relevant now than it was when Taleb’s major ideas began entering mainstream discussion around the turn of the century. Uncertainty itself is ancient. What has changed is the density of connections between unstable systems and the speed at which instability crosses from one domain into another. A geopolitical event becomes a logistics problem, an energy problem, an inflation problem and a corporate planning problem. A technological breakthrough changes investment behavior, labor expectations and competitive positioning before institutions have even developed stable terminology for it. Information travels globally in seconds while verification, legislation and organizational adaptation operate at completely different speeds. Companies depend on platforms, infrastructure, supply chains, payment systems, regulatory environments and political decisions they cannot control. AI is now accelerating another transformation while many organizations are still carrying structural debt from the previous one.

For an operator, this creates a peculiar environment. You are rarely dealing with one crisis. You are standing at the intersection of several systems moving at different speeds, with different levels of visibility and different relationships to your authority. The traditional managerial assumption that instability is an interruption between periods of normal operation becomes increasingly difficult to defend. In many industries and regions, instability is becoming part of the operating environment itself.

I wrote the Operating in the Dark books during the war in Ukraine. Air attacks, power outages and the practical consequences of a country at war were part of the environment in which the work was written. I mention this carefully because war should not be turned into decorative authenticity for a management argument. The underlying ideas did not originate with the invasion; they came from years of professional work with systems, responsibility and decisions. War simply removed a great deal of abstraction from them.