In the first half of this season, we focused on risk.

What could go wrong. Where systems break. And why organizations often see those risks… but fail to control them.

But once a system goes live, risk stops being theoretical.

It becomes behavior.

And at that point, the question changes.

Not “what could go wrong?” But:

“What happens when something does?”

Because in fast systems, detection is everything.

Not just whether signals exist.

But whether those signals trigger action.

In the Knight Capital incident, the system didn’t fail silently.

Signals were there.

Trades were unusual. Positions were building. Behavior didn’t match expectations.

But those signals required interpretation.

They required discussion.

And while that discussion was happening…

the system kept running.

This episode explores monitoring and alerting not as tools, but as control systems.

And more importantly—

how project management shapes those systems before they ever need to be used.

Because by the time an alarm goes off…

the response has already been designed.