Introduction: Innovation That Actually Ships

In cybersecurity, innovation is often treated like a slogan  something we talk about more than we practice. We attend conferences filled with visionary keynotes, evaluate platforms promising to revolutionize threat detection, and brainstorm automation ideas in post-incident retrospectives. But turning those ideas into something that ships;  something real, useful, and adopted is where most efforts stall.

Over my career building engineering and security operations teams, I’ve found that cultivating a culture of innovation is one of the hardest and most important things a leader can do. It’s hard not because good ideas are rare, but because meaningful change requires discomfort, coordination, and belief. People naturally gravitate toward the known. Even when we want to change, we usually dip a toe in the water while keeping one foot firmly on the shore.

But real innovation doesn’t emerge from cautious half-steps. It comes from a leap; a decision to think differently and act boldly. I’ll never forget something a colleague said to me years ago at Philips: “The invention of the lightbulb didn’t come from improving the candle.” That line has stuck with me. It reminds me that while continuous improvement has its place, breakthrough progress demands a different kind of mindset  one willing to abandon the safe and familiar in order to build what doesn’t yet exist.

This article is about that mindset not in theory, but in practice.

Whether you’re leading a cybersecurity team, launching a new detection framework, or simply trying to get a proof-of-concept out of someone’s backlog, this is a field guide for getting things built. You’ll find lessons on earning belief before building, on testing quickly and failing wisely, on recognizing real barriers, and on knowing when the market is ready for your idea. These lessons are drawn from real stories in cybersecurity, engineering, and beyond including where things worked, and where they didn’t.

Now, I know I’m not the first person to write about innovation, and there are certainly more polished frameworks and expert treatises out there. This isn’t meant to replace them. It’s simply my way of contributing to the ongoing conversation. It is a reflection of what I’ve seen work in the real world, what’s failed … for me, and the patterns I’ve come to trust after years of building and leading teams in fast-moving environments.

We’ll break this down into three sections that reflect the natural arc of meaningful innovation; not just in theory, but in practice:

• Ignition ; where belief meets vision. This is where it all begins. Before strategy, planning, or roadmaps, there must be belief. Teams need to rally around a clear “why”; a shared conviction that the problem is worth solving and the idea is worth building. Without this foundation, execution becomes aimless.
• Acceleration ; where ideas meet action. Once belief is in place, innovation needs movement. This is the messy middle ; where ideas are tested, prototypes are built, assumptions are challenged, and learning happens in real time. It’s not about perfect execution. It’s about building momentum and getting better with each iteration.
• Elevation ; where innovation meets reality. The final stage is about staying grounded. Even the best ideas must survive the real world. That means respecting the market, recognizing timing, leaning on domain expertise, and partnering across boundaries. This is where innovations evolve from concepts into sustainable, lasting impact.

These three stages mirror the cycle I’ve seen in every successful innovation effort ; especially in cybersecurity, where trust, speed, and timing are everything. Let’s start with Ignition.

1. Ignition ; Where Belief Meets Vision

Innovation doesn’t begin with a roadmap. It starts with belief ; in the problem, the idea, and the potential for impact. Before teams can build anything meaningful, they need to align on why it matters. In this phase, we explore how shared conviction and bold vision set everything in motion.

Key themes:

• Innovation needs emotional investment, not just strategy
• Belief aligns teams and drives commitment
• Vision without action is a dead slide

Start with Belief: Aligning Around Vision First

You can’t iterate on disbelief. Teams must agree on the “why” before they debate the “how.”

When I introduce an idea to a team, something new I’d like us to build, the first response is often a list of reasons why it won’t work. It’s a natural reflex: we analyze risk, anticipate blockers, and try to protect ourselves from failure. But if you’re not careful, these early objections can derail innovation before it ever has a chance.

This is what we call the content trap, getting pulled into debating execution before aligning on belief. Instead of jumping straight into feasibility, I pause and ask the team a more important question: Assuming we could build it, is this worth building? Would it bring value to the customer? Would we be proud to ship it?

That shift in framing changes everything. It focuses the conversation on vision, not logistics. And once you rally the team around the why, you’ve laid the foundation for meaningful, collaborative problem-solving.

Innovation only works when people are emotionally invested in the outcome. The team needs to share a vision not just understand it, but believe in it. Belief fuels creativity, drives persistence, and builds momentum. Without it, every discussion becomes a negotiation over compromises. With it, every challenge becomes an opportunity to make the vision real.

Once the team is aligned, then we can begin the structured process of refinement whether it’s using Edward de Bono’s Six Thinking Hats or another method to examine the facts, feelings, risks, and opportunities. But belief comes first. Without belief, there is no energy behind the effort just empty execution.

