When Good Teams Stop Innovating: The “Magic Number” Problem in Cybersecurity

When Good Teams Stop Innovating: The “Magic Number” Problem in Cybersecurity

When Good Teams Stop Innovating: The “Magic Number” Problem in Cybersecurity

We often assume innovation fades because leaders lose interest or budgets dry up. But as Safi Bahcall explains in Loonshots, that’s rarely the real reason.

In Chapter 7, “Phase Transitions II: The Magic Number,” he shows that organisations stop innovating not because people change — but because incentives do.


The Moment the System Snaps

Bahcall describes a threshold — a “magic number” — where organisations subtly shift from encouraging bold, high-impact ideas (“loonshots”) to rewarding safe, predictable execution.

It’s the moment when:

  • The perks of rank outweigh the stakes of outcomes,
  • Managers are rewarded more for avoiding mistakes than for backing new ideas, and
  • Innovation quietly gives way to bureaucracy.

He calls this silent shift the “invisible axe.” It doesn’t kill innovation with a loud “no.” It strangles it through structure, incentives, and risk-averse career logic.


Why It Matters for Cybersecurity

In security, risk, and compliance, this dynamic plays out daily.

We build frameworks, controls, and audit pillars (our “franchises”) to keep systems resilient. But when an organisation crosses its “magic number,” governance starts favouring stability over curiosity.

That’s dangerous. Because our threat landscape never stands still. Attack surfaces evolve. Adversaries innovate faster than our committees approve change.

If our structures reward only risk avoidance, bold security innovation — automation, predictive analytics, AI-driven defence — dies before it’s tested.


The Lesson: Structure Drives Behaviour

Bahcall’s point is blunt:

“You don’t fix culture with speeches. You fix it by adjusting structure — spans, layers, incentives — so the system favours new ideas again.”

If you lead cybersecurity or compliance strategy:

  • Map where you are on that phase curve.
  • Check if your teams are rewarded more for compliance metrics than innovation impact.
  • Protect your “loonshot nursery.” Give small, agile teams autonomy and psychological safety to test ideas fast.


A Practical Checklist

  1. Audit incentives, not just controls. Who benefits from staying safe?
  2. Watch for the “magic number.” When layers multiply, innovation usually fades.
  3. Balance soldiers and artists. We need both — operators to execute, and innovators to explore.
  4. Create safe spaces for risk. Some experiments are about learning faster, not just delivering ROI.


Closing Thought

After three decades across defence, telecoms, and cybersecurity, I’ve seen this pattern repeat: It’s rarely lack of talent that kills innovation — it’s the system itself.

The good news? Systems can be redesigned. That’s what separates organisations that simply comply from those that truly transform.

Maybe the real “magic number” isn’t headcount. Maybe it’s the number of people brave enough to protect their loonshots.


#CyberSecurity #Innovation #Leadership #Loonshots #RiskManagement #Governance #DigitalTransformation #NIS2 #SecurityLeadership

Interesting.. when orgs have to hunker down they'll prioritise the checklists and maintain that core service or compliance stat. On this basis innovation is only realistic in a growing organisation.

To view or add a comment, sign in

More articles by Mark Lewis

Others also viewed

Explore content categories