The condition.
There is a particular feeling that has become routine for senior operators over the last five years. It is not anxiety. It is not exhaustion in the conventional sense, though it often coexists with both. It is the feeling of never quite being ahead of what is happening.
You respond well to the situation as it arrives. Sometimes very well. The decisions you make are defensible, the actions you take are appropriate, the post-mortems on the things that went wrong reveal that you did roughly what could reasonably have been done given what was known at the time. And yet the situation keeps arriving in a shape you did not anticipate. The competitor's move that, in retrospect, had been signalled for months. The cost input that drifted while you were focused elsewhere. The market condition that everyone is now responding to as though it appeared overnight, when in fact it had been forming for the better part of a year.
You are not alone in this. The condition is general. It is not produced by a lack of intelligence, or effort, or access to information. The people experiencing it most acutely are, in most cases, more capable and better-resourced than any equivalent generation of operators that came before them.
What is wrong is not them.
This primer is about what is wrong, and what would actually be required to address it. It is not the full book. The book is longer, more carefully built, and works at a different depth. But the core of the argument can be made briefly, and is worth making briefly, because the condition it describes is real, common, and rarely named correctly.
The argument.
The world does not move in events. It moves in systems.
The events that appear in headlines, in board reports, in market data are the visible surface of something that has been in motion for months or years. By the time an event arrives, the system that produced it has already done most of its work. Most decision-making is aimed at events. Almost none of it is aimed at what produces them.
This is a structural problem, not a personal one. The reporting cycles that surface information to senior people are designed to aggregate and filter — to convert the granular behaviour of complex systems into formats that humans can read and act on. That conversion is necessary. It is also lossy in a specific direction: it removes precisely the granular behaviour where the earliest signals live. By the time information has been processed enough to appear in a briefing, the situation it describes has already moved.
Consider the Suez Canal in March 2021. A single container ship, the Ever Given, ran aground and wedged itself diagonally across the canal for six days. The images became briefly a cultural moment. Within hours, global shipping rates were spiking, European manufacturers were reporting just-in-time production disruptions, energy markets were registering blockage of oil and gas shipments. A single ship in a single canal had stopped a meaningful proportion of global trade.
The framing of the event focused on the ship. Almost none of it focused on what the event revealed. The Suez Canal handles approximately twelve percent of global trade by volume. Over decades, as efficiency was pursued relentlessly across global shipping, volume had consolidated onto the shortest path. Redundancy had been removed because redundancy is expensive. The network that resulted performs extraordinarily well under normal conditions and has almost no capacity to absorb disruption at the point of concentration.
The Ever Given did not create that vulnerability. It found it.
What the six days revealed was not a nautical incident. It was a structure — one that had been present long before the ship ran aground and would remain present long after it was freed. A structure in which a single point, in a single location, could stop an interconnected global economy in its tracks. That structure is what mattered. The ship was incidental to it.
This distinction — between the event and the structure that produced it — is the entire argument of this book. Events are reported. Structures are not. And the level at which you are reading determines what is available to you to act on.
Pressure.
Structures are stable, but they are not static. Something builds inside them over time. The book calls it pressure. It is not an event. It is what accumulates inside a system as the result of forces that are individually manageable and collectively transformative.
Pressure is what made the Ever Given consequential. Decades of efficiency optimisation had concentrated global trade onto a small number of routes; the consequence of any disruption at those points had been growing for years before it released. Pressure is what made the European energy crisis of 2022. Three decades of deepening dependency on Russian gas had been quietly narrowing Europe's options, even as the cheap gas was running real factories and heating real homes. The event was the cut. The crisis was the dependency, and the dependency had been accumulating, invisibly, for thirty years.
The system was not storing energy. It was storing constraint.
Pressure has a particular character that makes it consistently missed. It builds inside systems that are working. The performance is genuine. The success makes a compelling case for its own continuation. And the same conditions that make the system perform well are often the conditions that make its internal pressure invisible. Performance draws attention. Pressure does not.
This is the trap. By the time pressure becomes visible, the process is already advanced. The options have already narrowed. The obligations have already grown. What looks, in the moment, like a sudden crisis is usually a structure that has been moving toward that moment for longer than anyone tracked.
The decisions that matter, then, are not the decisions made in the moment of crisis. They are the decisions made earlier — by people who were reading the system carefully enough to see the pressure building, while it was still possible to do something about it that did not cost everything.
Most organisations have no systematic way of doing this.
Signals.
If pressure builds invisibly, the obvious question is how anyone ever reads it in time.
The answer is that pressure is not, in fact, invisible. It changes the behaviour of the system carrying it, and behaviour is observable. Long before pressure releases as an event, it expresses itself in how the components of the system are acting — small adjustments, individual decisions, granular activity that, taken in isolation, looks like noise. Taken collectively, it is a signal about the state of the system.
In the months before the Russian invasion of Ukraine in February 2022, a particular kind of activity was visible to anyone watching the right things. Satellite imagery showed accumulation of military equipment along the Ukrainian border. Railway networks inside Russia were carrying unusual volumes of military freight. Field hospitals were being established. Fuel depots were being positioned. The movement involved hundreds of thousands of personnel and a volume of materiel that could not be concealed from commercial satellite operators, from open-source analysts, or from allied intelligence services.
The information existed. It was not hidden. What separated the analysts who read the build-up correctly from those who did not was not access to different information. It was a decision about which information to trust. The logistics behaviour pointed in one direction. The diplomatic signals and the preferred interpretation pointed in another. The people who got it right decided that what a military force was physically doing was more informative than what the surrounding narrative suggested it was likely to do.
The hardest part of reading a signal, the book argues, is not finding it. It is believing it.
This is the second condition of seeing at the level of systems. The first is knowing where to look — having enough of a map of the structure that certain behaviours become legible as meaningful rather than incidental. The second is being willing to act on a reading that is, by its nature, earlier than the consensus that will eventually form around it. The two conditions are not independent. A reading you cannot act on is, operationally, a reading you did not have.
A reading exercise.
If the argument is right, then the question that matters for you, reading this, is whether you can apply it. The book builds toward an operational answer to that question. The primer ends with a smaller version of it: an exercise you can attempt today, against your own situation, to test whether the lens does anything useful for you.
Pick the system you depend on most heavily for your current position. It might be your customer base. It might be a single technology platform. It might be a regulatory environment, a supplier relationship, a talent pool, a category of demand. Choose something specific enough that you could draw it, but consequential enough that its movement would change your situation materially.
Now ask three questions about it, in order.
First: what does this system's performance currently depend on? Not what it produces. What it requires to keep producing what it produces. The honest answer is usually a small number of conditions — assumptions about price, about behaviour, about availability, about regulation, about the continued health of something upstream — that the model quietly relies on without examining.
Second: which of those conditions has been changing? Not changed past tense, but changing — in motion now, even if the movement is small. Most systems contain at least one input drifting in a direction that the operating assumptions have not yet absorbed. Sometimes more than one. Often the drift has been visible for some time, in places not regularly reviewed at the level you operate at.
Third: what would the system look like if the change you have just identified continued at its current rate for another twelve months? Not a dramatic extrapolation. The same rate of drift, the same direction, another year of it. Does the model still work? Are the assumptions still true? Are there decisions that would be obviously correct in that future condition that are not yet being made now?
If you take that exercise seriously for thirty minutes, you will produce a reading that is meaningfully different from anything in your current operating rhythm. It will not be complete. The structural questions are not designed to produce comfortable certainty. But it will surface something — at least one assumption, usually several, that has been quietly carrying weight in your situation and that is no longer as stable as your operating cadence implicitly assumes.
That is what reading a system looks like. The book contains a more disciplined version of it, applied across the kinds of situations that show up most consistently in the work of senior operators. The exercise above is a sample. The capability is a habit. The infrastructure that makes it consistent — that lifts it from a discipline an individual must maintain into something an organisation can operate continuously — is what the book argues for, and what Flinders is built to be.
The shift.
Once you start reading the world this way, it becomes difficult to switch off.
This is not a tactic you are applying. It is a shift in what is visible. Where you once saw an event, you will find yourself looking for the system. Where the headline offers an explanation, you will want to know what produced the conditions in which that explanation became necessary. The story on the surface will still be there. It will simply feel incomplete in a way it did not before.
That feeling — the one this primer began with, of being one move behind — is not a permanent condition. It is the consequence of reading at one level when the world is operating at another. When the level of reading changes, the feeling changes. Not because the world becomes simpler, but because the world becomes navigable in a way it was not before.
The book is Pressure: How to See What's Building Before It Breaks. It develops the argument here at considerably greater depth, with more cases, and with the operational discipline required to do this consistently rather than occasionally. The infrastructure that makes the discipline sustainable in a real organisation is Flinders — Radar, Sextant, and Compass — built to give senior operators what individual attention cannot give them alone: a continuous reading of the systems that matter, held steady against the operational pressure that pulls attention back to the surface.
They were always there. Now you know where to look.