Why Your Best People Stop Bringing Ideas

In Brief

  • When your best people go quiet, it’s almost never about motivation.
  • Ideas dry up when sharing them has stopped being rewarded.
  • Hierarchy, performance pressure, and a blurred purpose all kill contribution.
  • The fix is rebuilding the safety to suggest, not running an “innovation programme.”
  • One founder I spoke with publicly named his most expensive mistakes — and watched ideas start flowing within weeks.

There’s a moment in every small business where the owner notices something that hasn’t happened in a while. Their senior people have stopped bringing them things.

No suggestions. No “what if we tried.” No “I’ve been thinking about.” The team still shows up. They still execute. They’ve just gone quiet on the kind of thinking that used to be everywhere.

This silence is the signal most owners miss. It rarely shows up in metrics, because the team is still hitting targets. But the engine that produced the targets has changed. You’re now running on instructions, not on ideas.

The misdiagnosis

The first response most founders have is to call it a motivation problem. Maybe people are checked out. Maybe they need a team offsite. Maybe a leadership change is needed.

In nearly every case I’ve seen, that’s the wrong diagnosis.

The people who stopped bringing you ideas aren’t unmotivated. They’re learning. They’re paying attention to what happens when ideas get raised. And they’ve concluded that the cost of suggesting something is higher than the cost of staying quiet.

That conclusion is almost always rational. It’s also almost always recent.

What teaches people to stop suggesting

Watch what happens the first ten times a team member raises an idea in a workplace. Those ten interactions teach the whole team whether ideas are welcome here.

The patterns that kill ideas are predictable. You may recognise some.

The idea is acknowledged and then forgotten. “Great point, let’s pick that up next month.” Next month never comes. The team learns that suggesting is fine, but suggesting is also pointless.

The idea is implemented but the credit moves. A junior suggests something, the founder takes it to a client, the founder is praised. The junior learns there’s no upside to bringing the next one.

The person, not the idea, gets evaluated. Someone proposes a new approach. Instead of evaluating the approach, the room evaluates the person for daring to propose it. After two of those, ideas stop showing up.

The reflex answer is “we tried that.” Sometimes true. Often, a reflex. People learn there is a closed list of things that have been “tried” and an open list of things that are unwelcome.

The reward structure punishes contribution. Suggest something, and you’ll be asked to lead it on top of your regular work. People learn that having ideas means having more work without more support.

Any one of these in isolation is survivable. The pattern compounds. By month nine, your best people are running purely on execution. By month eighteen, they’re updating their CVs. Over time, these small lessons harden into defensive routines — automatic patterns where people protect themselves by saying less.

When the purpose blurs, contribution blurs

There’s another, quieter reason ideas stop flowing. The business has drifted.

In my PhD research with 19 Australian founders, the leaders who built workplaces people brought ideas to had one thing in common — a clear, shared purpose. Not a slogan. A specific, real-world problem the business existed to solve. One founder put it bluntly: “the thing that really matters is not so much the idea, it’s whether or not that idea is solving a real-world problem.”

This is the Holistic Collective. When people are connected to a problem worth solving, they bring their thinking to it. When the purpose blurs into “hit revenue targets and keep the lights on,” contribution drops to whatever the role description requires.

You can tell which mode your team is in by listening to how they describe what they’re working on. If they describe tasks (“I’m doing the report”), you’re in execution mode. If they describe problems (“I’m trying to figure out why our retention is dropping in Q3”), you’re in contribution mode. Only one of those will keep producing ideas.

What the founders who got it right did differently

A few patterns from my research are worth borrowing.

They made it safe to be wrong. One founder told his entire team he had made the most expensive mistakes in the company by a long way. He named them publicly. Not as a performance — as a statement of fact. The effect was immediate. People who had been protecting themselves started bringing forward half-formed ideas and concerns. The safety wasn’t created by an HR programme. It was created by a single statement from the top.

They actually used ideas. When someone suggested something, it got tested. Not always implemented — tested. The team learned that a suggestion would be taken seriously, even if it didn’t survive contact with reality. That’s enough to keep people suggesting.

They flattened where they could. None of these businesses ran on rigid hierarchies. Founders sat with their teams. The more layers between an idea and a decision, the less likely the idea is to survive. Open communication and collaboration aren’t a “nice to have” — they’re two of the eight conditions that show up in workplaces where people actually contribute.

They invited disagreement. “I really do like to hear what others think,” one founder said. Another spoke about wanting “answers from a divergent mindset.” These are small, repeated signals that say — I want you to challenge me. People hear them. The teams responded.

What to do this week

You don’t need an innovation programme. You need three specific things.

Run the last-ten audit. Think back to the last ten ideas your team raised in the last six months. For each, write down what happened. Was it tested, parked, dismissed, or absorbed without credit? The pattern in your answers is what your team has learned about contributing.

Name a mistake out loud. Pick one decision you made that didn’t work. Tell your team about it — not the polished retrospective version. The real one. Watch what comes back at you in the next two weeks.

Test an old idea. Pick one idea that was raised six or twelve months ago and never went anywhere. Resurface it. Have a 30-minute conversation. Either commit to testing it, or be honest about why it won’t go forward. People notice when you go back to old contributions.

If you want a structured way to see where these patterns sit across your whole team, the workplace diagnostic walks you through the conditions that produce contribution.

The team that stopped bringing you ideas is the same team that used to. The capacity is still there. What changed is what the environment taught them. Change what the environment teaches them, and the ideas come back. Usually faster than you’d expect.

For the broader picture across all seven patterns, see What 19 Australian founders taught me about workplaces people don’t leave.

How do I know my team has stopped bringing ideas?
Track the last six months. Can you list ten ideas your team has brought you? Five? Two? If the count is low and you weren’t aware of it, that’s the answer. The drop happens slowly enough that it’s easy to miss.
What if my team has never been "ideas people"?
Most teams have ideas. They just have history with what happens to them. If your team isn’t bringing things, ask one or two trusted people: “Have I made it hard to bring me suggestions?” The answers will surprise you.
Should I run an idea-of-the-month programme or innovation initiative?
Probably not. These programmes signal that ideas live in a separate special box, which actually reinforces that they’re not part of normal work. The fix is making everyday contribution safe, not creating a parallel structure.
How do I respond when an idea won't work?
Engage with it. Explain why you don’t think it will work, what would need to change to make it work, or what the constraint is. “We tried that” is the wrong answer even when it’s true — describe what happened and what was learned. People keep contributing when their thinking is taken seriously, even if it isn’t adopted.
How long does it take for ideas to come back once I change my response?
Faster than you’d think. Most teams test the new behaviour with small, low-risk suggestions within two to four weeks. If the response is genuinely different, the bigger ideas follow within a couple of months. Trust rebuilds quicker than it broke.
More like this

Where do you start?

If something here resonated, here's where to go next.