Why Good Ideas Gather Dust: A Systems Thinking Approach to Innovation Adoption
You submitted an idea last year. Since then: silence. Maybe a polite "thank you for your submission" email, followed by a vague promise to advise on the next update meeting. If this sounds familiar, you're not alone — it's a recurring pattern in innovation departments everywhere. And when the stream of new ideas quietly stalls, the office chatter starts: "What does the innovation department even do?"
It's a frustrating position to be in. You know you're solving a real business problem, so why isn't the idea simply being adopted and run with? And when reviewing what could’ve gone wrong it’s easy to point fingers and find a department responsible for the stall. But that's rarely the full story.
Looking Beyond the Blame
Systems thinking asks you to understand a situation by examining the relationships and structures that produce behaviour, rather than fixating on isolated events or blaming individual people or departments. Here's a familiar scenario: as an innovation manager, you help a team build new software to solve a genuine efficiency problem. Months later, no one is using it. It's gathering dust. Eventually someone explains: "the system was too complex to understand, so we just went back to how we've always done things." This doesn't mean the innovation failed because of poor design. It failed because it wasn't examined holistically.
People Follow What Gets Rewarded
People tend to behave in ways their environment rewards and measures. You might roll out new software without ever communicating, organization-wide, how it saves money, improves margins, or ultimately benefits the people using it. Without a clear line between the change and what people are actually measured and rewarded on, adoption stalls — not because the tool is bad, but because the incentive was never made visible.
Resistance Is Feedback, Not an Obstacle
In systems thinking, resistance is usually a balancing loop protecting something the system currently needs — job security, manageable workload, or a sense of professional competence. That makes resistance valuable feedback, not simply an obstacle to push past. Instead of asking "who rejected my proposal?" ask:
1. Why are they resisting the change?
2. What reward or satisfaction does the current status quo provide them?
The answers to those two questions will usually point to the real root cause behind stalled adoption not the surface-level symptom in front of you. Before rushing to fix the visible, surface-level problem, take the time to understand the whole system: the incentives, the relationships, and the structures shaping behavior. That's where sustainable innovation adoption actually begins