Skip to content
Knight Capital: Who Gets to Stop the System? episode artwork

Mar 22, 2026 16 min

Knight Capital: Who Gets to Stop the System?

from Project Management is Boring

In the previous episode, we talked about rollback — the ability to reverse a change when something goes wrong. But rollback capability alone isn’t enough. Someone still has to decide to use it. In fast automated environments, hesitation can be just as dangerous as technical failure. When engineers see unusual behavior, stopping a system may interrupt revenue, halt operations, or create visible business impact. Because of that, people often pause. They escalate. They ask for confirmation. And while that conversation is happening, the system keeps running. Episode 6 explores the governance structures that determine who has the authority to halt a system during an incident.Each segment examines a different dimension of that discipline: why unclear authority delays containment, how escalation chains unintentionally slow incident response, the psychology behind hesitation during outages, and how project managers help define operational authority before systems go live. Together, these segments build toward one central insight: Containment requires authority. If no one is clearly empowered to stop automation when something looks wrong, the system will continue operating while people debate what to do. And in fast systems, those minutes matter.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Knight Capital: Who Gets to Stop the System?

0:00 16:28

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of Project Management is Boring?

This episode is 16 minutes long.

When was this Project Management is Boring episode published?

This episode was published on March 22, 2026.

Can I download this Project Management is Boring episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.