Vision Without Motion Is Just a Slide Deck

Don’t get stuck admiring the problem. Take action, even if it’s messy.

Every bold idea starts as a vision. But unless that vision is acted on, it’s just another bullet point in a presentation, another concept gathering dust in a backlog. Innovation demands motion. You have to move. You have to build.

Too often, teams become excellent at describing what’s wrong. They dissect the problem from every angle, outline the constraints, and anticipate what might go wrong. But describing a problem isn’t solving it. As President Obama once said, “I’ve seen people who are very sophisticated in explaining why something can’t get fixed. But what I’m always looking for is someone who says, ‘Let me take care of that.’” That’s the mindset innovation requires.

During my time at McKinsey, I was assigned to work with a long-standing industry vendor whose products had begun to stagnate. Their service was stable, but innovation had slowed to a crawl. I spent months in technical sessions, strategy reviews, and informal lunches with their teams. Each time, I shared practical ideas ; from low-effort enhancements to ambitious, R&D-heavy features. In total, I gave them more than ten actionable suggestions. But nothing happened.

They became paralyzed by options. They asked for documentation, feasibility assessments, and long-term roadmaps. A year later, we decided to drop the vendor. They had fallen into what is called the donkey’s dilemma, stuck between too many bales of hay, unable to choose one, and starving in the process.

The lesson is simple. You don’t need the perfect plan to begin. You need the courage to act, even if your first step is rough. Innovation favors the doers, not the debaters.

2. Acceleration ; Where Ideas Meet Action

With vision in place, progress depends on movement. This phase is about experimentation; building fast, failing wisely, and learning relentlessly. It’s where ideas get pressure-tested and refined, and where hesitation gives way to momentum.

Key themes:

• Speed matters more than perfection
• Failure is feedback, not defeat
• Surface real barriers and ignore the noise

Build to Learn

Test quickly. Fail fast. Learn faster. Then recover and move forward.

Innovation sessions always generate a flood of ideas. Some can be evaluated logically, based on data or known constraints. But others are messier ideas that seem implausible or unscalable at first glance. That’s where prototypes come in.

While “fail fast” has become a familiar mantra, I use this approach very deliberately, for two reasons. First, to validate what works and what doesn’t. Second, because it’s often faster ; and more productive ; to build something and watch it fail than to argue about whether it will work. I call it: the sooner you build it, the sooner it fails, and the sooner you can pivot.

Sometimes the best way to kill a bad idea is to prototype it. Let it run. Let it fall over. And do it quickly, with minimal investment. Not only do you settle the debate, but you also demonstrate decisiveness and respect for the process. And occasionally, the idea that looked shaky on paper surprises everyone.

Of course, there’s a balance to strike. Time and resources matter. But when the cost of a quick proof-of-concept is lower than the cost of three months of circular debate, the choice is clear. Build it. Test it. Move on.

More importantly, this approach sends a powerful message to your team: all ideas are welcome and worth testing. Even if you’re certain something won’t work, showing a willingness to invest a little time in someone else’s idea builds trust. It tells your colleagues that you value their input and that innovation isn’t about being right. It’s about discovering what works. And when you’ve earned that credibility, the next time you push back, your team will know it comes from experience, not ego.

Prototyping isn’t just about speed. It’s about creating a culture where learning is valued more than perfection. That’s the only environment where innovation truly thrives.

Distinguish Constraints from Excuses

Not every barrier is real. Know which ones to challenge and which ones to work around.

One of the biggest blockers to innovation isn’t technology, or the market, or even the budget. It’s the quiet assumptions we stop questioning. “That won’t work in banking.” “That’ll never fly in the Middle East.” “Our clients aren’t ready for that.” These statements are often treated as fact but rarely interrogated.

Innovation requires curiosity; not just about the idea, but about the barriers in front of it. Ask why. Is the pushback grounded in law, physics, or hard limitations? Or is it based on fear, inertia, or outdated precedent?

Some constraints are immovable. Regulations, latency ceilings, and data sovereignty are real and require careful navigation. But many others are cultural, emotional, or political. Those can be challenged. Often what’s labeled as “impossible” is simply unfamiliar.

The key is to develop a framework for understanding the difference. You need a plan to challenge superficial blockers; and a mitigation strategy for the hard ones. Too many great ideas die because no one takes the time to separate real constraints from imagined ones.

In cybersecurity, this mindset is critical. Whether it’s pushing for zero trust in traditionally flat networks or automating incident response in a compliance-heavy environment, progress depends on your ability to see past the default objections and assess what’s really stopping you.

