Why Innovation Rarely Fails Where We Look for It

Author: Maria Kolitsch

Organizations change far less than they believe.

They launch transformations. Introduce new methods. Invest in innovation, digitalization, or new technologies. And yet something strange happens: the organization moves – but barely changes.

The reason is rarely the people. Far more often, it lies in the system they work within.

Organizations aren't just strategies, structures, or processes. They're a network of decision logic, incentive systems, power structures, implicit rules, and cultural expectations.

This network determines how an organization actually behaves.

The organizational sociologist Niklas Luhmann described organizations as decision systems. Organizations reproduce themselves through decisions – and through the patterns by which those decisions are made.

That's where what we call the operating system of an organization takes shape. Not what's written on slides. But what actually happens day to day.

Systems shape perception

Systems don't just determine what gets done. They determine what seems possible at all.

Over time, implicit boundaries emerge: which ideas seem realistic, which risks are acceptable, which questions can be asked – and which are better left alone.

Psychologically, this isn't surprising. People adapt quickly to the logic of a system. Our brains favor predictability. Clear expectations reduce uncertainty and social friction.

Organizations amplify this effect further. They reward behavior that fits the system. And they respond skeptically to behavior that disrupts it.

A practical example: When innovation meets the operating system

A company with decades of experience developing and producing highly specialized components launches an innovation project. The idea: build a digital service offering around existing products – something customers don't just buy once, but use continuously.

The team works on it for months. Talks to customers. Builds first prototypes. Tests new usage scenarios. The feedback is surprisingly positive.

Then comes the moment when a decision is needed. Should this offering actually be built?

And suddenly the dynamic shifts. New questions emerge: Who owns the product long-term? Which business unit does it belong to? Does it fit the existing sales structures? How does the revenue map onto existing controlling frameworks?

The discussion grows more complex. Not because the idea is bad. But because it doesn't fit cleanly into the existing system.

A few months later, the project has gone quiet. Not officially stopped. But not moving forward either.

The project didn't fail because of the idea. It failed because of the organization's operating system – a system optimized over decades to develop physical products, minimize production risks, and organize clear responsibilities along established business units.

Innovation was wanted. But the operating system was optimized for stability.

Why methods alone rarely suffice

Many transformation programs therefore focus on methods. New innovation processes. New workshops. New frameworks.

These approaches can be helpful. They create space for new perspectives and enable first experiments. But their impact often remains limited. Not because the methods are bad. But because they sit on top of an operating system that continues to run on different rules.

The system ultimately decides which ideas survive – and which disappear again.

Systems do what they were built to do

The key point is actually simple: systems reliably produce the behavior they were built for.

If an organization has spent decades optimizing for minimizing risk, increasing efficiency, and improving predictability – that's exactly what it will keep doing. Even when its strategy now demands innovation. Not out of resistance. But out of system logic.

The first step is visibility

Real change rarely begins with new tools or methods. It begins with an honest question: what operating system is our organization actually running on?

How are decisions really made? What logic drives our priorities? Which risks are acceptable – and which aren't? Which assumptions have we stopped questioning?

These questions are rarely comfortable. But they're necessary if organizations want to understand why change can be so hard – even when everyone involved actually wants it.

How we work at Leeep

At leeep, we rarely start with methods. We start with the system.

Together with organizations, we look at how decisions actually get made, which logics determine priorities, where tensions arise between strategy and everyday work, and which structures enable innovation – or prevent it.

What often becomes clear: many organizations try to launch innovation without changing their operating system. But that's frequently where the greatest lever lies. Not in the next method. But in the logic by which an organization functions.

The real question

In the end, it comes down to one fundamental question: what behavior does our system produce – and is that really the behavior we need to achieve our goals?

Organizations don't change through new tools. They change when the logic of their decisions changes.

Because systems aren't static. They were designed. And for exactly that reason, they can be redesigned.