Jon W. Hansen, FCIPS · Procurement Insights | Hansen Models™
When a hurricane like Isaias heads for the Gulf Coast, most attention goes to the forecast lines on the map. But for any organization that depends on fuel, the greater risk lies less in which line comes true than in the connections around the refineries: feedstock, power, pipelines, terminals, people and policy. A refinery can come through a storm undamaged and still stop shipping because the grid is down or a terminal is closed. David Shillingford’s post on Isaias made the point well: the storm matters because of what it crosses.
That changes what the C-suite should do before the storm arrives. Name one incident lead with defined authority across procurement, finance, IT and operations, within the limits set by safety and technical authorities, and keep one time-stamped decision record that all four use. Procurement maps critical demand to deliverable supply, checks that alternate suppliers don’t depend on the same refinery or terminal, and secures confirmed allocations, pre-positioning fuel only where documented need, storage and safety justify it. Finance pre-authorizes emergency spending. IT decides in advance what evidence counts and what automated systems do when their inputs go stale. Operations sets triggers based on conditions at the assets and on the lead time needed to act safely, because some decisions have to be made before the evidence is certain.
A high-level outline of who owns which connections before, during and after the storm, reflecting input from the Procurement Insights proprietary archive.
And the work doesn’t end at landfall. Track whether deliveries actually arrived, whether the alternates proved independent and whether restarted operations held. Then ask which connections failed, which held and why. The hurricane is one strand. The outcome is decided where it crosses the others. And finally, managing the long-tail impact creates a more reliable feedback loop for future events.
None of this is new. When a fire hit a Philips chip plant in 2000, Ericsson accepted the supplier’s word that production would be back within a week and took no action; Nokia acted at once, and the outcomes split accordingly. After the 2011 earthquake in Japan, analysts called a two-week restart “wishful thinking.” In July, writing about tariffs, I made the same point, adapted here: the shock is not what determines the damage; the structure of the supply chain when it lands is. Strand Commonality™ does not predict the next disaster. It shows where to harden the structure before one arrives.
Truth Is Believing. Accuracy Is Knowing. Outcome Is Proof.™
-30-
The Litmus Matrix is the visual record of each round of review. Every column is an AI model, and every row is a question about the work. A rust cell means a model challenged something and named a defect; amber means it engaged with a condition; mint means it raised nothing, which is not the same as approval. The matrix is not a scorecard, and a board of mint is never the goal: some objections should remain standing, because they mark what is still uncertain. What it shows is where the debate was alive and where it went quiet, so the human orchestrator knows where to look. Accuracy is not decided by any single board. It comes from the feedback loop that follows every decision.
Related
The Storm Is One Strand. The Outcome Is Decided Where It Crosses the Others.
Posted on October 8, 2026
0
Jon W. Hansen, FCIPS · Procurement Insights | Hansen Models™
When a hurricane like Isaias heads for the Gulf Coast, most attention goes to the forecast lines on the map. But for any organization that depends on fuel, the greater risk lies less in which line comes true than in the connections around the refineries: feedstock, power, pipelines, terminals, people and policy. A refinery can come through a storm undamaged and still stop shipping because the grid is down or a terminal is closed. David Shillingford’s post on Isaias made the point well: the storm matters because of what it crosses.
That changes what the C-suite should do before the storm arrives. Name one incident lead with defined authority across procurement, finance, IT and operations, within the limits set by safety and technical authorities, and keep one time-stamped decision record that all four use. Procurement maps critical demand to deliverable supply, checks that alternate suppliers don’t depend on the same refinery or terminal, and secures confirmed allocations, pre-positioning fuel only where documented need, storage and safety justify it. Finance pre-authorizes emergency spending. IT decides in advance what evidence counts and what automated systems do when their inputs go stale. Operations sets triggers based on conditions at the assets and on the lead time needed to act safely, because some decisions have to be made before the evidence is certain.
A high-level outline of who owns which connections before, during and after the storm, reflecting input from the Procurement Insights proprietary archive.
And the work doesn’t end at landfall. Track whether deliveries actually arrived, whether the alternates proved independent and whether restarted operations held. Then ask which connections failed, which held and why. The hurricane is one strand. The outcome is decided where it crosses the others. And finally, managing the long-tail impact creates a more reliable feedback loop for future events.
None of this is new. When a fire hit a Philips chip plant in 2000, Ericsson accepted the supplier’s word that production would be back within a week and took no action; Nokia acted at once, and the outcomes split accordingly. After the 2011 earthquake in Japan, analysts called a two-week restart “wishful thinking.” In July, writing about tariffs, I made the same point, adapted here: the shock is not what determines the damage; the structure of the supply chain when it lands is. Strand Commonality™ does not predict the next disaster. It shows where to harden the structure before one arrives.
Truth Is Believing. Accuracy Is Knowing. Outcome Is Proof.™
-30-
The Litmus Matrix is the visual record of each round of review. Every column is an AI model, and every row is a question about the work. A rust cell means a model challenged something and named a defect; amber means it engaged with a condition; mint means it raised nothing, which is not the same as approval. The matrix is not a scorecard, and a board of mint is never the goal: some objections should remain standing, because they mark what is still uncertain. What it shows is where the debate was alive and where it went quiet, so the human orchestrator knows where to look. Accuracy is not decided by any single board. It comes from the feedback loop that follows every decision.
Share this:
Like this:
Related