Getting Ideas Heard

Why the hardest part of innovation isn't having ideas

The hardest part of innovation isn't having ideas. It's getting them understood.

After 20+ years leading product teams at Google, Meta, and startups, I've watched countless good ideas die. Not because they were wrong. Because they arrived before people were ready to hear them.

This isn't a complaint. It's a pattern worth understanding. Because once you see it, you can work with it instead of against it.

Why Ideas Get Stuck

New ideas require people to update their mental models. That's cognitively expensive. It's also threatening. If your new idea is right, it implies the current approach is wrong. And the people who built the current approach are still in the room.

So there's resistance. Not because people are stupid or political (though sometimes they are). But because genuinely new thinking asks something hard of the listener: change how you see the problem.

The further ahead an idea is, the more change it requires. The more change it requires, the harder it is to hear.

This creates a timing problem. Ideas that are only slightly ahead get adopted easily but don't move things much. Ideas that are far ahead move things significantly but struggle to land.

The ideas that matter most are often the hardest to communicate.

What Actually Works

I used to think the answer was better arguments. More data. Clearer presentations. Tighter business cases.

None of that works until people are ready.

What does work is meeting people where they are. Not dumbing down the idea, but finding the bridge between their current understanding and where the idea lives.

This means asking different questions:

• What problem do they already feel?

• What language do they already use?

• What would make this idea feel like a natural next step instead of a leap?

The goal isn't to convince. It's to connect. To find the overlap between what you see and what they can see, then build from there.

Sometimes this means starting smaller than you'd like. Proposing step one when you can see steps one through ten. Letting the full vision emerge over time as people catch up.

It feels slow. It is slow. But it works.

The Rope Principle

There's a saying: you can't push rope. It only moves when pulled.

I think about this constantly now. Pushing harder on people who aren't ready accomplishes nothing except exhausting everyone. The energy goes nowhere.

Pulling means creating conditions where people want to move toward the idea. It means showing, not telling. Building small proofs. Letting people experience the value instead of arguing for it.

The shift from pushing to pulling changed how I work. Instead of presenting finished ideas for approval, I involve people earlier. Let them shape the thinking. Help them arrive at conclusions that feel like their own, because in some real sense, they are.

The idea gets better through collaboration. And it gets heard because people are invested in it.

When Ideas Land Later

Sometimes ideas don't land in your timeline. You propose something, it gets shelved, and two years later it resurfaces as the obvious solution.

This used to frustrate me. Now I see it differently.

The idea survived. It found its moment. The fact that it took longer than expected, or that different people carried it forward, doesn't diminish the idea. The point was never personal credit. The point was the idea being understood and acted on.

What matters is whether good ideas eventually win. Whether the right things get built. Whether the work makes a difference.

If you're optimizing for the ideas mattering, you play a longer game. You plant seeds knowing some won't sprout until you're not around. You accept that the best ideas often need multiple attempts, multiple champions, multiple moments before they land.

This isn't resignation. It's understanding how change actually happens.

The Creative's Challenge

People who generate ideas face a specific challenge in engineering-driven environments. The value of ideas is hard to measure. The value of execution is easy to measure.

So organizations reward execution and tolerate ideation. Sometimes barely.

This creates a gap. The people best at seeing what should exist aren't always the people best at making it exist. And the system privileges makers over seers.

I don't think this is wrong, exactly. Execution matters enormously. But it creates a blind spot. Organizations get very good at building things efficiently and not very good at knowing what to build.

The best teams find ways to honor both. They create space for ideas to be heard, even when they're uncomfortable. They value the people who see around corners, even when they can't prove it yet.

If you're one of those people, your job is to keep showing up. To keep generating ideas. To keep finding ways to connect what you see to what others can understand.

The system won't always reward you. But the ideas need you.

What I've Learned

Meet people where they are. The bridge matters more than the destination. Find the connection between their current thinking and your idea.

Pull, don't push. Create conditions for people to move toward the idea. Show, don't argue. Let them experience value.

Play the long game. Good ideas often need multiple attempts. Measure success by whether the ideas eventually win, not whether they win on your timeline.

Keep generating. The world needs people who see things others don't see yet. Even when it's frustrating. Even when it takes longer than it should.

The point isn't getting credit. The point is getting good ideas into the world where they can do some good.

Everything else is noise.