Ideas Aren't the Bottleneck

Idea fatigue isn't a shortage of ideas. It's manufacturing instead of noticing.

6 minute read

A product leader setting down a marker beside a whiteboard of sticky notes to look at an open support-ticket queue on a monitor

Imagine that you’re six hours in with a wall of sticky notes and a facilitator asking everyone to dot-vote on ideas that all sound like the same idea. Somebody always jokes that we should just build all of them.

That exhaustion gets called idea fatigue. The initial diagnosis is that there’s a supply problem, as if there simply aren’t enough good ideas left to find. I don’t think that’s what’s happening.

Ugh! vs. A-ha!

There’s a specific kind of tired that comes from a two-hour ideation session where nobody in the room has talked to a real user in a month. That “ugh” of the same thing over and over without any movement or momentum. The energy goes toward performing the appearance of thinking, on a schedule, in front of people.

A real idea doesn’t feel like that at all. It shows up the moment a support ticket or an offhand comment on a sales call lines up with something that’s been tickling in the back of your head for months. The “a-ha!” moment.

That same friction point logged two different ways, an onboarding call where a customer says setup felt confusing and a lost-deal note where a rep writes off the loss as the buyer going with someone easier to set up. In most orgs, nobody owns both records so the two never get connected. The idea was already there, just unconnected.

Generating asks you to invent something from nothing, on demand, which is a genuinely difficult, and exhausting, cognitive task. Noticing asks you to pay attention to signal that’s already arriving, which is closer to pattern recognition than to creativity, and it doesn’t drain you the same way.

Who Actually Knows?

Ask any product team where their best features came from and the answer is rarely “a brainstorm session.” It’s a support thread somebody forwarded, or if you’re really unlucky, a forum post. It’s a sales and marketing team constantly unable to seal partnerships. Customers hand teams the raw material for good ideas constantly. The bottleneck is what happens to that signal once it reaches someone with the authority to act on it.

Research from Wayne Johnson and Brian Lucas, written up in Harvard Business Review in October 2025 and published in full in Organizational Behavior and Human Decision Processes, calls that bottleneck the idea endorser’s dilemma.

Frontline employees, closest to customers and the raw data of how the product gets used, are often best positioned to spot what needs to change. Middle managers sit between them and the decision, and endorsing an employee’s idea carries real personal risk either direction. If it works, the employee who had the idea gains more status from it than the manager who backed it does, and the gap between them narrows. If it fails, blame lands on whoever vouched for it. The safer move, individually rational and organizationally expensive, is to let a good idea die quietly instead of spending status on it.

 

One of the most rewarding leadership teams I’ve chaired was a cross-functional data team made up of customer service, product, technology, marketing, and finance and, twice per week, helping everyone share amongst themselves and see correlations and causations.

Those “a-ha!” moments where a marketing team’s unsuspecting social media post drove incrased spiked load on servers, driving slow app performance and increasing customer service calls are where our product teams shined in helping not only have real brainstorming, but also premortem on the spot.

That reframes what sourcing ideas from customers requires, because most organizations already have more signal than they know what to do with, sitting in support queues and churn surveys nobody upstream is reading. What’s missing is a way for the person who hears it to act.

Keeping Up

Most leaders instinctually treat idea fatigue as a stamina problem: shorter sessions or fewer meetings to “protect people’s energy” for their best ideas. That’s usually solving the wrong thing. A 2025 study in Communications Psychology, a Nature Portfolio journal tested classic decision fatigue directly, using large-scale field data from a national telephone triage service where the analysis plan was locked before the researchers had access to the data they’d test it on. It found no sign that fatigue pushed nurses toward default judgments or inflated urgency ratings. The authors’ point is narrower and more useful than a universal claim about fatigue. The popular version, the idea that you’re working from a finite tank of willpower draining with every choice, doesn’t hold up well once someone tests it rigorously.

If that’s right, what people feel by hour six of an ideation session is closer to cognitive overload than to a depleted reserve of willpower, the cost of evaluating a pile of unranked, unsourced ideas with no shared criteria for which ones matter. That’s a structure problem. Shorter meetings or “getting everyone in a room together” doesn’t fix it, but cutting down what has to be evaluated from scratch in the room does.

 
Before your next ideation session, use an async tool like Miro and have the team evaluate each idea for specific customer moment or data point it’s responding to. If nobody can answer, it’s not ready yet and goes back in the bin.

Noticing

Ideas aren’t your bottleneck. An idea that alerady traces to a support thread or a lost conversion pattern arrives with evidence attached and is likely ready for you right now. It just needs the room to decide whether the case is strong enough to act on. Ideation stops being exhausting once most of what’s on the wall has already been half-argued by a customer.

Idea fatigue is what happens when a team spends its energy manufacturing options instead of noticing the ones already handed to them, then burns even more energy debating those options that never had evidence behind them in the first place. Noticing is a quieter skill than brainstorming and it’s rarely as exciting for a Monday all-hands. It’s also the only version of ideation that gets less tiring as you get better at it because the work moves from inventing a case to recognizing one that’s already sitting in a support queue.

Before you schedule the next offsite, pull the last month of support tickets and lost conversion notes instead. See how many of offsite’s sticky notes are already sitting there waiting for your team to solve. Use that newly freed time to focus on validating, prioritizing, and excuting.