The Adoption Paradox
It's not that organizations resist innovation. It's that they're designed to exhaust the people who carry it.
The pitch
Here is how it usually goes.
You have an idea. A real one — not a vague notion, but something specific and executable that you’ve thought through carefully. You find the right moment, which itself requires more political calculation than it should. You pitch it. The room loves it. People nod. Someone says “we should absolutely move forward with this.” You leave the meeting feeling like something is finally going to happen.
Then crickets.
Weeks pass. Sometimes months. Then the idea comes up again in a different context — maybe a different meeting, maybe a different group — and you have to tell the whole story from the beginning. Like no one has ever heard it. Like that first meeting never happened. Like the enthusiasm in that room evaporated the moment everyone walked out the door and back into their own priorities.
Most senior practitioners I know have lived this cycle more times than they can count. I have lived it more times than I want to admit. And I want to talk about it honestly — not as a policy problem or a process failure, but as a human one. Because the machinery that kills good ideas inside large organizations isn’t made of bureaucracy and red tape alone. It’s made of people. Specific, recognizable, very human people doing very human things.
The room loves it. Then crickets. Then you tell the whole story again like nobody ever heard it.
The telephone game
The first thing that happens after a good idea gets introduced into a large organization is that it gets translated. Then retranslated. Then translated again.
You say something specific and precise. Someone hears a version of it. They describe that version to someone else. By the time it reaches the person who actually has the authority to move it forward, it barely resembles what you said — even when it’s in writing. I have watched memos get misread, emails get mischaracterized, and presentations get summarized in ways that stripped out exactly the part that made the idea worth doing.
This is the organizational telephone game. And it isn’t incompetence. It’s the natural result of every person in the chain filtering your idea through their own context, their own priorities, and their own calculation of what it means for them. By the time it arrives at the decision point, it’s carrying everyone else’s fingerprints — and sometimes everyone else’s skepticism.
The timing problem makes it worse. Just finding the right moment to present an idea to the right person is itself a months-long exercise in political navigation. You wait for the right window. You read the room. You figure out who needs to be in the conversation before the conversation happens. And then you wait some more. By the time you get your moment, the urgency you felt six months ago has either intensified or been beaten out of you entirely.
Everyone filters your idea through their own context. By the time it arrives at the decision point, it’s carrying everyone else’s fingerprints.
What’s really happening in that room
I want to say something that people rarely say out loud about organizational meetings, because I think naming it is the only way to work around it.
Most of the people in that room are not primarily thinking about your idea. They are thinking about what your idea means for them.
Will this create more work for my group? Does this overlap with something I’m already doing? If this succeeds, does it make my project look less important? If it fails, will I be associated with the failure? Does supporting this help me with the person I’m trying to impress — or does it put me sideways with the person I’m trying not to antagonize?
These are not bad people. They are rational people operating inside an incentive structure that rewards self-preservation and punishes visible mistakes. In that environment, the safest move is almost always to appear supportive while doing nothing. Nod along. Say the right things. Tell the person with the idea how much you love it. Then go back to your desk and do whatever you were going to do anyway.
The person who told you to your face that they loved your idea — and then quietly undermined it through the grapevine — isn’t a villain. They’re a person who has learned that visible enthusiasm costs nothing and visible opposition costs something. So they perform enthusiasm and privately protect their position. You find out what they actually think through a third party, weeks later, when it’s too late to address it directly.
This is the human failure at the center of the adoption paradox. Not malice. Rational self-interest operating inside a broken incentive structure.
The safest move is to appear supportive while doing nothing. Nod along. Say the right things. Then go back to your desk.
The competing interest problem
Even when everyone in the room is genuinely engaged and genuinely well-intentioned, the idea often dies for a different reason: someone else is already doing something adjacent.
Your idea overlaps with another group’s initiative. It touches a system that a different team owns. It requires a developer that three other projects are already fighting over. It needs budget from a pool that was already allocated before your idea existed. The organizational machinery doesn’t have a clean slot for something new — it has a thousand existing commitments that your new thing has to navigate around, and usually the existing commitments win.
I have watched a proof of concept — offered completely free by a vendor and their implementation partner — get stalled for months because one senior leader had a bad experience with that vendor years earlier. A free demonstration of a solution to a documented, expensive problem. Stalled for a quarter. While the broken system it was meant to replace continued to cost the organization money every single day it ran.
That is not a technology problem. That is one person’s unresolved experience from ten years ago functioning as an invisible veto over a decision that objectively made sense to everyone else in the room. And because that person was senior enough, nobody named it. The political cost of naming it was higher than the financial cost of the delay.
So the organization waited. And the broken system ran. And the money bled out. And eventually everyone arrived at the same conclusion they could have reached months earlier — but only after assembling enough data points and presentations and formal justifications to give the skeptic a face-saving way to change their position.
That is the real cost of the adoption paradox. Not the idea that didn’t get built. The months of organizational energy spent creating the conditions under which someone powerful could gracefully agree to something obvious.
The political cost of naming it was higher than the financial cost of the delay. So nobody named it.
What it costs the people who keep showing up
I want to be honest about what this does to the people who keep bringing ideas anyway.
It is exhausting in a specific way that is hard to describe to someone who hasn’t lived it. Not the exhaustion of hard work — that kind of exhaustion is satisfying. This is the exhaustion of friction. Of pushing against a system that absorbs your energy without converting it into momentum. Of caring deeply about something and watching it get slowly dissolved by indifference, politics, and competing agendas.
You start to develop a finely tuned radar for which ideas are worth the fight and which ones will die in the telephone game before they reach anyone who can act on them. You learn to pre-calculate the political landscape before you even open your mouth. You build coalitions before you pitch. You time your moments. You get strategic in ways that feel fundamentally at odds with why you got into this work in the first place.
And still, sometimes, the free proof of concept sits on a shelf for months because of a years-old grudge. And you can’t say that out loud. So you say something diplomatic and schedule another meeting and tell the same story one more time.
I have asked myself more than once why I keep doing it. Why I keep showing up with the next idea after watching the last one get lost in translation. The honest answer is uncomfortable but true:
If I stop bringing ideas, I have no reason to stay. The ideas are not a side effect of the job. They are the job — or at least the only part of it that still feels like mine. The day I make peace with the telephone game and the competing agendas and the decade-old vetoes and stop caring whether any of it moves — that’s the day I’m done.
I suspect I’m not the only one who feels this way.
If I stop bringing ideas, I have no reason to stay. The ideas are the only part of the job that still feels like mine.
What you can actually do
I don’t want to end this without something useful, because I think the practitioners reading this deserve more than a diagnosis.
The first thing is to stop expecting the system to reward what the system was not designed to reward. Large organizations are not designed to optimize for innovation. They are designed to manage risk, maintain continuity, and protect existing commitments. When you understand that, you stop taking the telephone game personally. It isn’t about your idea. It is about a system doing exactly what systems do.
The second thing is to find the single owner. Every decision has one person who actually has the authority and the willingness to say yes. The committee is a distraction. The telephone game is noise. Your job is to identify that person, get in front of them directly, and make the decision as easy as possible for them to make. Reduce the political cost of yes. Give them the face-saving framing. Make it their idea if you have to. Get the thing done.
The third thing — and this is the one I’ve had to learn the hard way — is to build outside the container when the container won’t move. Not every idea needs organizational permission to develop. The capability lives in you. The fluency lives in you. Whatever you can build independently, build. Document it. Refine it. Keep it alive. The organization may catch up eventually. And if it doesn’t, the capability goes with you when you leave.
The ideas are worth the fight. Not every fight — you have to choose. But the ones that are genuinely yours, that you keep coming back to, that the telephone game can’t fully distort? Those are worth showing up for.
Even if you have to tell the story one more time.
If this resonated, subscribe to TECTIQ for practitioner intelligence at the intersection of complex risk, emerging technology, and organizational performance.
TECTIQ Group publishes practitioner intelligence for senior leaders at the intersection of domain expertise, operational risk, and emerging technology. At the Fault Line of Risk and Resilience.
tectiqgroup.com