3. Elevation ; Where Innovation Meets Reality

Great ideas only last if they’re grounded in reality. This final phase is about building with humility, partnering with experience, and recognizing the power of timing. To create innovation that sticks, you must respect the landscape you’re entering ; and be ready when the world is.

Key themes:

• Respect history, domain expertise, and timing
• Collaboration beats disruption alone
• The best innovations land when conditions align

Innovate With Respect

Know your limits. Know the landscape. And know whose shoulders you’re standing on.

Innovation is often celebrated as a disruptive force, but real innovation starts with humility. Isaac Newton once wrote, “If I have seen further, it is by standing on the shoulders of giants.” That idea still holds true today. Every product, breakthrough, or platform we create is shaped by the work that came before us.

When building something new, it’s easy to fall into the trap of thinking your idea is the first of its kind. But most innovation happens in existing ecosystems. That means you’re rarely starting from scratch; you’re entering a space with history, experts, patterns, and unwritten rules. To succeed, you have to respect the space and the people who understand it best.

This is especially clear in highly regulated and tightly controlled environments like finance, energy, and healthcare. Startups like Theranos and Babylon Health made headlines with bold claims but failed to fully grasp the regulatory and clinical realities of the healthcare system. In contrast, companies like Flatiron Health and Tempus found success by embedding deeply with healthcare professionals, partnering with oncologists, and building tools grounded in the day-to-day work of medicine. They didn’t try to disrupt from the outside; they built with the system, not against it.

Satya Nadella captured this mindset well when he said, “Empathy makes you a better innovator.” Empathy means listening to those with more experience. It means understanding what already works before trying to improve it. And it means knowing when someone else can do it better than you can ; and bringing them into the room.

In cybersecurity, the same principle applies. A brilliant detection model doesn’t help if it generates alerts that are meaningless to incident responders. A compliance automation tool is useless if it doesn’t align with actual legal requirements. The best solutions come from collaboration between engineers, analysts, legal experts, and frontline defenders.

Ursula Burns once said, “Believe that you can make a difference, but don’t ever believe you have to do it alone.” Innovation thrives in diverse, cross-functional teams. The job of the innovator is not to know everything. It’s to recognize the gaps, bring in the right expertise, and build something that works because it’s grounded in the reality of the space.

In the end, the most impactful innovations are those that last ; and longevity comes from understanding, not just ambition. If you want your work to be the foundation for what comes next, start by respecting the foundation that’s already there.

Seize the Moment

Timing matters. Innovation sticks when the environment is ready.

Every great idea needs the right conditions to thrive. The innovation itself may be sound, but if the timing is off, even the best ideas fall flat.

Take mobile check deposit. Today, it feels like a basic banking feature scan a check with your phone, and it’s in your account. But think back to when it was first introduced. The concept likely faced heavy skepticism. Fraud concerns, trust issues, camera limitations, and bandwidth constraints were all valid points of resistance. Fifteen years earlier, this idea would have been dead on arrival. The tech simply wasn’t there.

What changed? Camera quality improved. Smartphones became standard. Biometric security became normal. The speed and reliability of mobile networks exploded. Together, these shifts created the perfect environment for the idea to succeed. The same feature proposed too early would have failed, not because it was a bad idea, but because the world wasn’t ready for it yet.

Now contrast that with Microsoft’s Lumia phones. In many ways, they were ahead of their time. They had USB-C before almost anyone else. They featured iris scanners and beautiful displays. But the ecosystem wasn’t there. The app market wasn’t robust. Consumer demand wasn’t aligned. Despite the technical brilliance, the product didn’t stick.

Innovation is not just about having the best idea, it’s about recognizing when the market, the tools, and the people are ready for it. Sometimes, you have to wait. Other times, you have to move fast before the window closes. Either way, you need to be tuned in. Because when the moment arrives, hesitation is the enemy.

Conclusion: Innovation That Ships, Scales, and Sticks

Innovation isn’t magic. It’s not reserved for visionaries or unicorn startups. It’s a practice; one grounded in belief, accelerated by action, and sustained by reality.

In cybersecurity, where change is constant and threats evolve daily, innovation isn’t optional. It’s how we stay ahead. Whether you’re building threat detection models, automating response workflows, or rethinking how your SOC operates, the same principles apply. Start with conviction. Move with urgency. Build with humility. And stay ready; because sometimes, the moment finds you.

The truth is, most great ideas don’t fail because they’re wrong. They fail because they’re never given the chance to move. Or they move too early. Or they’re built in a vacuum, disconnected from the people and systems they’re meant to serve.

So, if you’re sitting on a light bulb while everyone else is still polishing lanterns; now is your time.