Skip to content Skip to footer

What an Organisation Looks Like When It Can See What Is Coming

The previous posts in this series described what goes wrong. The navigation signal lies. The infrastructure layer fails and takes everything that depends on it down at once. The leadership picture arrives after the window has closed. The cheap decision passes, unnoticed, while the cascade builds toward the expensive one. This post describes what changes when an organisation has the capability to see the cascade before it runs.

Not in abstract terms. In operational terms. What the operations team sees differently. What reaches the CEO differently. What the board is asked to approve differently. What finance models differently.

What changes for each stakeholder

Operations

A number instead of an alert

  • Probability-weighted outcome with time attached
  • Trajectory management, not incident response
  • Cheap decision available while window is open

Leadership

Same picture, same time

  • Predicted outcome crosses the gap to leadership level
  • CEO receives something to decide, not acknowledge
  • Board governs the risk rather than reviewing it

Finance

Cost before it happens

  • Forwards-looking DCI input to operational risk provision
  • Structural risk argument to insurance underwriters
  • Evidence of active management, not passive absorption

Board

Governance of risk, not review

  • Cascade mapped before it runs, not post-mortem
  • DBS reviewed 10 incidents before the regulator acted
  • Pattern visible before incident 10 when model is running

Operations: A Number Instead of an Alert

What changes

An operations team using OCTA does not receive an alert that something is degrading. It receives a probability-weighted outcome and a time: if the current trajectory continues, this function is affected in this many hours. That is a different kind of information. An alert says something is wrong. The OCTA output says what happens next and how long before it does.

What it changes

The decision to act moves from reactive to anticipatory. The operations team is not managing an incident. It is managing a trajectory. A heading correction while the anomaly is building. A supplier swap while the tier-one signal is still early. A payment system intervention before 56% of transactions have already failed. The decisions are the same decisions the team would eventually make anyway. They are made earlier, when they are cheaper, because the team knows how much time they have.

Leadership: The Same Picture at the Same Time

What changes

The structural gap between the operational layer and the leadership layer exists because the information that reaches leadership is filtered, aggregated and time-delayed. The OCTA output is designed to cross that gap. It is not operational telemetry. It is a predicted outcome with a time dimension, which is the format leadership can act on.

A CEO who receives a predicted outcome and a window is in a different position than a CEO who receives a status report. The first gives the CEO something to decide. The second gives the CEO something to acknowledge.

What it changes

A board that sees the cascade mapped before it runs can govern the risk. A board that sees the cascade in the post-mortem can only review it. The DBS board reviewed 10 incidents before the regulator made the cost personal. An organisation with OCTA does not reach incident number 10 without the earlier pattern becoming visible.

Finance: Modelling the Cost Before It Happens

What changes

Finance models operational risk as a provision – a figure in the accounts that represents the expected cost of incidents that have not happened yet, estimated from incidents that have. This is backwards-looking modelling applied to a forwards-looking problem. The OCTA Dependency Cascade Index gives finance a forwards-looking input: how tightly coupled the organisation’s critical functions are to the incoming signals that predict cascade risk. The tighter the coupling, the larger the provision should be.

What it changes

Insurance premiums are priced on the same backwards-looking history. An organisation that can demonstrate an active, mapped dependency structure and a real-time intervention window capability is presenting a different risk profile to an underwriter. That is not a claims reduction argument. It is a structural argument that the risk itself is being actively managed, not passively absorbed. The pricing conversation is different when the evidence is different.

The Post-Mortem That Does Not Get Written

Every major incident produces a post-mortem. The post-mortem identifies the point where the cheap fix was available and was not taken. It recommends better monitoring, faster escalation, clearer protocols. The next incident produces another post-mortem with the same findings. The recommendations do not fix the structural gap because they are addressed at the symptom – the escalation process – not the cause: nobody knew how long the window was, so nobody acted while it was still open.

An organisation that calculates the intervention window before the cascade runs does not eliminate operational risk. It eliminates the category of failure that results from not knowing the window was closing. That category accounts for the majority of the cost in every post-mortem across every sector described in this series.

The OCTA model closes that gap. It maps the dependency structure, watches the incoming signals, calculates the cascade sequence and produces a single output: how long before the window closes, for every function that will be affected, simultaneously. Operations, leadership and finance see the same number at the same time. The cheap decision is still available. The post-mortem is the one that does not get written.

The working paper introducing the OCTA model and its mathematical basis is available here: jameslarsson.pro/research-octa

Before you go

Efficiency gain by using AI

Join our community for insights on AI, leadership, and business strategy.