Send us Fan Mail

On May 18, 2012, Facebook went public, and Nasdaq expected the opening to produce the largest IPO order volume in its history. What it got instead was a system that couldn't finish calculating the opening price. Engineers pushed through an untested workaround, and the exchange declared the problem solved. Trading was open. The tape was printing. From the outside, everything looked fine.

It wasn't. For the next two hours, thousands of trade confirmations never went out. Firms across Wall Street had placed orders and had no way to verify whether those orders had gone through. At 12:01 that afternoon, the CEO of a major market-making firm put it to Nasdaq's CEO in three words: we are all trading blind.

This week, Mike breaks down the Facebook IPO failure through what he calls the Unknown Status Problem, the doctrinal cousin of a common operating picture failure in emergency management. It's the gap between what an organization believes is true and what is actually true, and why that gap is more dangerous than a visible failure. A known problem tells you to fix it. An unknown status tells you to go find out, and most organizations aren't built to notice that second condition exists at all.

The episode also covers how UBS turned an unknown status into a documented $349 million loss by taking a second action to compensate for a first one it couldn't confirm, and closes with a Monday-morning audit any leader can run in under a minute: find one decision in your organization standing on a time-bound assumption right now, and ask who owns coming back to it if that assumption expires.

Frameworks referenced: Business Lifelines™, the Unknown Status Problem, Green/Gray status distinction

Companion content: This episode pairs with this week's Blue to Gray deep dive, expanding on the decision-shelf-life concept and the UBS compounding-loss mechanism.

Links

• Blue to Gray deep dive: bluetogray.beehiiv.com
• Southwind Planning Solutions: southwindplanning.com
• Contact: mike@southwindplanning.com

www.southwindplanning.com

www.bluetogray.beehiiv.com

Send us Fan Mail

On a July evening in 2024, a piece of equipment failed on a transmission line in Northern Virginia. The grid's protection system responded correctly. So did the protection systems inside a cluster of nearby data centers. Within 82 seconds, roughly 1,500 megawatts of demand vanished from the grid — not because anything malfunctioned, but because two systems, each behaving exactly as designed, produced a combined outcome nobody had modeled.

This week, Mike breaks down the July 2024 Northern Virginia load-loss event — and the NERC and FERC actions still unfolding around it in 2026 — through what he calls the ownership gap: the space between two individually correct systems that nobody was ever assigned to own.

Using the Business Lifelines™ framework, this episode covers:

• Why "each system worked" doesn't mean "the organization is safe"
• Why an unknown condition — Gray — is more dangerous than a known failure
• Where ownership gaps hide in healthcare, manufacturing, and logistics
• A 20-minute R.I.S.E. exercise to find and close your own ownership gaps before they find you

www.southwindplanning.com

www.bluetogray.beehiiv.com

Send us Fan Mail

Nothing about the Homeland Security Information Network ever looked broken. Alerts kept going out. Information kept flowing. That's what made it dangerous.

In this episode, Mike breaks down the HSIN breach — discovered in early July after weeks inside the platform federal, state, local, and private-sector partners use to share threat intelligence — and the failure underneath it that has nothing to do with cybersecurity expertise. Every agency pulling information off that platform had a source with a track record. What none of them had was a running answer to a second, separate question: is this specific information still accurate, right now — because the first answer had been "yes" for so long that nobody thought to keep asking the second one.

That distinction — trusting a source versus verifying today's claim from it — is the same discipline intelligence analysts are trained to hold onto, and it's the same discipline that failed inside SolarWinds in 2020, when a digitally signed, routinely trusted software update carried a backdoor into roughly 18,000 organizations, including several federal agencies, for months before anyone noticed.

This episode walks through:

• What actually happened inside HSIN, and why the platform staying operational the entire time is the real warning sign
• The difference between trusting a source and verifying what it's telling you right now — and why almost every organization quietly collapses the two into one
• How the SolarWinds compromise shows the same pattern at a different scale
• Why vetting a vendor once at the start of a relationship isn't the same as ever checking again
• Four low-cost, low-effort ways to keep confirmed information from quietly turning into stale assumption — without adding headcount or new software: expiration dates on operational data, trigger-based audit gates tied to change management, tolerance-bandwidth alerts, and the ten-minute pre-mortem
• A three-step, no-new-software exercise for finding the sources your organization has stopped questioning, before something forces the question for you

Mentioned in this episode: Business Lifelines™, Information Hygiene, the Signal Integrity Assessment

www.southwindplanning.com

www.bluetogray.beehiiv.com