The “killer switch” story is not just a tech failure

A programmer is facing 10 years in prison. The cause? He left behind a “killer switch”, malicious code designed to shut everything down the moment he was fired.

Scary, right?

But here’s the harder truth: this isn’t only a tech failure. It’s a leadership failure.

People rarely wake up one day and decide to sabotage a company. They get there after months, sometimes years, of feeling ignored, undervalued, and disconnected. The code bomb is the symptom. The real disease is a broken relationship between the organization and the people building it.

That said, culture is only half the story.

Let’s be very clear: no single employee should ever have the unchecked power to take down a system in the first place.

That is a management responsibility, building systems and processes so no one person becomes a single point of failure.

What companies should do differently

If you want to prevent crises like this, you need both safeguards and healthy team dynamics.

1) Strong code review and change control

Robust reviews are not bureaucracy. They are risk management and knowledge sharing.

• Catch suspicious or risky changes early
• Ensure critical paths are understood by more than one person
• Reduce the chance of hidden logic slipping into production

2) Access control and separation of duties

Limit what any single individual can do without oversight.

• Use least-privilege permissions
• Protect production with approvals and auditing
• Require multiple reviewers for sensitive areas

3) Communication channels that surface issues early

If frustrations only show up at exit interviews, you are already too late.

• Regular 1:1s that feel safe and actionable
• Clear escalation paths when someone feels blocked
• A culture where “this is risky” is welcomed, not punished

4) Employee well-being as a security investment

Engaged, supported teams do not become disgruntled teams.

Treat well-being as part of operational resilience, not a nice-to-have.

The lesson

You can’t code-review your way out of poor culture, and you can’t “culture” your way out of poor systems.

Strong leadership and strong safeguards go hand in hand.

At JiNi, we help companies prevent crises like this by building resilient, people-centric tech teams, from auditing current practices to implementing the right processes and controls.

What’s one practice you’ve seen that keeps teams both secure and supported?